RE: [SLE] Multicast Problem with Suse 9.2
Hi there, I installed Suse 9.1 for testing purposes, and using exactly the same network configuration, issued ping command, and got response from all computers from the same network without Suse 9.2, including my own computer. -----Original Message----- From: Hugo Veiga [mailto:hasv@mega.ist.utl.pt] Sent: Tuesday, January 18, 2005 22:30 To: Suse-Linux-E@Suse. Com Subject: [SLE] Multicast Problem with Suse 9.2 This is repeated, sorry, this is really important. Hi I use Suse 9.2 on my notebook. Issuing "ping 224.0.0.1" on one computer from the same network (switch), my computer does not respond to the multicast packets. The firewall is turned off, and all the computers ip's are assigned by DHCP. What's the problem? Thx in advance
Today at 1:07pm, Hugo Veiga wrote:
Hi there, I installed Suse 9.1 for testing purposes, and using exactly the same network configuration, issued ping command, and got response from all computers from the same network without Suse 9.2, including my own computer.
-----Original Message----- From: Hugo Veiga [mailto:hasv@mega.ist.utl.pt] Sent: Tuesday, January 18, 2005 22:30 To: Suse-Linux-E@Suse. Com Subject: [SLE] Multicast Problem with Suse 9.2
I use Suse 9.2 on my notebook. Issuing "ping 224.0.0.1" on one computer from the same network (switch), my computer does not respond to the multicast packets.
The firewall is turned off, and all the computers ip's are assigned by DHCP.
What's the problem?
Perhaps it would help if you gave us more information about what you're trying to do: What is your intended application? (Surely not ping.) Why are you using multicast addresses for ping, for example? Also, can you provide output from "ifconfig" and "netstat -rn" for the systems where pings work and where they don't? Jim
Jim Cunning wrote:
Today at 1:07pm, Hugo Veiga wrote:
Hi there, I installed Suse 9.1 for testing purposes, and using exactly the same network configuration, issued ping command, and got response from all computers from the same network without Suse 9.2, including my own computer.
-----Original Message----- From: Hugo Veiga [mailto:hasv@mega.ist.utl.pt] Sent: Tuesday, January 18, 2005 22:30 To: Suse-Linux-E@Suse. Com Subject: [SLE] Multicast Problem with Suse 9.2
I use Suse 9.2 on my notebook. Issuing "ping 224.0.0.1" on one computer from the same network (switch), my computer does not respond to the multicast packets.
The firewall is turned off, and all the computers ip's are assigned by DHCP.
What's the problem?
Perhaps it would help if you gave us more information about what you're trying to do: What is your intended application? (Surely not ping.) Why are you using multicast addresses for ping, for example?
Also, can you provide output from "ifconfig" and "netstat -rn" for the systems where pings work and where they don't?
Jim
Hi, By covention, the multicast address 224.0.0.1 is reserved for testing purposes, all machines with multicast capabilities, should respond to 224.0.0.1 requests. I must make 4 robots comunicate with eachother using multicast. If i had the robots in my posession i would test the code right as is... but all i have is 4 notebooks that will be using Suse 9.2 and as a simple test they won't respond to ping as by convention they should. The intention is for later create a multicast group to used with the robots. But i ask, if they won't respond to 224.0.0.1, will they respond to any other group? ifconfig output: eth0 Link encap:Ethernet HWaddr 00:02:3F:BD:17:58 inet addr:10.0.100.246 Bcast:10.0.255.255 Mask:255.255.0.0 inet6 addr: fe80::202:3fff:febd:1758/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:1947 errors:0 dropped:0 overruns:0 frame:0 TX packets:348 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:289901 (283.1 Kb) TX bytes:31831 (31.0 Kb) Interrupt:11 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:30 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1956 (1.9 Kb) TX bytes:1956 (1.9 Kb) netstat -rn output: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 10.0.0.254 0.0.0.0 UG 0 0 0 eth0 netstat -g output: IPv6/IPv4 Group Memberships Interface RefCnt Group --------------- ------ --------------------- lo 1 ALL-SYSTEMS.MCAST.NET eth0 1 ALL-SYSTEMS.MCAST.NET lo 1 ipv6-allnodes eth0 1 ff02::1:ffbd:1758%3221187208 eth0 1 ipv6-allnodes eth1 1 ipv6-allnodes sit0 1 ipv6-allnodes Hope this helps you, and helps me. Hugo Veiga
Today at 6:20pm, Hugo Veiga wrote:
Jim Cunning wrote:
Today at 1:07pm, Hugo Veiga wrote:
I use Suse 9.2 on my notebook. Issuing "ping 224.0.0.1" on one computer from the same network (switch), my computer does not respond to the multicast packets.
The firewall is turned off, and all the computers ip's are assigned by DHCP.
What's the problem?
[...]
ifconfig output:
eth0 Link encap:Ethernet HWaddr 00:02:3F:BD:17:58 inet addr:10.0.100.246 Bcast:10.0.255.255 Mask:255.255.0.0 inet6 addr: fe80::202:3fff:febd:1758/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 [...] Two other things you could check:
1. Be sure multicast is configured in the kernel: # zcat /proc/config.gz | grep MULTICAST CONFIG_IP_MULTICAST=y 2. Verify ping are going out the expected interface ping -I eth0 224.0.0.1 Run ethereal on the originating PC and verify the source IP address. The destination ethernet MAC address should be 01:00:5e:00:00:01 Jim
participants (2)
-
Hugo Veiga
-
Jim Cunning