Mesh networking issue "Can't bind send socket: address already in use"

WhiskeyTangoFoxtrot · 02-23-2009, 01:34 PM

G'day

I am currently trying to get a B.A.T.M.A.N mesh network up and running. the thing uses UDP port 4305 for broadcasting to nearby nodes and it seems this port is closed or used by something else.

now i have tried to open this port with commands like

Code:

iptables -A INPUT -p udp --dport 4305 -j ACCEPT
iptables -A OUTPUT -p udp --dport 4305 -j ACCEPT

it still gives me the same error saying the socket cannot connect.any way for me to scan that udp port, see what is blocking it and open the thing up ?

thanks.

bathory · 02-23-2009, 02:11 PM

Run any of the following commands:

Code:

netstat -unapl|grep 4305
fuser -v -n udp 4305

to find what's listening on that port.

Regards

WhiskeyTangoFoxtrot · 02-23-2009, 02:21 PM

thanks for the quick reply.

interesting result, netstat says the only 2 things listening are batmand, the BATMAN daemon which does the mesh networking. using fuser shows no output.

Quote:

udp 0 0 192.168.10.255:4305 0.0.0.0:* 3470/batmand
udp 0 0 192.168.10.10:4305 0.0.0.0:* 3470/batmand

is it possible the two are interfering with each other ? heres an extract of what happens when i try to tell BATMAN to scan for neighboring nodes

Quote:

root@fit-4:/home/fit# batmand -d 1 wlan0
Deleting default route via unknown (table 67)
Deleting default route via unknown (table 67)
Error - can't bind send socket: Address already in use
Interface deactivated: wlan0
Not using interface wlan0 (retrying later): interface not active
B.A.T.M.A.N. 0.3.1 (compatibility version 5)
debug level: 1
BOD
Originator (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. 0.3.1, MainIF/IP: wlan0/192.168.10.10, UT: 0d 0h 0m]
No batman nodes in range ...
EOD
BOD
Originator (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. 0.3.1, MainIF/IP: wlan0/192.168.10.10, UT: 0d 0h 0m]
No batman nodes in range ...
EOD

and it goes on.

bathory · 02-23-2009, 04:55 PM

I don't know how batman works, but you can try to stop/kill batmand before running the "batmand -d 1 wlan0" command. This way when you run the above command it will not complain and will start listening on udp port 4305. The batmand pid is 3470, thus you can also use:

Code:

kill -9 3470

WhiskeyTangoFoxtrot · 02-24-2009, 10:38 AM

interesting suggestion bathory, it doesnt seem to give me the socket error anymore when I try scanning for nearby mesh nodes. will get to the lab ASAP and test it out with the other nodes and post back on results.

thanks again.

Update:Success. Thanks to both of you guys.What i needed was :

netstat -unapl|grep 4305

based on the output i simply did:

kill -9 <whatever number was given by prev step>