Sendmsg: No route to host

bimmerdriver · Nov 12, 2017, 3:13 AM

I'm running the latest snapshot: 2.4.2.a.20171110.1936

It's running on a hyper-v and it was working before this update. There is one windows 10 client, also virtual. ipv4 is working, but not ipv6. Both ipv6-test.com and test-ipv6.com are reporting that ipv6 is not working, as well as the adapter status on the client. The client has ipv4 and ipv6 addresses. Everything looks normal, except the routing log is filled with messages such as the following:

Nov 11 18:58:07	radvd	42580	sendmsg: No route to host
Nov 11 18:58:18	radvd	42580	sendmsg: No route to host
Nov 11 18:58:29	radvd	42580	sendmsg: No route to host
Nov 11 18:58:38	radvd	42580	sendmsg: No route to host
Nov 11 18:58:43	radvd	42580	sendmsg: No route to host
Nov 11 18:58:49	radvd	42580	sendmsg: No route to host
Nov 11 18:59:08	radvd	42580	sendmsg: No route to host
Nov 11 18:59:23	radvd	42580	sendmsg: No route to host

Anyone else experiencing this? Any suggestions to locate the problem?

maverick_slo · Nov 12, 2017, 7:08 AM

https://forum.pfsense.org/index.php?topic=139797.0

maverick_slo · Nov 12, 2017, 7:35 AM

Hmmm, but my ipv6 is working just fine
static ones and slaac androids as well…

bimmerdriver · Nov 12, 2017, 4:47 PM

I'm still getting the same RADVD messages in the log.

maverick_slo · Nov 12, 2017, 4:55 PM

And your ipv6 is dead?
I too have log entries but my ipv6 is ok.

bimmerdriver · Nov 12, 2017, 5:28 PM

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.

maverick_slo · Nov 12, 2017, 5:42 PM

Huh thats weird.
I have same messages but ipv6 is ok.
I have pppoe dhcpv6 isp config…

bimmerdriver · Nov 12, 2017, 8:04 PM

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.

bimmerdriver · Nov 13, 2017, 2:37 AM

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

bimmerdriver · Nov 13, 2017, 3:14 AM

This seems to be a likely culprit: https://redmine.pfsense.org/issues/8022#note-15

loos · Nov 13, 2017, 2:49 PM

Fixed.

The build is still running, please wait until the next snapshot to check.

Thanks for reporting.

bimmerdriver · Nov 13, 2017, 4:36 PM

@loos:

Fixed.

The build is still running, please wait until the next snapshot to check.

Thanks for reporting.

Updated, looks good.

maverick_slo · Nov 13, 2017, 6:38 PM

+1
But strange that I had no issues…

bimmerdriver · Nov 13, 2017, 11:50 PM

@maverick_slo:

+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.