From Electron Cloud
| Line 1: | Line 1: | ||
* [http://www.hezmatt.org/~mpalmer/blog/general/severe_discomforts_the_joy_of_udp.html good explanation of problems with UDP on interfaces that have multiple IP addresses] and consequently why it's a good idea to bind separately to each interface's IP address | * [http://www.hezmatt.org/~mpalmer/blog/general/severe_discomforts_the_joy_of_udp.html good explanation of problems with UDP on interfaces that have multiple IP addresses] and consequently why it's a good idea to bind separately to each interface's IP address | ||
| + | * [http://www.abc.se/~m6695/udp.html trivial UDP server example] which binds to a port, receives packets and prints them out | ||
See what ports are bound: | See what ports are bound: | ||
| Line 6: | Line 7: | ||
Watch UDP traffic: | Watch UDP traffic: | ||
tcpdump -A -u port 9877 -i iface | tcpdump -A -u port 9877 -i iface | ||
| + | |||
| + | Modified version of the UDP server linked above, which sends replies: | ||
Revision as of 11:21, 24 February 2009
- good explanation of problems with UDP on interfaces that have multiple IP addresses and consequently why it's a good idea to bind separately to each interface's IP address
- trivial UDP server example which binds to a port, receives packets and prints them out
See what ports are bound:
netstat -lun
Watch UDP traffic:
tcpdump -A -u port 9877 -i iface
Modified version of the UDP server linked above, which sends replies: