waspbloke
Group: Members
Posts: 4
Joined: Jan. 2006 |
|
Posted: Jan. 02 2006,14:03 |
|
Hello, first thing to say is that I am a Linux virgin - well not quite, I have kissed a few but never climbed into bed with any. Until DSL opened my eyes to the joy of 50mb distros - now I can't stop fiddling.
My problem is:
I have a W2Kpro with 3 NICs NIC1=red/internet, DHCP NIC2=green/LAN, Static IP 192.168.0.1/24 NIC3 unused
My brother has a laptop 1 NIC: NIC1=green/LAN, Static IP 192.168.0.42/24 gw 192.168.0.1 dns1 and dns2 are set to my external dns
When in windows it works as you'd expect.
When I boot my machine with DSL i want to be able for brother's laptop to seemlessly connect to the internet as before.
I have read this forum to bits and the wiki and so many other Linux (networking/IP masqerading/IP forwarding) how-to sites and am frankly stuck!!!
I think it was YoLinux site that seemed to sugguest that all I need do is set my static IP, enable IP forwarding and add a couple of routes. I have tried all ways but no matter what i do, the 192.168.0.42 laptop remains unpingable, it can't ping my DSL machine and no ICS happens.
I have IPtables extensions loading from myDSL at boot, tried the rc.firewall extension (no joy) and using the rc.firewall setup script from their site - says everything was done properly but still no traffic.
I suspect the problem is the routing as when I look at my W2Kpro route table it has a bunch of 224.0.0.0 and 255.255.255.255 stuff (11 routes and 1 default gw), whereas my DSL routes are way more minimal with only 3 or 4 routes.
Now I am no networking guru but am capable of creating good solid small office networks and such in windows. Linux seems to be the OS of choice for doing routing/firewalling and the fact that my pre-configured coyote-linux floppy fw/router got on with and did exactly what i wanted makes me think something simple is missing in my DSL config/install.
There's an awful lot of ambiguity about how to setup a static IP addy on my eth1 LAN adapter aswell - I currently have a line in bootlocal.sh: ifconfig eth1... etc. Some sites suggest putting scripts in various locations within /etc. What to do?
Please please help!
|