[YLUG] Interesting Networking Problem

[Njal Munro]

Ok so, i have just bought and installed a new NIC and am awaiting a
wireless adaptor, now the wireless adaptor is going to allow anyone in
my house SSH (or something like that) access to the server, even if
someone else is pysically using the server for some random reason.

Now am going to use the 

			 /Laptop 1
modem > server > router > Laptop 2
			 \Laptop 3

Set-up i shall look through the previous replys for links but now i know
exactually how i want to set up this network, can anyone add anything to
the advice list, thanks Stephen for letting me know about ddclient, i
shall definatly check that out and look into it, coz by the sounds of
it, it's what i need.

My presumptions is (since i have not installed ubuntu on the server yet)
that it's onboard network card will be eth0 and the new NIC i added will
be eth1 and the wireless might be eth2, i will have the modem coming
into eth0 and going out to the router on eth1, (it's a cable modem) i
could route the incoming eth0 out to eth1, in a simelar manner to how i
had been trying on the mini network. I remember that
setting /proc/sys/net/ipv4/ip_forward to 1, shared a connection, but i
remember that gets reset every reboot, now i could write a script to run
on start up, but i'd much rather have it perminatly set up.

Am i getting my meaning accross, i think i might be confusing myself at
this point, so i shall keep it here, and delve further into this a
little bit at a time.

Many thanks
Neil Munro



On Sun, 2006-05-14 at 09:53 +0100, Gaffer wrote:
> Hi Neal,
> 
> I don't know if it will help, but the Ipcop Firewall project on 
> Sourceforge could be a good source of info !  It certainly gave me a 
> good insight into networking machines and isolating local lans from the 
> Internet !!  I now use an old 486 as my firewall.  ( But then I'm too 
> lazy to climb into the loft to change it !!) ;-)
> 
> On Saturday 13 May 2006 23:27, Njal Munro Scribbled:
> > On Sat, 2006-05-13 at 22:37 +0100, Stephen wrote:
> > > On 13 May 06, Njal Munro (neilmunro at gmail.com) wrote:
> > > > Ok so i need a wee bit more help, just a few things i need to
> > > > clarify, our network is as follows: -
> > > >
> > > > 		         /  Laptop 1
> > > > Modem > Wireless Router	-   Laptop 2
> > > >                          \  Laptop 3
> > > >
> > > > So the websever i run from laptop 1 can be accessed by laptops 2
> > > > and 3, now, i presume that website can't be accessed from ouside
> > > > the router?
> > >
> > > Well, the default firewall configuration on your wireless router
> > > would be not to allow external addresses to access internal network
> > > services, though you can set up port forwarding if you want the
> > > outside world to be able to reach (for instance) apache on laptop1.
> > >
> > > > And if so, my guess is the network mapped out should look like
> > > > this?
> > > >
> > > > 			 /  Laptop 1
> > > > Modem > Server > Router -   Laptop 2
> > > >                          \  Laptop 3
> > > >
> > > > For the server to both be accessed inside our network and from
> > > > 'the cold
> > >
> > > Thats the simplest way of doing it, though you'll then need a
> > > firewall on your server. Thats basically how I have things set up
> > > here, with dyndns (ddclient) so the server can at least keep the
> > > same hostname when its IP changes.
> >
> > Well it's going to be either debian stable or dapper for the server
> > OS, but next question is, if we connect the server to the modem, and
> > get a second network card, we can forward packets to the router? I
> > presume so, but just need to check....
> >
> > thanks for the help thus far, again until i get the parts i cant
> > ACTUALLY test all this, but at least i know the right direction in
> > which to go.
> >
> > Many thanks
> > Neil Munro
>