Another stupid ICS question

[Steve Scrimpshire]

I'm sharing with a Win2K box with the Linux box as the server. No router/hub, just a crossover cable. The way I've done it before always worked, but now, it doesn't. I have searched here and google and cannot find the answer. I ran DrakGW, just like I've always done and I set up Win2K to get it's IP automagically. It gets the IP fine when I do ipconfig /renew, but I cannot surf. Here is my /etc/dhcpd.conf file:

ddns-update-style none;

subnet 192.168.0.0 netmask 255.255.255.0 {

# default gateway

option routers 192.168.0.1;

option subnet-mask 255.255.255.0;

option ip-forwarding on;



option domain-name "omarserenity.no-ip.com";

option domain-name-servers 204.127.199.8, 63.240.76.198;



range dynamic-bootp 192.168.0.16 192.168.0.253;

default-lease-time 43200;

max-lease-time 21600;

}

 

The option ip-forwarding was not in there by default after running DrakGW and I've tried it with and without. The option domain-name-servers, I've tried with only one ISP DNS server, with both (as you see here) and with just 192.168.0.1. My /etc/resolv.conf is fine. With the option domain-name-servers as 192.168.0.1, the name doesn't resolve in Windows...I just get "Finding site yahoo.com..." in the status bar or whatever. With the option domain-name-servers as you see them here, it resolves and I see "Connecting to site 216.109.118.65..." in the status bar, but it takes a few minutes and then goes to a "Page cannot be displayed" error (Cannot find server or DNS error). I have no idea how to troubleshoot this.

 

Here is the output of ifconfig:

 eth0      Link encap:Ethernet  HWaddr 00:0C:6E:84:CA:EF

         inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0

         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

         RX packets:1957 errors:0 dropped:0 overruns:0 frame:0

         TX packets:1657 errors:0 dropped:0 overruns:0 carrier:0

         collisions:0 txqueuelen:100

         RX bytes:201916 (197.1 Kb)  TX bytes:223201 (217.9 Kb)

         Interrupt:4



eth1      Link encap:Ethernet  HWaddr 00:90:64:B4:AC:DB

         inet addr:<<ip removed for privacy>>  Bcast:255.255.255.255  Mask:255.255.255.0

         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

         RX packets:685721 errors:0 dropped:0 overruns:0 frame:0

         TX packets:6635 errors:0 dropped:0 overruns:0 carrier:0

         collisions:0 txqueuelen:100

         RX bytes:42317680 (40.3 Mb)  TX bytes:434777 (424.5 Kb)



lo        Link encap:Local Loopback

         inet addr:127.0.0.1  Mask:255.0.0.0

         UP LOOPBACK RUNNING  MTU:16436  Metric:1

         RX packets:4168 errors:0 dropped:0 overruns:0 frame:0

         TX packets:4168 errors:0 dropped:0 overruns:0 carrier:0

         collisions:0 txqueuelen:0

         RX bytes:242524 (236.8 Kb)  TX bytes:242524 (236.8 Kb)

 

and route -n:

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

xxx.xxx.xxx.0   0.0.0.0         255.255.255.0   U     0      0        0 eth1

192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

0.0.0.0         xxx.xxx.xxx.1   0.0.0.0         UG    0      0        0 eth1

 

Of course in route -n, the xxx.xxx.xxx.0 and xxx.xxx.xxx.1 are actual ips

Any thoughts? Does it have something to do with the Genmask of both adapters being 255.255.255.0?

[Steve Scrimpshire]

I had installed 9.2rc2 with disks I had burned from the isos currently available for it. Since then, I have reinstalled 9.1 and am upgrading through urpmi and cooker to 9.2rc2. So far, it is working. Must be something broken in the isos.

[Ric]

what dose the

option ip-forwarding on

do, I havent come across it before

 

Ric

[Steve Scrimpshire]

Well, I think with the latest DrakGW, it is taken care of elsewhere, but I added that, because in 8.1, that was one of the things that I had to do to get it to work and I was trying everything. What it did back then, was make sure that when the box behind the firewall surfed, it was seen as the same ip as the machine actually connected to the net. I think, in dhcpd.conf, all it really does is make sure the value inside some file (I forget which one) is '1' to enable that. I think, for iptables.