similar to: Multicast routing

Laine I made the change and I can now ping across both bridges: br1 (192.168.0.0/24) and br1600 (192.168.1.0/24): br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet 192.168.0.110  netmask 255.255.255.0  broadcast 192.168.0.255         inet6 fe80::1e98:ecff:fe1b:276d  prefixlen 64  scopeid 0x20<link>         ether 1c:98:ec:1b:27:6d  txqueuelen 1000  (Ethernet)

Even more puzzling, I reverted back to the old configuration to confirm what I had seen and found that it works in one direction but not the other: i.e. from 192.168.0.110 to 192.168.0.120, but not the other way around. Must be something with my configuration....which I can follow up on. So, thanks again for your help. Richard On 12/3/19 11:36 AM, Richard Achmatowicz wrote: > Laine >

The testsuite that checks for mcast_max_groups functionality will need to generate IGMP and MLD packets with configurable number of (S,G) addresses. To that end, further extend igmpv3_is_in_get() and mldv2_is_in_get() to allow a list of IP addresses instead of one address. Signed-off-by: Petr Machata <petrm at nvidia.com> --- tools/testing/selftests/net/forwarding/lib.sh | 22

The testsuite that checks for mcast_max_groups functionality will need to wipe the added groups as well. Add helpers to build an IGMP or MLD packets announcing that host is leaving a given group. Signed-off-by: Petr Machata <petrm at nvidia.com> --- tools/testing/selftests/net/forwarding/lib.sh | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git

Hi, I have problem with multicast routing on my network. I tried mrouted and also pimd, but always same problem. When I set mrouted or pimd on one router, everything works fine, but when I start mrouted/pimd on another one, routing die. In moment when I start anorher mrouted/pimd /proc/net/ip_mr_cache is cleaned. My topology: gateway (no mrouted/pimd)

These functions will be helpful for other testsuites as well. Extract them to a common place. Signed-off-by: Petr Machata <petrm at nvidia.com> Reviewed-by: Ido Schimmel <idosch at nvidia.com> --- .../selftests/net/forwarding/bridge_mdb.sh | 49 ------------------- tools/testing/selftests/net/forwarding/lib.sh | 49 +++++++++++++++++++ 2 files changed, 49 insertions(+), 49

I need to send multicast traffic through a GRE tunnel between two Linux routers. The tunnel works for normal IP packets, but I can''t see how to make it work for multicast. Here''s the setup: 10.10.10.0/24 LAN-B--------------RtrB-------------RtrC--------------LAN-C 192.168.2.0/24 192.168.1.0/24 RtrB interfaces: eth0

Hi, Whilst doing some QA work on XORP on my desktop, which has fxp0 and msk0, fxp0 got totally hosed. I was running PIM-SM and IGMPv2 router-mode on the box at the time. I wonder if this is related to the problems with fxp multicast transmission I saw back in April. I'm a bit concerned about this as fxp is still a very widespread and useful network chip. I am running

I have a standard 3 interface shorewall setup and I want to receive multicast stuff from ''net'' -> ''loc''. This requires me, first, to do an IGMP join which involves 192.168.1.x -> 224.0.0.x being NATed out as the ''net'' interface''s IP address. Obviously replies have to be NATed back to ''loc'' addresses. Can

I am trying to set up my Shorewall box to forward multicast packets to my local net. I do have some problems with mrouted (see below), but I can join and add routes using smcroute. Multicast works when shorewall is disabled. I got a lot of help from the following. http://lists.shorewall.net/pipermail/shorewall-users/2005-January/016674.html I cannot get the multicast packets to pass the fw when

Currently we would still potentially suffer multicast packet loss if there is just either an IGMP or an MLD querier: For the former case, we would possibly drop IPv6 multicast packets, for the latter IPv4 ones. This is because we are currently assuming that if either an IGMP or MLD querier is present that the other one is present, too. This patch makes the behaviour and fix added in "bridge:

Hi Laine What you have suggested sounds eminently reasonable. Thanks for your advice. I'm going to give it a shot and report back. Richard On 11/27/19 1:38 PM, Laine Stump wrote: > On 11/26/19 11:07 PM, Richard Achmatowicz wrote: >> Hello >> >> I have a problem with attaching VMs to a VLAN interface. >> >> Here is my setup: I have several physical hosts

Hello list, Not sure if I am asking the question in the correct list. I am a newbie trying to get multicast routing to work on my linux 2.4 kernel. I am using usc pimd code. I have pimd which sets up the route in the kernel [ /tmp]# ip mroute show (22.22.22.1, 224.0.1.20) Iif: eth2 Oifs: eth1 [ /tmp]# I can see data packets arriving on eth2 [/tmp]# tethereal -i eth2 Capturing

Hi all, We want linux (ubuntu) with 2.6 kernel to act as multicast router and to pass multicast packets between different subnets. And linux machine as router has two network cards having two different subnets assigned onto. We first worked "sysctl -w net.ipv4.ip_forward=1" line on linux shell that made linux to work as unicast router. (like host, the multicast packets were discarded at

Hi, I have been reading: http://lartc.org/howto/lartc.multicast.html in effort to understand how to route multicast traffic and just joined the group. History: I am trying to multicast mpeg (using the videolan server) on a private network. The server side of the network is copper gigabit, which connects to one of those cheap fast Ethernet switches with a single gigabit uplink. The problem

well, once i figured out what to do it was easy. 1) install freebsd over linux. 2) recompile kernel with: option MROUTING 3) start mrouted 4) go get yourself a cold beer. you deserve it! thanks! -bob CONFIDENTIALITY NOTICE: The information in this electronic mail transmission contains confidential information intended only for the use of the individual or entity named above. If the

V3: drop debugging printk's update selinux perm table as well V2: drop patch 1/2, export ifindex directly Redesign netlink attributes Improve netlink seq check Handle IPv6 addr as well This patch exports bridge multicast database via netlink message type RTM_GETMDB. Similar to fdb, but currently bridge-specific. We may need to support modify multicast database too

I tried to close everything I had open and filter as best as I could.. but left random lines in just in case it helps. 172.16.5.230 is my local machine and *.33.235 is the server. This is a slow save.. 13:48:39.852340 (60) 001F5B35DB28 Broadcast UDP - Other Ports 172.16.5.93 172.16.5.255 00:04:53.922946 293.922946 13:48:39.852605 (60) 001F5B35DB28 USC-IANA

I am trying to get multicast traffic to traverse 3 different subnets call connected to the same linux router. This is primarily to get rendezvous/zeroconf services working for Macs on the network. Being able to experiment with the VideoLAN client''s multicasting abilities would be a bonus. I see that rendezvous sends out packets with a TTL of 1 and expects them back with a TTL of 255 so

Hi, Here are two, small feature changes I would like to submit to increase the usefulness of the multicast snooping of the bridge code. The first patch is an unaltered one I had submitted before, but since it got no feedback I'm resubmitting it here for net-next. With the recently added patch to disable snooping if there is no querier (b00589af + 248ba8ec05 + 8d50af4fb), it should be a safe