L2TP Interface shows IPv6 WAN Address
-
Not sure if this is a bug or a "feature". I use an L2TP tunnel, and have an interface assigned to the L2TP. Despite having configured IPv6 on the Interface as Disabled, on the status screens and via an ifconfig, it shows the IPv6 address which is identical to teh WAN DHCP address.
Is this expected?
-
Not exactly sure what you mean there. Can we see that output?
-
Sure can
[2.5.0-RC][root@gw.griffo.co]/root: ifconfig igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: WAN options=e120bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,WOL_MAGIC,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2e inet6 fe80::4262:31ff:fe14:862e%igb0 prefixlen 64 scopeid 0x1 inet6 2403:5800:7001:b:f4f7:9e2e:66f2:31ef prefixlen 128 inet 159.196.107.74 netmask 0xfffffc00 broadcast 159.196.107.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: LAN options=e120bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,WOL_MAGIC,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2f inet6 fe80::4262:31ff:fe14:862f%igb1 prefixlen 64 scopeid 0x2 inet6 fe80::1:1%igb1 prefixlen 64 scopeid 0x2 inet6 2403:5800:7600:b00:4262:31ff:fe14:862f prefixlen 64 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:30 media: Ethernet autoselect status: no carrier nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb3: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:31 media: Ethernet autoselect status: no carrier nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb4: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:32 media: Ethernet autoselect status: no carrier nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb5: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:33 media: Ethernet autoselect status: no carrier nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> enc0: flags=0<> metric 0 mtu 1536 groups: enc nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff000000 inet 10.10.10.1 netmask 0xffffffff groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> pflog0: flags=100<PROMISC> metric 0 mtu 33160 groups: pflog pfsync0: flags=0<> metric 0 mtu 1500 groups: pfsync igb1.20: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: VL_20_US_VPN options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2f inet6 fe80::4262:31ff:fe14:862f%igb1.20 prefixlen 64 scopeid 0xb inet 192.168.20.1 netmask 0xffffff00 broadcast 192.168.20.255 groups: vlan vlan: 20 vlanpcp: 0 parent interface: igb1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb1.30: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: VL_30_AU_VPN options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2f inet6 fe80::4262:31ff:fe14:862f%igb1.30 prefixlen 64 scopeid 0xc inet6 fe80::1:1%igb1.30 prefixlen 64 scopeid 0xc inet6 2403:5800:7600:b20:4262:31ff:fe14:862f prefixlen 64 inet 192.168.30.1 netmask 0xffffff00 broadcast 192.168.30.255 groups: vlan vlan: 30 vlanpcp: 0 parent interface: igb1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb1.50: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: VL_50_EU_VPN options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2f inet6 fe80::4262:31ff:fe14:862f%igb1.50 prefixlen 64 scopeid 0xd inet 192.168.50.1 netmask 0xffffff00 broadcast 192.168.50.255 groups: vlan vlan: 50 vlanpcp: 0 parent interface: igb1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb1.66: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: VL_66_IoT options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2f inet6 fe80::4262:31ff:fe14:862f%igb1.66 prefixlen 64 scopeid 0xe inet6 fe80::1:1%igb1.66 prefixlen 64 scopeid 0xe inet6 2403:5800:7600:b66:4262:31ff:fe14:862f prefixlen 64 inet 192.168.66.1 netmask 0xffffff00 broadcast 192.168.66.255 groups: vlan vlan: 66 vlanpcp: 0 parent interface: igb1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb1.99: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: VL_99_Guest options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2f inet6 fe80::4262:31ff:fe14:862f%igb1.99 prefixlen 64 scopeid 0xf inet 192.168.99.1 netmask 0xffffff00 broadcast 192.168.99.255 groups: vlan vlan: 99 vlanpcp: 0 parent interface: igb1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> igb1.40: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: VL_40_AU_VPN options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> ether 40:62:31:14:86:2f inet6 fe80::4262:31ff:fe14:862f%igb1.40 prefixlen 64 scopeid 0x10 inet 192.168.40.1 netmask 0xffffff00 broadcast 192.168.40.255 groups: vlan vlan: 40 vlanpcp: 0 parent interface: igb1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> ovpns5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500 options=80000<LINKSTATE> inet6 fe80::4262:31ff:fe14:862e%ovpns5 prefixlen 64 scopeid 0x13 inet 192.168.70.1 --> 192.168.70.2 netmask 0xffffffff groups: tun openvpn nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> Opened by PID 99838 ovpnc3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500 options=80000<LINKSTATE> inet6 fe80::4262:31ff:fe14:862e%ovpnc3 prefixlen 64 scopeid 0x14 inet 10.8.3.8 --> 10.8.3.1 netmask 0xffffff00 groups: tun openvpn nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> Opened by PID 8910 ovpnc2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500 options=80000<LINKSTATE> inet6 fe80::4262:31ff:fe14:862e%ovpnc2 prefixlen 64 scopeid 0x15 inet 10.8.1.7 --> 10.8.1.1 netmask 0xffffff00 groups: tun openvpn nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> Opened by PID 18229 wg0: flags=8080c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420 options=880000<LINKSTATE> inet 10.70.216.246 netmask 0xffffffff inet6 fe80::4262:31ff:fe14:862e%wg0 prefixlen 64 scopeid 0x12 groups: wg listen-port: 51820 private-key: GFeaYI8bYOFrCfk/N/r1GAa+/vZOC0u8PIEqaHKx/nk= public-key: yBrQjNLbMEl0WCF4cdehnZ6+H8RY4rFTeJRphikmbGQ= media: Ethernet autoselect (25GBase-ACC <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> wg1: flags=8080c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420 options=880000<LINKSTATE> inet 192.168.70.65 netmask 0xffffffc0 inet6 fe80::4262:31ff:fe14:862e%wg1 prefixlen 64 scopeid 0x16 groups: wg listen-port: 51821 private-key: qIJxtOGI7RU635vzMLqn31gF9i2sEa975+acIpkvPG0= public-key: 6iEV/lkOxZTe7naSF3LvLl+M9KfMDqdFYqhzmvoD1io= media: Ethernet autoselect (25GBase-ACC <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> wg2: flags=8080c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420 options=880000<LINKSTATE> inet 10.68.2.28 netmask 0xffffffff inet6 fe80::4262:31ff:fe14:862e%wg2 prefixlen 64 scopeid 0x11 groups: wg listen-port: 51822 private-key: gA/AQzkQtUJvRQeo8xxROQ77JMEHNp3RgF0kbejfR1g= public-key: tVD80+9oTjefKZxWsY0+ulZv0/vWYH8qjUenuc1Ma1I= media: Ethernet autoselect (25GBase-ACC <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>. l2tp0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492 description: VPN_Trimium_L2TP inet 192.168.88.94 --> 192.168.88.1 netmask 0xffffffff inet6 fe80::4262:31ff:fe14:862e%l2tp0 prefixlen 64 scopeid 0x17 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> [2.5.0-RC][root@gw.griffo.co]/root:
even in down state
-
Oh I see it's an L2TP client?
I assume the server is not passing IPv6 to it? Not sure I've ever considered if that's possible to be honest.Mmm, that is probably an edge case that slipped though. L2TP clients are not at all common.
I would open a bug report for that: https://redmine.pfsense.org/
I don't see anything there that looks like that already.Steve
-
@stephenw10 Thanks. I actually don't want any IPv6 on this interface, but it seems to get one anyway. I'll raise a bug. There's actually a bunch of small bugs with L2TP clients so I might get busy raising them all.
-
Yes, I'd go ahead and do that. That interface type is probably the least well used. Or maybe pptp!
It's likely a display bug only. You can see the actual interface does not have an IPv6 address.
Steve