[CUWiN-Dev] Not routing to a connected user... missing something?
Rob Simmons
robsimmons at gmail.com
Wed Apr 5 16:39:50 CDT 2006
It's pretty simple, actually. And as a parenthetical note, the laptop node
is running CUWiN r3812, all other nodes in question are running CUWiN r3787.
>From the west tower:
root at wtower # traceroute 10.20.21.254
traceroute to 10.20.21.254 (10.20.21.254), 64 hops max, 40 byte packets
1 10.0.241.220 (10.0.241.220) 10.366 ms 3.558 ms 2.459 ms
2 10.20.21.254 (10.20.21.254) 4.407 ms 21.048 ms 9.466 ms
root at wtower # traceroute 10.20.21.252
traceroute to 10.20.21.252 (10.20.21.252), 64 hops max, 40 byte packets
1 10.0.233.19 (10.0.233.19) 2.284 ms 2.142 ms 6.210 ms
2 10.0.106.141 (10.0.106.141) 3.454 ms 96.409 ms 168.923 ms
3 * * *
4 * * *
5 * *^C
>From the laptop node:
root at 10.0.106.141 # traceroute 10.20.21.252
traceroute to 10.20.21.252 (10.20.21.252), 64 hops max, 40 byte packets
1 10.20.21.252 (10.20.21.252) 1.268 ms 1.240 ms 1.191 ms
root at 10.0.106.141 # traceroute wtower
traceroute to wtower (10.0.253.114), 64 hops max, 40 byte packets
1 10.0.241.220 (10.0.241.220) 4.010 ms 11.117 ms 5.952 ms
2 wtower (10.0.253.114) 11.137 ms 11.553 ms 6.084 ms
For good measure (again from the laptop node):
root at 10.0.106.141 # route4 | head -n 45
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu
Interface
default 169.254.241.220 UG1 0 1733 - ath0
10/16 127.0.0.1 UGRS 0 0 33192 lo0
10.0.106.141/32 link#3 UC 0 0 - ath0
10.0.155.183 169.254.241.220 UGH1 0 0 - ath0
10.0.155.186 169.254.233.19 UGH1 0 0 - ath0
10.0.233.15 169.254.233.19 UGH1 0 0 - ath0
10.0.233.19 169.254.233.19 UGH1 0 0 - ath0
10.0.233.20 169.254.233.19 UGH1 0 0 - ath0
10.0.233.21 169.254.233.19 UGH1 0 0 - ath0
10.0.233.27 169.254.233.19 UGH1 0 0 - ath0
10.0.233.54 169.254.233.19 UGH1 0 0 - ath0
10.0.233.62 169.254.241.220 UGH1 0 0 - ath0
10.0.233.63 169.254.233.19 UGH1 0 0 - ath0
10.0.233.64 169.254.241.220 UGH1 0 0 - ath0
10.0.233.67 169.254.241.220 UGH1 0 0 - ath0
10.0.236.151 169.254.241.220 UGH1 0 0 - ath0
10.0.236.155 169.254.233.19 UGH1 0 0 - ath0
10.0.236.156 169.254.233.19 UGH1 0 0 - ath0
10.0.236.158 169.254.233.19 UGH1 0 0 - ath0
10.0.236.159 169.254.233.19 UGH1 0 0 - ath0
10.0.241.164 169.254.233.19 UGH1 0 0 - ath0
10.0.241.170 169.254.233.19 UGH1 0 0 - ath0
10.0.241.171 169.254.233.19 UGH1 0 0 - ath0
10.0.241.172 169.254.233.19 UGH1 0 0 - ath0
10.0.241.175 169.254.233.19 UGH1 0 0 - ath0
10.0.241.179 169.254.241.179 UGH1 1 594 - ath0
10.0.241.196 169.254.233.19 UGH1 0 0 - ath0
10.0.241.197 169.254.241.220 UGH1 0 0 - ath0
10.0.241.220 169.254.241.220 UGH1 0 312 - ath0
10.0.248.77 169.254.233.19 UGH1 0 0 - ath0
10.0.253.112 169.254.241.220 UGH1 0 0 - ath0
10.0.253.114 169.254.233.19 UGH1 0 58 - ath0
10.0.253.115 169.254.233.19 UGH1 0 0 - ath0
10.20.21/24 link#1 UC 2 0 - ex0
10.20.21.252 00:0c:f1:ae:f3:8c UHLc 1 71478 - ex0
10.20.21.253 00:11:50:a3:67:8a UHLc 0 20 - ex0
10.64.136/24 169.254.241.220 UG1 0 0 - ath0
10.64.136.254 169.254.241.220 UGH1 0 0 - ath0
10.64.168/24 169.254.241.220 UG1 0 0 - ath0
10.64.168.254 169.254.241.220 UGH1 0 0 - ath0
10.64.172/24 169.254.233.19 UG1 0 0 - ath0
-----Original Message-----
From: David Young [mailto:dyoung at pobox.com]
Sent: Wednesday, April 05, 2006 4:28 PM
To: Rob Simmons
Cc: wcn-tech at cntwireless.org; 'CUWiN Development'
Subject: Re: [CUWiN-Dev] Not routing to a connected user... missing
something?
On Wed, Apr 05, 2006 at 04:19:58PM -0500, Rob Simmons wrote:
> This is a (probably not very good) slice of the network topology that I'm
> dealing with, but I don't know if that element's too important. I
currently
> have someone connected to a node (laptop, 10.0.106.141) that can connect
two
> nodes which both connect to the tower in some number of hops, often just
0.
>
> West Tower <-> (0 or more links) <-> 10.0.241.179 <------> 10.0.106.141
> \--------> 10.0.241.220 <-/
>
> The sip0 interface on 10.0.106.141 is 10.20.21.254, and the IP address of
> the user's machine is 10.20.21.252. I can ping 10.20.21.252 from the node
> only - they seemed to have some success pinging from their computer out to
> 10.0.241.220 and other nearby nodes, but they definitely could not get out
> to the network, even though when I had left the node the night before it
> worked fine.
>
> It doesn't seem to be their computer's fault, since I can ping it locally,
> and she claimed to even be receiving pings back from nearby nodes when I
> talked it over with her on the phone.
>
> When I try to ping 10.20.21.254 (the local interface of the node), it
works
> from pretty much anywhere. In every routing table I checked the next-hop
> entries for 10.20.21.254 and 10.20.21/24 were the same.
>
> I confirmed that I could ping other computers remotely from elsewhere
around
> the network, but when I try to ping 10.20.21.252 from anywhere besides the
> node it is connected to, I get lots and lots and lots of silence, but
> occasionally some messages in the style of:
>
> root at 10.0.241.220 # ping -R 10.20.21.252
> PING 10.20.21.252 (10.20.21.252): 56 data bytes
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> 76 bytes from 10.0.233.19: Time To Live exceeded for icmp_seq=50
> ping: sendto: No buffer space available
> 76 bytes from 10.0.233.19: Time To Live exceeded for icmp_seq=51
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> 76 bytes from 10.0.241.179: Time To Live exceeded for icmp_seq=455
I am curious what 'traceroute -n 10.20.21.252' and 'traceroute -n
10.20.21.254' say.
Dave
--
David Young OJC Technologies
dyoung at ojctech.com Urbana, IL * (217) 278-3933
More information about the CU-Wireless-Dev
mailing list