<homer> Stupid network! </homer>

Sun Apr 16 20:38:23 EDT 2006

markw at mohawksoft.com wrote:
> First the stupid stuff, into which port of the WRTG54 did you plug into
> the hub?
> 
> If you plug into the WAN port, then you will be using the WRTG54 as a
> router and the wireless computers will need a different base IP address
> and netmask. If you plug the hub into the (with a crossover) the standard
> bank of RJ45s it will ignore the who WRTG54 router software and just be
> used as an access point.

I've tried all sorts of configurations.  But in the
server --> hub --> wired computers
                --> WRT54G --> wireless conmputers
configuration, I tried the WRT54G in both a regular slot and the 
"cascade" slot, which I'm pretty sure would be the automatic crossover 
wiring for hub-to-hub.  I was also sufficiently desperate that I tried 
putting the server in the cascade slot.

OK, I'm going to simplify the setup to eliminate as many variables as 
possible.  I'm going to do

server --> ("internet" jack) WRT54G (LAN jacks) --> wored computers
                                                 --> wireless conmputers

Should I need a crossover cable from the ethernet jack on my server to 
the internet jack on the WRT54G (I dont' have one, but I can get one 
tomorrow I guess)?

What I'm seeing is that stuff goes out but doesn't come back in.  On the 
wired computer (Win2K), when I hit a web page, I see the sent packet 
count go up and the received packet count never does.

When I hit www.blu.org on my wireless laptop, tcpdump on eth1 (internal) 
looks like this:
20:08:45.454757 arp who-has 192.168.1.99 tell 192.168.1.3
20:08:46.455122 arp who-has 192.168.1.99 tell 192.168.1.3
20:08:47.455490 arp who-has 192.168.1.99 tell 192.168.1.3
20:08:48.872136 IP 192.168.1.3.netbios-dgm > 192.168.1.255.netbios-dgm: 
NBT UDP PACKET(138)
20:08:50.437208 IP 192.168.1.99.intersan > 
dns.nyc1.speakeasy.net.domain:  33521+ A? www.blu.org. (29)
20:08:50.437906 IP 192.168.1.99.netdb-export > 
ns-legacy.speakeasy.net.domain:  49895+ A? www.blu.org. (29)
20:08:50.438344 IP 192.168.1.99.pcia-rxp-b > 
dns.nyc1.speakeasy.net.domain:  30176+ AAAA? www.blu.org. (29)
20:08:50.438531 IP 192.168.1.99.streetperfect > 
ns-legacy.speakeasy.net.domain:  49324+ AAAA? www.blu.org. (29)
20:08:50.460599 arp who-has 192.168.1.99 tell 192.168.1.3
20:08:50.872925 IP 192.168.1.3.netbios-dgm > 192.168.1.255.netbios-dgm: 
NBT UDP PACKET(138)
20:08:51.460968 arp who-has 192.168.1.99 tell 192.168.1.3
20:08:52.461336 arp who-has 192.168.1.99 tell 192.168.1.3
20:08:52.873818 IP 192.168.1.3.netbios-dgm > 192.168.1.255.netbios-dgm: 
NBT UDP PACKET(138)
20:08:54.874339 IP 192.168.1.3.netbios-dgm > 192.168.1.255.netbios-dgm: 
NBT UDP PACKET(138)
20:08:55.443815 IP 192.168.1.99.passwrd-policy > 
ns-legacy.speakeasy.net.domain:  33521+ A? www.blu.org. (29)
20:08:55.444205 IP 192.168.1.99.writesrv > 
dns.nyc1.speakeasy.net.domain:  16685+ A? www.blu.org. (29)
20:08:55.444991 IP 192.168.1.99.digital-notary > 
ns-legacy.speakeasy.net.domain:  30176+ AAAA? www.blu.org. (29)
20:08:55.445356 IP 192.168.1.99.ischat > dns.nyc1.speakeasy.net.domain: 
  23035+ AAAA? www.blu.org. (29)
20:08:55.470446 arp who-has 192.168.1.99 tell 192.168.1.3

So it looks like there's no answer.

The tcpdump of eth0 repeats the following a few times:
20:30:23.589460 IP dsl092-068-235.bos1.dsl.speakeasy.net > 
ns-legacy.speakeasy.net: ICMP host dsl092-068-235.bos1.dsl.speakeasy.net 
unreachable, length 91
20:30:25.573450 IP dsl092-068-235.bos1.dsl.speakeasy.net.naap > 
ns-legacy.speakeasy.net.domain:  51819+ A? www.blu.org. (29)
20:30:25.574190 IP dsl092-068-235.bos1.dsl.speakeasy.net.qubes > 
dns.nyc1.speakeasy.net.domain:  59122+ A? www.blu.org. (29)
20:30:25.574406 IP dsl092-068-235.bos1.dsl.speakeasy.net.esbroker > 
ns-legacy.speakeasy.net.domain:  53384+ AAAA? www.blu.org. (29)
20:30:25.574556 IP dsl092-068-235.bos1.dsl.speakeasy.net.re101 > 
dns.nyc1.speakeasy.net.domain:  58376+ AAAA? www.blu.org. (29)
20:30:25.593731 IP dns.nyc1.speakeasy.net.domain > 
dsl092-068-235.bos1.dsl.speakeasy.net.qubes:  59122 2/0/0 CNAME[|domain]
20:30:25.601361 IP dns.nyc1.speakeasy.net.domain > 
dsl092-068-235.bos1.dsl.speakeasy.net.re101:  58376 1/0/0 CNAME[|domain]
20:30:25.701926 IP ns-legacy.speakeasy.net.domain > 
dsl092-068-235.bos1.dsl.speakeasy.net.naap:  51819 2/0/0 CNAME[|domain]
20:30:25.705868 IP ns-legacy.speakeasy.net.domain > 
dsl092-068-235.bos1.dsl.speakeasy.net.esbroker:  53384 1/0/0 CNAME[|domain]
20:30:28.595282 IP dsl092-068-235.bos1.dsl.speakeasy.net > 
dns.nyc1.speakeasy.net: ICMP host dsl092-068-235.bos1.dsl.speakeasy.net 
unreachable, length 91
20:30:28.595294 IP dsl092-068-235.bos1.dsl.speakeasy.net > 
ns-legacy.speakeasy.net: ICMP host dsl092-068-235.bos1.dsl.speakeasy.net 
unreachable, length 107
20:30:28.595303 IP dsl092-068-235.bos1.dsl.speakeasy.net > 
ns-legacy.speakeasy.net: ICMP host dsl092-068-235.bos1.dsl.speakeasy.net 
unreachable, length 91

That's that "ICMP host dsl092-068-235.bos1.dsl.speakeasy.net 
unreachable" again.

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.