pfsense / HE tunnel / client vm problem

capt_scurrrvy

@johnpoz
I believe what you are asking for is in the post above. Under Windows 8 config.
I don't remember if that was ipconfig or ipconfig /all. The routes are there too.

Thanks.

johnpoz

Sorry I missed that - yeah it has a global address.. Does your linux?

edit: Oh missed that too - it does.. But your routing table is not correct..

Here for example is my default route on actual interface

It can point to the link-local of your gateway. But not going to work on your lo interface.

capt_scurrrvy

@johnpoz
In that same post is my test Centos 8 vm. It did get assigned an address, but from the route list, doesn't look like the default route gets set.

johnpoz

Your default is set, but only for lo - which never going to work.

capt_scurrrvy

@johnpoz
So is that Centos failing to request a route from the pfsense DHCP6 server or similarly failing to get the pfsense router advertisement?

johnpoz

Clients do not get "routes" from dhcpv6.. Not how IPv6 works. RA is used..

capt_scurrrvy

@johnpoz
Does that mean pfsense's router advertisement is not sending the information?

capt_scurrrvy

I noticed the fe80 address of the LAN nic of pfsense is being set automatically as the default route on the linux box.

[root@localhost ~]# ip -6 route
unreachable ::/96 dev lo metric 1024 error -113 pref medium
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -113 pref medium
2001:470:1f1d:bc::ff04 dev eth1 proto kernel metric 100 pref medium
2001:470:1f1d:bc::/64 dev eth1 proto ra metric 100 pref medium
unreachable 2002:a00::/24 dev lo metric 1024 error -113 pref medium
unreachable 2002:7f00::/24 dev lo metric 1024 error -113 pref medium
unreachable 2002:a9fe::/32 dev lo metric 1024 error -113 pref medium
unreachable 2002:ac10::/28 dev lo metric 1024 error -113 pref medium
unreachable 2002:c0a8::/32 dev lo metric 1024 error -113 pref medium
unreachable 2002:e000::/19 dev lo metric 1024 error -113 pref medium
unreachable 3ffe:ffff::/32 dev lo metric 1024 error -113 pref medium
fe80::/64 dev eth1 proto kernel metric 100 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fe80::8802:71ff:fe34:93cb dev eth1 proto ra metric 100 pref medium

I don't understand why that would happen.

The ifcg_eth1 file

DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy

capt_scurrrvy

Still trying to figure out why I can't get non Windows machines to communication via ipv6.

On pfsense, I have disabled DHCPv6 and Router Advertisements.

On the Centos vm, I statically set the ipv6 address and the gateway.

Just as previously, the VM can:
ping6
(this even does the correct DNS lookup)

traceroute6 and tracepath6 both show going out the Hurricane Electric tunnel.

Just as previously, the VM cannot:
Use a browser to view cnn, google, redhat.

I even put an allow any type rule on the pfsense WAN, LAN, and WANv6.
I disabled the firewall running on Centos.

It is as if TCP is not working. However, tcpdump shows traffic.

capt_scurrrvy

@johnpoz
Upgraded to 2.5.0. Had to manually add the default route for my ipv4 gateway on the WAN. See Default gateway can not be created with GUI

Surprise, Firefox on CentOS VM started to get to ipv6 web sites. This is with a manually assigned ipv6 for CentOS. Not sure what has changed between 2.4.5 and 2.5.

Gertjan

I upgraded this morning my main 'company' pfSense to 2.5.0.
I'm using he.net for my my IPv6 'needs'.

I had nothing to do.

Everything came up and was working fine.
( + captive portal using FreeRadius - OpenVPN server for my remote access).

Even a non-native package I installed many years ago was upgraded and kept on running.