<homer> Stupid network! </homer>

[Paul Baumgardner]

On 4/16/06, David Kramer <david at thekramers.net> wrote:
> For MattG, here's the IP addresses I'm using:
> 192.168.1.1   Internal side of WRT54G
> 192.168.1.2   IP address I originally tried having the WRT54G log
>                into my server with, but now I'm using DHCP, which
>                is serving it 192.168.1.99, which is correct.
> 192.168.1.3   Internal network card on my server
> 192.168.1.4   IP address of my Linux wireless laptop (fixed)
> 192.168.1.8   IP address of my daughter's wired Win2K box (fixed)
> All netmasks are 255.255.255.0
>
> Routing table on my server is:
> Destination  Gateway    Genmask     Flags Metric Ref Use Iface
> 66.92.68.0   0.0.0.0    255.255.255.0   U     0   0   0 eth0
> 192.168.1.0  0.0.0.0    255.255.255.0   U     0   0   0 eth1
> 169.254.0.0  0.0.0.0    255.255.0.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      66.92.68.1 0.0.0.0         UG    0   0   0 eth0
>
> Routing table on my laptop is:
> Destination  Gateway    Genmask     Flags Metric Ref Use Iface
> 192.168.1.0  0.0.0.0    255.255.255.0   U     0   0   0 eth1
> 169.254.0.0  0.0.0.0    255.255.0.0     U     0   0   0 eth1
> 127.0.0.0    0.0.0.0    255.0.0.0       U     0   0   0 lo
> 0.0.0.0      192.168.1.1 0.0.0.0        UG    0   0   0 eth1
> (I have no idea what the 169.254.0.0 line is doing there)
>
> Interestingly, if I try to ping my WRT54G with it's DHCP'd address of
> 192.168.1.99, I get:
> PING 192.168.1.99 (192.168.1.99) 56(84) bytes of data.
>  From 192.168.1.3: icmp_seq=1 Destination Host Unreachable
> ...
> On the WRT54G, I see the "internet" light blink in time with the pings.

Don't you need to have wireles hub on a different IP range for routing?

On my server setup I have the LAN nic on 192.168.0.1  that connects to
a hub for all my wired PC's and then I have a wireless NIC (server is
an AP)  that is 192.168.1.1 for my laptops, etc.