Ubuntu Multicast packet bug

Bug #690026 reported by Mayank Tripathi
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am using Kubuntu 10.10 for multicast data packets. I am sending multicast data packets from a windows machine which is listened for on my Kubuntu machine.
With wireshark I have confirmed that the packets are reaching the Kubuntu machine. Also I have confirmed on the windows machine of my membership addition to the multicast broadcast.

However, my c++ code is blocking on a receive from (recvfrom) function call, but my code is not receiving the data packets at all.
I tried a lot of settings to get it to work. After a day of looking, I found that flushing the ip tables, turning of the firewall and making my code listen on INADDR_ANY, then only does it work, but if we Bind to a particular IP, it does not work.
I think this is a bug because the code runs on the windows machine as is.
Also, I need to bind to aparticular IP since my LAN card has multiple IPs and I also have multiple NICs.

Is there a way to make ti work with binding and possibly have this bug fixed in Ubuntu/Kubuntu?

Revision history for this message
Mayank Tripathi (makdt) wrote :

Following settings also done

1) sudo iptables --flush
2) CONFIG_IP_MULTICAST=y
3) echo 1 > /proc/sys/net/ipv4/ip_forward
4) net.ipv4.ip_forward = 1

in /etc/sysctl.conf
-------------------------------------------------------------------------------------------------------------------------------
# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
# Turn on Source Address Verification in all interfaces to
# prevent some spoofing attacks
net.ipv4.conf.default.rp_filter=0
net.ipv4.conf.all.rp_filter=0

# Uncomment the next line to enable TCP/IP SYN cookies
# See http://lwn.net/Articles/277146/
# Note: This may impact IPv6 TCP sessions too
#net.ipv4.tcp_syncookies=1

# Uncomment the next line to enable packet forwarding for IPv4
net.ipv4.ip_forward=1

# Uncomment the next line to enable packet forwarding for IPv6
# Enabling this option disables Stateless Address Autoconfiguration
# based on Router Advertisements for this host
net.ipv6.conf.all.forwarding=1

###################################################################
# Additional settings - these settings can improve the network
# security of the host and prevent against some network attacks
# including spoofing attacks and man in the middle attacks through
# redirection. Some network environments, however, require that these
# settings are disabled so review and enable them as needed.
#
# Do not accept ICMP redirects (prevent MITM attacks)
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_redirects = 0
# _or_
# Accept ICMP redirects only for gateways listed in our default
# gateway list (enabled by default)
# net.ipv4.conf.all.secure_redirects = 1
#
# Do not send ICMP redirects (we are not a router)
#net.ipv4.conf.all.send_redirects = 0
#
# Do not accept IP source route packets (we are not a router)
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_source_route = 0
#
# Log Martian Packets
#net.ipv4.conf.all.log_martians = 1
#
---------------------------------------------------------------------------------

Revision history for this message
Harshal Borade (harshal-borade) wrote :

I am facing the same issue, spent a few sleepless nights tried the above things, had been binding to a specific IP address.
Though the problem is resolved to (an extent i would say) by binding to IADDR_ANY but is not an acceptable solution in my current project, the machine in production has multiple NICs and binding IADDR_ANY is not favorable.
Please also let me know if any resolution was found.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: maverick
tags: added: kubuntu
Revision history for this message
penalvch (penalvch) wrote :

Mayank Tripathi, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.