196
17.1 Legacy Series / Re: Multicast Routing
« on: March 20, 2017, 11:14:48 am »
... how does your igmpproxy.conf look like?
Br br
Br br
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
FreeeBSD/and64 EFI loader, revision 1.1
(root@sennsey64, Mon, Feb20, 13:09:03 CET 2017)
Loading /boot/defaults/loader.conf
|
Jul 23 12:06:58 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:04 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:05 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:06 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:13 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:14 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:14 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:17 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:18 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:24 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:24 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:25 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:31 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:33 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:34 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:39 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:40 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:41 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:42 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:43 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:49 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:50 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:53 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:07:55 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 23 12:07:56 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 23 12:07:58 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 23 12:08:00 OPNsense rtsold[14935]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 21 19:12:28 OPNsense rtsold[15608]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 21 19:12:29 OPNsense rtsold[15608]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 21 19:12:29 OPNsense rtsold[15608]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 21 19:12:34 OPNsense rtsold[15608]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn2)
Jul 21 19:12:36 OPNsense rtsold[15608]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
Jul 21 19:12:38 OPNsense rtsold[15608]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn3)
Jul 21 19:12:41 OPNsense rtsold[15608]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(xn0)
I have a dual stack configured with Capture from WAN. tcpdump does not show any further RA in my networkscontroller# ip rule list
0: from all lookup local
32764: from all to 192.168.88.11 lookup mng
32765: from 192.168.88.11 lookup mng
32766: from all lookup main
32767: from all lookup default
controller# ip route list table mng
default via 192.168.88.1 dev eno4
192.168.88.0/24 dev eno4 scope link src 192.168.88.11
So: what works:controller# ping -I eno4 192.168.88.1
PING 192.168.88.1 (192.168.88.1) from 192.168.88.11 eno4: 56(84) bytes of data.
64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=1061 ms
64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=52.2 ms
64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=59.7 ms
64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=1059 ms
64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=83.2 ms
64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=90.8 ms
controller# ping -I eno4 192.168.2.101
PING 192.168.2.101 (192.168.2.101) from 192.168.88.11 eno4: 56(84) bytes of data.
From 192.168.88.11 icmp_seq=1 Destination Host Unreachable
Obviously, there is a missing route in the opnsense between the gateway 192.168.88.1 and the WAN. Evidence for this is when executing on the server:controller # ip neigh show
104.68.210.119 dev eno4 FAILED
192.168.88.31 dev eno4 lladdr 00:25:kk:mm:rr:a1 STALE
192.168.2.1 dev eno4 FAILED
104.108.187.66 dev eno4 FAILED
192.168.88.1 dev eno4 lladdr 00:17:ww:ff:ww:1c STALE
192.168.1.83 dev eno1 lladdr ac:87:ww:ff:nn:rr REACHABLE
192.168.2.101 dev eno4 FAILED
192.168.1.1 dev eno1 lladdr 00:17:nn:aa:bb:1a STALE
(...)
(Don't ask me why even LAN connections are stale ); BUT, a trace route command to an address in the internet showscontroller# traceroute -i eno4 www.nokia.com
traceroute to www.nokia.com (104.68.210.119), 30 hops max, 60 byte packets
1 192.168.88.1 (192.168.88.1) 57.456 ms 59.551 ms 59.545 ms
2 192.168.2.1 (192.168.2.1) 59.573 ms 59.611 ms 59.592 ms
3 217.0.117.111 (217.0.117.111) 59.684 ms 59.668 ms 59.659 ms
4 (...)
8 a104-68-210-119.deploy.static.akamaitechnologies.com (104.68.210.119) 187.744 ms 187.735 ms 187.724 ms
something really confusing here .... xn0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=503<RXCSUM,TXCSUM,TSO4,LRO>
(...)
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet manual
status: active
No pecularity in the logs of the opnsense box. I correlate this behavior time wise to the update to 16.1.14, getting slowly worse over time.OPNsense 16.1.16-amd64
FreeBSD 10.2-RELEASE-p18
OpenSSL 1.0.2h 3 May 2016
I did check the uptime and opnsense was running, The trick with F5 I will try next time