[CUWiN-Dev] Troublesome Bouncing Default Route

[Rob Simmons]

I will send you that information definitely when I see it again. Right now
the CNT Lawndale network is set up like:

Lots of nodes on Channel 1 
|
Stower gateway 
              \  
               Switch ----- Router ---- Internet
              /
Wtower gateway
|
Lots of nodes on Channel 11

In other words, two gateways but on different meshes (the two sides of the
network can talk through the local interfaces of the two gateways). This
usually works very well.

However, when you asked I realized that it is possible that this event has a
relationship with the event that happened a couple of times where a WAP got
the node plugged into the DHCP-serving side and so a node that shouldn't
have been a gateway thought it was one for awhile. The circular default
route problem definitely persisted long after the gateway glitch was
corrected, however.

The cuw_config file seems to indicate that nodes can be forced into
gateway-mode or node-mode, and all of our cuw_config files are set to
"both." Is that currently a to-be implemented feature, or is there a word to
replace "both" with to force the node to not act like a gateway?

 - Rob

-----Original Message-----
From: cu-wireless-dev-bounces at lists.cuwireless.net
[mailto:cu-wireless-dev-bounces at lists.cuwireless.net] On Behalf Of David
Young
Sent: Saturday, March 04, 2006 5:43 PM
To: 'CUWiN Development'
Subject: Re: [CUWiN-Dev] Troublesome Bouncing Default Route

On Sat, Mar 04, 2006 at 04:01:21PM -0600, Rob Simmons wrote:
> I have noticed this problem a couple of times and have always fixed it by
> just involved rebooting lots of things and hoping it would sort itself
out,
> but when I got a call this morning about it happening yet again, I figured
I
> would raise it here because it seems to be a specific and fairly
reoccuring
> problem.
> 
> The two nodes in question here - 10.0.233.27 and 10.0.241.164, are both
> running cuwin 0.6 version 3787 (cnt subversion 3454). They have a
> connection, but as should be seen from the routing tables, their "best"
> connection to "most of the rest of the network" at this time is through
> 10.0.241.196. They would, on very rare occasions, connect to the rest of
the
> network through each other, but not commonly.

Next time this happens, send /var/db/linkstates and /var/log/daemon.

How many routers on this network are connected to the Internet?

Dave

-- 
David Young             OJC Technologies
dyoung at ojctech.com      Urbana, IL * (217) 278-3933
_______________________________________________
CU-Wireless-Dev mailing list
CU-Wireless-Dev at lists.cuwireless.net
http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev