[CUWiN-Dev] HSLSD Not Sending HSLS(9191) Packets

[Socrates Socrates]

Hi Matthew, David

At last, well problem solved.
The problem was that function beacon_rx_socket()in ssrx/ssrv.c. bound
address 0.0.0.0 to port 9191. However, the was no prior call to setsockopt()
with *SO_REUSEADDR.*
So beacon_tx_socket() failed to bind and somehow it was using the
"arbitrary" port, instead of 9191, to which my Linux HSLSD was sending it's
packets. So all I did was to call setsocketopt with the SO_REUSEADDR option
and it works fine. Well at least that's how I solved the problem.

Now my "netstat -nl" is the same as the CUWiN box and looks like this:

tcp        0      0 127.0.0.1:9292          0.0.0.0:*               LISTEN
udp        0      0 169.254.237.50:9191     0.0.0.0:*
udp        0      0 0.0.0.0:9191            0.0.0.0:*

One last (I hope) question. How do I tell hsls to advertize my lan address?
My laptop has eth1(wireless) address 169.254.237.50 and Lan eth0 address
192.168.12.1.
>From the CuwWiN box I can't reach the Latop's lan(192....). I
 believe it has to be on the ./hslsd command line  but I can't get it tight.

Thanks your the help guys.

Kind regards

Lawrence


On 1/15/07, David Young <dyoung at pobox.com> wrote:
>
> On Fri, Jan 12, 2007 at 09:08:43AM +0200, Socrates Socrates wrote:
> > Hi Dave
> >
> > Thanks for the response. Here's what I found, on my Linux the 9191 port
> is
> > associated with address 0.0.0.0 and not the interface address (
> > 169.254.237.50) as is shown on CUWiN box.
> >
> > Below are the outputs for netstat -ln and also the hsls debug output on
> > Linux.
> >
> > netstat -ln on my linux is (ipv4):
> > udp        0      0 0.0.0.0:9191            0.0.0.0:*
>
> > netstat -ln on CUWiN is (ipv4):
> > udp        0      0  10.177.52.254.9191     *.*
> > udp        0      0  169.254.10.168.9191    *.*
> > udp        0      0  *.9191                 *.*
>
> Linux is missing some sockets.  I don't understand how those sockets
> could be missing, yet we see no errors or warnings in your logs.
> Perhaps loglib_warn() is not working?  Make sure that it works, it will
> help you a lot to see what it will tell you. :-)
>
> > 20070112064854 etx_txbeacon_cb: 169.254.237.50
> > 20070112064854 TX 68B from 169.254.237.50 to 224.0.0.2 with jitter
>
> Do you see this packet transmitted if you run tcpdump on both the sender
> and the receiver?
>
> 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/20070115/5194878e/attachment.html