[CUWiN-Dev] Not routing to a connected user... missing something?
Rob Simmons
robsimmons at gmail.com
Wed Apr 5 18:25:55 CDT 2006
Just wtower (192.168.4.3) and stower (192.168.4.6); that's never caused any
issues before.
Let me know if you want the archived /var/log/daemon as well.
- Rob
-----Original Message-----
From: David Young [mailto:dyoung at pobox.com]
Sent: Wednesday, April 05, 2006 5:54 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 05:44:51PM -0500, Rob Simmons wrote:
> This is the output from several successive calls, first three for 252 and
> then the last two for 254
It is strange that the route to 10.20.21.252 is different from
10.20.21.254 route. Send me /var/db/linkstates and /var/log/daemon
from wtower.
Do you have any nodes connected to each other through their ethernet
ports?
Dave
>
>
> root at wtower # route -n get 10.20.21.252
>
> route to: 10.20.21.252
>
> destination: 10.20.21.0
>
> mask: 255.255.255.0
>
> gateway: 169.254.233.19
>
> local addr: 169.254.253.114
>
> interface: ath0
>
> flags: <UP,GATEWAY,DONE,PROTO1>
>
> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu
> expire
>
> 0 0 0 0 0 0 0
> 0
>
> root at wtower # route -n get 10.20.21.252
>
> route to: 10.20.21.252
>
> destination: 10.20.21.0
>
> mask: 255.255.255.0
>
> gateway: 169.254.241.179
>
> local addr: 169.254.253.114
>
> interface: ath0
>
> flags: <UP,GATEWAY,DONE,PROTO1>
>
> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu
> expire
>
> 0 0 0 0 0 0 0
> 0
>
> root at wtower # route -n get 10.20.21.252
>
> route to: 10.20.21.252
>
> destination: 10.20.21.0
>
> mask: 255.255.255.0
>
> gateway: 169.254.241.179
>
> local addr: 169.254.253.114
>
> interface: ath0
>
> flags: <UP,GATEWAY,DONE,PROTO1>
>
> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu
> expire
>
> 0 0 0 0 0 0 0
> 0
>
> root at wtower # route -n get 10.20.21.254
>
> route to: 10.20.21.254
>
> destination: 10.20.21.254
>
> gateway: 169.254.233.19
>
> local addr: 169.254.253.114
>
> interface: ath0
>
> ^[[A flags: <UP,GATEWAY,HOST,DONE,PROTO1>
>
> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu
> expire
>
> 0 0 0 0 0 0 0
> 0
>
> root at wtower # route -n get 10.20.21.254
>
> route to: 10.20.21.254
>
> destination: 10.20.21.254
>
> gateway: 169.254.233.19
>
> local addr: 169.254.253.114
>
> interface: ath0
>
> flags: <UP,GATEWAY,HOST,DONE,PROTO1>
>
> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu
> expire
>
> 0 0 0 0 0 0 0
> 0
>
>
>
> -----Original Message-----
> From: David Young [mailto:dyoung at pobox.com]
> Sent: Wednesday, April 05, 2006 5:09 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:39:50PM -0500, Rob Simmons wrote:
>
> > 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
>
> >
>
>
>
> Those paths should be identical. Please send output from
>
>
>
> route -n get 10.20.21.254
>
> and
>
> route -n get 10.20.21.252
>
>
>
> Dave
>
>
>
> --
>
> David Young OJC Technologies
>
> dyoung at ojctech.com Urbana, IL * (217) 278-3933
>
--
David Young OJC Technologies
dyoung at ojctech.com Urbana, IL * (217) 278-3933
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkstates
Type: application/octet-stream
Size: 41958 bytes
Desc: not available
Url : http://lists.chambana.net/mailman/archive/cu-wireless-dev/attachments/20060405/7003c4f6/linkstates-0001.obj
More information about the CU-Wireless-Dev
mailing list