[CUWiN-Dev] Fwd: rev 4074...

[tom]

----- Original Message ----- 
From: "David Young" <dyoung at pobox.com>
To: <cu-wireless-dev at lists.cuwireless.net>
Sent: Friday, July 14, 2006 12:38 PM
Subject: Re: [CUWiN-Dev] Fwd: rev 4074...


> On Fri, Jul 14, 2006 at 12:16:18PM -0500, dan blah wrote:
>> ---------- Forwarded message ----------
>> From: daniel <daniel at cuwireless.net>
>> Date: Jul 14, 2006 11:56 AM
>> Subject: rev 4074...
>> To: David Young <dyoung at pobox.com>
>>
>>
>> seems on the 3 boxes i have access to there is some route issues.
>>
>>
>> --
>> Daniel# ifconfig ath0
>> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>        ssid cuwireless.net
>>        powersave off
>>        bssid 9e:03:a6:b3:37:2b chan 11
>>        address: 00:02:6f:20:ed:46
>>        media: IEEE802.11 autoselect mode 11b adhoc
>>        status: active
>>        inet 10.0.237.70 netmask 0xffffffff broadcast 10.0.237.70
>>        inet alias 169.254.237.70 netmask 0xffff0000 broadcast
>>        169.254.255.255
>>        inet6 fe80::202:6fff:fe20:ed46%ath0 prefixlen 64 scopeid 0x1
>>        inet6 fdb4:542d:dc11:ed46:202:6fff:fe20:ed46 prefixlen 64
>> # ifconfig sip0
>> sip0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>        address: 00:00:24:c2:b1:50
>>        media: Ethernet autoselect (100baseTX full-duplex)
>>        status: active
>>        inet 10.177.80.254 netmask 0xffffff00 broadcast 10.177.80.255
>>        inet alias 192.168.16.125 netmask 0xffffff00 broadcast 
>> 192.168.16.255
>>        inet6 fe80::200:24ff:fec2:b150%sip0 prefixlen 64 scopeid 0x2
>>        inet6 fdb4:542d:dc11:b150:200:24ff:fec2:b150 prefixlen 64
>> # route -n get default
>>   route to: default
>> destination: default
>>       mask: default
>>    gateway: 192.168.16.254
>> local addr: 10.177.80.254
>>  interface: sip0
>>      flags: <UP,GATEWAY,DONE,STATIC>
>> recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu
>> expire
>>       0         0         0         0         0         0         0
>>       0
>
> This node is getting a DHCP lease with a default route.  It is acting
> just as expected.  It must be plugged into the same ethernet segment as
> a DHCP server.
>
> Dave
>

I think what must have happened is that the people moving in to the 115 W. 
Main building trying to get temporary internet access until their T1 arrives 
must have plugged something in that had a DHCP server on it. So ironically 
enough when I called them to let them know that while I had resolved the 
hardware issue I had spoken of earlier, there was still a software problem, 
they were actually causing it. Looking at the network remotely now 
everything looks great - all 4 of the nodes in range are running 0.7.0rc1 
and have internet access (including the library, once again). They must have 
unplugged whatever it was at 115 W. Main that was causing problems, unless 
one of us did something.

Tom