Messages

1

23.1 Legacy Series / Re: IPv6: neighbor solicitations not answered by opnsense

« on: April 05, 2023, 12:15:21 pm »

I found out that it's "RFC 7278: Extending an IPv6 /64 Prefix from a Third Generation Partnership Project (3GPP) Mobile Interface to a LAN Link" which has to be supported.

2

23.1 Legacy Series / Re: IPv6: neighbor solicitations not answered by opnsense

« on: April 04, 2023, 06:14:14 pm »

Yes, it's only one /64. But why does it work with the residential CPE which I "reverse-engineered"? It also runs a NDP proxy.
Isn't it possible to support this scenario? I read multiple times that this is not a good IPv6 design, but it's reality.

3

23.1 Legacy Series / Re: IPv6: neighbor solicitations not answered by opnsense

« on: April 04, 2023, 12:46:01 pm »

Hi,

if I understand it correctly, ICMPv6 is allowed by default via the auto-generated firewall rules on WAN and LAN side.

Regards,
meiser

4

23.1 Legacy Series / IPv6: neighbor solicitations not answered by opnsense

« on: April 03, 2023, 08:55:24 pm »

Hi,

I installed opensense in a proxmox VM with two interfaces, one WAN connected to a 5G router, the other LAN.

On WAN side, I get a public IPv4 address and a IPv6 address via SLAAC (no DHCPv6 possible).  The LAN interface is static IPv4 and "track WAN" for IPv6. Therefore, I get a /64 on the LAN side. The LAN clients receive a /64 via SLAAC and can ping each other via IPv4/IPv6. But I cannot ping the opnsense VM or any host in the Internet via IPv6.

The neighbor solicitations are not answered by opnsense.

Code: [Select]

19:59:42.743631 IP6 xxxx:xxxx:xxxx:xxxx:5054:ff:fe21:d971 > ff02::1:ff21:d976: ICMP6, neighbor solicitation, who has xxxx:xxxx:xxxx:xxxx:5054:ff:fe21:d976, length 32

The client is xxxx:xxxx:xxxx:xxxx:5054:ff:fe21:d971, the opnsense WAN interface is xxxx:xxxx:xxxx:xxxx:5054:ff:fe21:d976

BTW, I can ping any host in the Internet via IPv6 from opnsense.

Could you give me some advice what I could check?.

Thanks a lot for your help.
Regards,
meiser