[CUWiN-Dev] Progress towards HSLS LInux Port [from Latest Code base]

David Young dyoung at pobox.com
Thu Feb 22 01:12:45 CST 2007


On Wed, Feb 21, 2007 at 02:39:08PM +0200, Socrates Socrates wrote:
> Hi Dave;
> 
> I've resolved the last problem I had [Discussed in thread "HSLSD Not Sending
> HSLS(9191) Packets."].
> 
> Now the debug messages look this:
> 
> root at appletiser:/home/lawrence/work/latest_hsls/cuwin-0.7.0-src/src/hsls#
> ./run-hsls
> 20070221121114 hsls_server_create: created server 0x8091874
> 20070221121114 main: event(3) initialized
> 20070221121114 beacon_rx_socket: bound 0.0.0.0 port 9191
> 20070221121114 beacon_tx_socket: bound 169.254.237.50 port 9191
> 20070221121114 ERR RIB indicates 'connected'
> 20070221121114 rib_zpkt_header_pack: packed 1 fields in 3 bytes at
> 0xbf97118d
> 20070221121114 hsls_server_start: bound 127.0.0.1 9292
> 
> Questions:
> 1. Should I be concerned with the message "20070221121114 ERR RIB indicates
> 'connected'"? That is, Does ERR RIB indicates an error?

That is ok.  That means the HSLS daemon has connected to Zebra.

> After the message "20070221121114 hsls_server_start: bound 127.0.0.1 9292",
> the program hangs. Tracing leads me to event_loop() in 
> libevent-0.8a/event.c.
> 
> I assume at some point event_loop() should exit (which doesn't), if so:
> 1. What are the conditions/events that should cause this function to exit?

hsls_router_run() calls event_dispatch(), which repeatedly calls
event_loop(), forever, or until there are no more events scheduled, or
until there is an exception from which event_dispatch() cannot recover.
libevent has some documentation.  On NetBSD, there is a manual page.

BTW, I am using version 1.0c of libevent.  You may need a later version.

> 2. Are these conditions/events external to my system? In other words, the
> event would be say, receiving an hsls packet.

Right, one event is receiving a packet.

Dave

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


More information about the CU-Wireless-Dev mailing list