Sendmsg: No route to host
-
https://forum.pfsense.org/index.php?topic=139797.0
-
Hmmm, but my ipv6 is working just fine
static ones and slaac androids as well… -
I'm still getting the same RADVD messages in the log.
-
And your ipv6 is dead?
I too have log entries but my ipv6 is ok. -
It's dead. nslookup will return ipv4 and ipv6 addresses, but can only ping ipv4 addresses. ipv6-test.com and test-ipv6.com both report no ipv6.
Aside from the above, and the radvd messages in the log, everything looks normal.
-
Huh thats weird.
I have same messages but ipv6 is ok.
I have pppoe dhcpv6 isp config… -
My ISP does not use PPPoE, but rather RFC 1483 via DHCP. Both gateways are up, DHCPv4 and DHCPv6 are up. I have a separate pfsense 2.3.4 system that is working fine. This ipv6 problem seems to be within the latest snapshots of pfsense 2.4.2.
-
Looking at the list of snapshots, I think the one where it broke is either the first or send of these:
https://snapshots.pfsense.org/amd64/pfSense_master/installer/pfSense-CE-2.4.2-DEVELOPMENT-amd64-20171110-0646.iso.gz
https://snapshots.pfsense.org/amd64/pfSense_master/installer/pfSense-CE-2.4.2-DEVELOPMENT-amd64-20171110-1033.iso.gz
-
This seems to be a likely culprit: https://redmine.pfsense.org/issues/8022#note-15
-
Fixed.
The build is still running, please wait until the next snapshot to check.
Thanks for reporting.
-
Fixed.
The build is still running, please wait until the next snapshot to check.
Thanks for reporting.
Updated, looks good.
-
+1
But strange that I had no issues… -
+1
But strange that I had no issues…Maybe if the log messages weren't so vague, it would shed light on why the effects of this problem were different for different users.