[CUWiN-Dev] Boatload of WRAP node problems

[David Young]

Seth,

Update on some of the issues you found:

On Wed, Aug 31, 2005 at 06:01:03PM -0500, David Young wrote:
> On Wed, Aug 31, 2005 at 03:21:51PM -0500, Seth Price wrote:
> > It looks like it is all HSLS traffic over both IPv4 and IPv6. I had  
> > thought that I had read somewhere that it only needed one hello per  
> > second, and I assumed that they were only sent over the wireless  
> > interface. Seems I was wrong.
> 
> Hellos have always been sent over the wire interface, too.  I do expect
> two Hellos per interface (one sent by IPv6, one sent by IPv4), but I did
> not expect four.
> 

I have fixed this on the hello-consolidation branch.  Now I see two Hellos
like I expect.  I am wary of pulling the changes up to the trunk just yet.

> > Should I head over to your office some time to work on the serial  
> > console part of it? It'll probably need to stay hooked up to it over  
> > night before it goes into whatever crash condition is the problem.  
> > Though I should probably figure out some serial console setup for  
> > myself, I've been needing one lately.
> 
> Now that we have a WRAP node in the office, I will try to duplicate
> the hang.

Haven't gotten around to that, yet.

> It occurred to me today that the ETX for a new adjacency may not
> be set to a middle or high value, so that new adjacencies look like
> super-desirable routes.  That would wreck havoc on the routing every
> time a node rebooted.  It would help to explain why your node would
> try to route through a northern node instead of taking a direct route
> southward to the Internet gateway.

Looks like the code DTRT, but looks don't count for much.

Dave

-- 
David Young             OJC Technologies
dyoung at ojctech.com      Urbana, IL * (217) 278-3933