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

[Socrates Socrates]

Hi David;

With regard to HSLS linux port not receiving packets from CUWiN box, I've
gotten libevent-1.0c and libevent-0.8a .
I tested these versions with the old code and they work just fine. I also
tried these versions on the latest code with no change in the behaviour of
the latest code.
So I am pretty much certain that libevent is not the issue.

I noticed, for example, that the *struct hsls_interface* passed to
EVTIMER_SET in function hsls_interface_create is much lager in the new code
than on the older code.
Is there anything in the 3rd argument of EVTIMER_SET (and/or related macros)
that could possibly affect events not being detected?

I believe that the arguments/structures past to EVTIMER_SET (and/or related
macros)  are most likely the cause of the problem.
Trouble is the structures are so big to know exactly which member of the
structure to check out.

What is the event that should be detected (or occur) after some timeout (if
any)?

Oh, while running the new code, I do *netstat -nl* and I noticed the Recv-Q
counter associated with address:Port (0.0.0.0:9191) incrementing, showing
that the packets from CUWiN box do arrive but do not get collected.


Regards;

Lawrence

On 2/22/07, David Young <dyoung at pobox.com> wrote:
>
> 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.19292",
> > 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
> _______________________________________________
> CU-Wireless-Dev mailing list
> CU-Wireless-Dev at lists.cuwireless.net
> http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.chambana.net/mailman/archive/cu-wireless-dev/attachments/20070307/019ea6e9/attachment.htm