Is anything listening on those ports already? A failure to bind to a port is usually one of two things - something is already using the port, or the user you're running as doesn't have sufficient permissions to open a listener on that port.
 
Since flow-fanout also does source address spoofing that may present another permissions issue. Does the user you're running as have rights to spoof the source addr?
 
To test for the permissions issue, see if you can run flow-fanout as root. If so, then you know it's a permission issue.
 
As for the listener issue, netstat -an will show the existing open UDP ports.
 
 
 
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wright, Brandt
Sent: Friday, August 11, 2006 9:21 AM
To: [email protected]
Subject: [Flow-tools] Trouble getting flow-fanout to work

When I run the following command:

 

flow-fanout 10.45.68.38/0/8924 0/0/6301 10.32.4.44/162.48.52.59/6301

 

The messages below show up in my syslog…

 

Aug 10 20:24:25 mopsnftemp flow-fanout[25656]: bind(xmit): Cannot assign requested address

Aug 10 20:29:40 mopsnftemp flow-fanout[25680]: bind(xmit): Cannot assign requested address

Aug 10 20:48:13 mopsnftemp flow-fanout[26309]: bind(xmit): Cannot assign requested address

Aug 10 20:48:19 mopsnftemp flow-fanout[26325]: bind(xmit): Cannot assign requested address

Aug 10 20:53:08 mopsnftemp flow-fanout[26725]: bind(xmit): Cannot assign requested address

Aug 10 21:01:45 mopsnftemp flow-fanout[26791]: bind(xmit): Cannot assign requested address

Aug 10 21:02:14 mopsnftemp flow-fanout[26795]: bind(xmit): Cannot assign requested address

Aug 10 21:02:44 mopsnftemp flow-fanout[26799]: bind(xmit): Cannot assign requested address

 

Anyone know what I am doing wrong?

 

Thanks in advance,

-Brandt

 

 

_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools

Reply via email to