That's actually a limitation on how multicast works. In usual circumstances, a router does not listen to multicasts not originating from the subnet its interface is connected to.
Could that be the reason why ampr-ripd multicast mode does not work for me? I always put the local address /32 on the tunnel interface. Maybe it would work when that is changed to /8 ?
Rob
I think ampr-ripd shouldn't care. It is the regular routing daemons/multicast clients that drop the data which does not fit, not the socket itself.
I also have a /32 interface which works as expected with multicast packets.
On 23.05.2017 20:48, Rob Janssen wrote:
(Please trim inclusions from previous messages) _______________________________________________
That's actually a limitation on how multicast works. In usual circumstances, a router does not listen to multicasts not originating from the subnet its interface is connected to.
Could that be the reason why ampr-ripd multicast mode does not work for me? I always put the local address /32 on the tunnel interface. Maybe it would work when that is changed to /8 ?
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Rob,
I'm curious, what Router OS are you using?
Also, do you have a destination IP firewall rule?
My tunl0 doesn't have an address, and my IP is assigned to a bridge. I've even used invalid and private addresses on tunl0, including an IP from 44.128.0.0/16. I've even ran ampr-ripd with NO 44 IP assigned to the device, it still works.
br-amprnet Link encap:Ethernet HWaddr <snip> inet addr:44.60.44.1 Bcast:44.60.44.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP RUNNING NOARP MULTICAST MTU:1480 Metric:1
As I understand, we have ampr-ripd compiled for:
- Debian/Ubuntu Linux (various CPUs) - BSD? - OpenWRT/LEDE (various CPUs)
Are there any other OSes running ampr-ripd?
- Lynwood KB3VWG
Lynwood.
"Are there any other OSes running ampr-ripd?"
VyOS too...
See: Re: [44net] AMPR + VyOS dated: Dec 12th 2016 19:55UTC
Best regards. Tom _ SP2L
All,
I've added the list of OSes so far to:
http://wiki.ampr.org/wiki/RIP#Availability.2FCompatibility
- Lynwood KB3VWG
On 05/23/2017 08:15 PM, lleachii--- via 44Net wrote:
(Please trim inclusions from previous messages) _______________________________________________ Rob,
I'm curious, what Router OS are you using?
Also, do you have a destination IP firewall rule?
My tunl0 doesn't have an address, and my IP is assigned to a bridge. I've even used invalid and private addresses on tunl0, including an IP from 44.128.0.0/16. I've even ran ampr-ripd with NO 44 IP assigned to the device, it still works.
br-amprnet Link encap:Ethernet HWaddr <snip> inet addr:44.60.44.1 Bcast:44.60.44.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP RUNNING NOARP MULTICAST MTU:1480 Metric:1
As I understand, we have ampr-ripd compiled for:
- Debian/Ubuntu Linux (various CPUs)
- BSD?
- OpenWRT/LEDE (various CPUs)
Are there any other OSes running ampr-ripd?
- Lynwood
KB3VWG
The Slackware (various CPUs) is running here with ampr-ripd:
tunl0 Link encap:IPIP Tunnel HWaddr inet addr:44.134.32.240 Mask:255.0.0.0 UP RUNNING NOARP MULTICAST MTU:1480 Metric:1 RX packets:7721318 errors:0 dropped:0 overruns:0 frame:0 TX packets:7833476 errors:48456 dropped:0 overruns:0 carrier:134 collisions:48272 txqueuelen:0 RX bytes:636721617 (607.2 Mb) TX bytes:516863215 (492.9 Mb)
-
Gustavo Ponza -
lleachii＠aol.com -
Marius Petrescu -
Rob Janssen -
SP2L