On Wed, 2004-07-28 at 02:00, Scot L. Harris wrote: > On Tue, 2004-07-27 at 18:48, Erik P. Olsen wrote: > > > netstat -rn on server yields: > > > > Kernel IP routing table > > Destination Gateway Genmask Flags MSS Window irtt > > Iface > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 > > eth0 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 > > eth0 > > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 > > eth0 > > > > I have tried to route add -net 192.168.2.0 gw 192.168.1.7 to no avail. > > netstat on a customer machine gave: > > I think you may need to add a netmask to your route add command. I know > it should know that from the 192.168 being a class C address but I have > found some other Unix systems had problems without specifying the > netmask. > > Just to confirm, you can ping 192.168.1.7 right? Yes, I can. > Also, with the Linksys wireless device, how did you connect it? Did you DHCP picked that address. I first configured the Linksys router offline then attached it to the WAN router and the address 192.168.1.7 showed up on the Linksys setup window. > define the WAN port with 192.168.1.7? If you connected your 192.168.1 > network to the switch or LAN side of the wireless router I think the > wireless users are simply bridged over to that network. In other words > the WAN port would be unused and all of your devices, server and > wireless users, would be on the 192.168.1 network. > > I have to look at the linksys to see if the wireless portion can be > configured for a different subnet or not. I had no problem configuring it to a different subnet. With the factory defaults the LAN address of the Linksys router is 192.168.1.1 but since that conflicts with the WAN router's adresses I had to chose something else. When you then pick 192.168.2.1 and commit it you'll just have to logon to http://192.168.2.1 to continue configuring it. Piece of cake. -- Regards, Erik P. Olsen
