Ipv6 down
-
2.4.0-RC (amd64)
built on Mon Aug 28 11:05:02 CDT 2017ipv6 down he.net tunnel online but v6 network not work. windows tracert v6 address show 1231 wrong.
-
2.4.0-RC (amd64)
built on Mon Aug 28 20:30:48 CDT 2017the version client windows system can't get ipv6 gateway.
-
HE works as before on multiple 2.4-RC boxes. There's no info here to debug anything. What's "1231 wrong"? ???
-
HE works as before on multiple 2.4-RC boxes. There's no info here to debug anything. What's "1231 wrong"? ???
Ipv6 network barrier，PF Status Dashboard show ipv6 up, but lan's host ipv6 down.
built on Mon Aug 28 11:05:02 CDT 2017 this version use tracert ipv6 address show 1231 wrong code.
built on Mon Aug 28 20:30:48 CDT 2017 this version not show 1231 code, but lan's host dncp cant get ipv6 gateway and can't tracert to remote ipv6 address.
-
Hmmm, so there's actually nothing wrong with IPv6 except that your unknown Windows version does not get IPv6 assigned via DHCP? Well you do not need DHCPv6 at all in the first place. I'd suggest to switch RADVD to Assisted or Unmanaged.
-
Hmmm, so there's actually nothing wrong with IPv6 except that your unknown Windows version does not get IPv6 assigned via DHCP? Well you do not need DHCPv6 at all in the first place. I'd suggest to switch RADVD to Assisted or Unmanaged.
yes. just it is Assisted. but ipv6 not normal work.
2.4.0-RC (amd64)
built on Tue Aug 29 09:29:29 CDT 2017tracert 2a04:b900:0
:371 2003 ms 1 ms 1 ms face.x.net [2001:470:x:1089::20]
2 * * * time out。
3 * * * time out。
4 * * * time out。
5 * * * time out。
6 * * * time out。
7 * * * time out。
8 * * * time out。
9 * * * time out。
10 * * * time out。
11 * * * time out。
12 * * * time out。
13 * * * time out。
14 * * * time out。
15 * * * time out。
16 * * * time out。
17 * * * time out。
18 * * * time out。
19 * * * time out。
20 * * * time out。
21 * * * time out。
22 * * * time out。
23 * * * time out。
24 * * * time out。
25 * * * time out。
26 * * * time out。
27 * * * time out。
28 * * * time out。
29 * * * time out。
30 * * * time out。
-
You should probably troubleshoot your "not normal work" with Microsoft.
May I at least suggest posting on the international section of the forums, because I cannot see this going anywhere when English is used.
-
i have three he.ne tunnel, only an tunnel gif is up. other gif tunnel is down.
only the pf localhost ipv6 can tracert to internet. lan's hosts can't.
i have send mail he.net support.
he reply
Tunnels are stateless so make certain your IPv4 endpoints are up to date in our system and that no filtering is happening by your ISP or any configuration on your systems.
Both tunnel IDs are showing they are properly configured on our end, however I'm not seeing counters increment on either.
-
I have no idea how are you having 3 HE tunnels on a single box. Last time I checked it was completely impossible to create another tunnel to WAN IPv4 that's already been configured in another existing tunnel. Sounds very much like a completely broken setup, additionally unsupported by HE as well.
-
I have no idea how are you having 3 HE tunnels on a single box. Last time I checked it was completely impossible to create another tunnel to WAN IPv4 that's already been configured in another existing tunnel. Sounds very much like a completely broken setup, additionally unsupported by HE as well.
i had used 3 tunnel years . i have 3 ip wan.
-
Well, good luck with that.
-
you need to make sure you have unique gateways for each tunnel
-
DHCPv6 Server not work. no push ipv6 gateway to lan's client.
-
@yon:
DHCPv6 Server not work. no push ipv6 gateway to lan's client.
client can't get default ipv6 gateway ip.
-
DHCPv6 is not the thing that's pushing GWs. You need RA enabled.
-
DHCPv6 is not the thing that's pushing GWs. You need RA enabled.
of cause, i have enabled RA. it is can get DNS server, but can't get default ipv6 gateway
-
DHCPv6 is not the thing that's pushing GWs. You need RA enabled.
i find the Router Advertisement Daemon can't start.
log show :
servicewatchdog_cron.php: The command '/usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog' returned exit code '1', the output was ''
servicewatchdog_cron.php: Service Watchdog detected service radvd stopped. Restarting radvd (Router Advertisement Daemon)
-
Router Advertisement Daemon
-
1/ Remove the RADVD service from service watchdog!
2/ Kindly configure your gateway monitoring so that it reflects your super-sucky connectivity which results in RTTs in 300+ms range so that it does not think one of your zillion WANs went down every couple of minutes. Or disable the monitoring altogether.
-
1/ Remove the RADVD service from service watchdog!
2/ Kindly configure your gateway monitoring so that it reflects your super-sucky connectivity which results in RTTs in 300+ms range so that it does not think one of your zillion WANs went down every couple of minutes. Or disable the monitoring altogether.i have do it. but the RADVD service still can't start.
73688 /status_services.php: The command '/usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog' returned exit code '1', the output was ''
-
@yon:
1/ Remove the RADVD service from service watchdog!
2/ Kindly configure your gateway monitoring so that it reflects your super-sucky connectivity which results in RTTs in 300+ms range so that it does not think one of your zillion WANs went down every couple of minutes. Or disable the monitoring altogether.i have do it. but the RADVD service still can't start.
73688 /status_services.php: The command '/usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog' returned exit code '1', the output was ''
i have no the file in system /var/run/radvd.pid
-
I've been having this issue for a few weeks now, as well. Only using one WAN. The radvd process seems to start on bootup, but the first boot after an upgrade it seems to not function. Restarting radvd or rebooting seems to fix.
-
I've been having this issue for a few weeks now, as well. Only using one WAN. The radvd process seems to start on bootup, but the first boot after an upgrade it seems to not function. Restarting radvd or rebooting seems to fix.
my radvd service cant start. i dont know why
-
@yon:
I've been having this issue for a few weeks now, as well. Only using one WAN. The radvd process seems to start on bootup, but the first boot after an upgrade it seems to not function. Restarting radvd or rebooting seems to fix.
my radvd service cant start. i dont know why
Can you post your radvd.conf, or at least examine it to confirm that it is correct.
-
Automatically Generated, do not edit
Generated for DHCPv6 Server lan
interface re0 {
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 20;
AdvLinkMTU 1500;
AdvDefaultPreference high;
AdvManagedFlag on;
AdvOtherConfigFlag on;
prefix 2001:470:f165::/48 {
DeprecatePrefix on;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
};
prefix 2001:470:f165
:1/64 {
DeprecatePrefix on;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
route ::/0 {
RemoveRoute on;
};
RDNSS 2001:470:f167::8 2001:470:f165::6 { };
DNSSL xoyu.net { };
};Generated for DHCPv6 Server opt8
interface gif3 {
AdvSendAdvert on;
MinRtrAdvInterval 5;
MaxRtrAdvInterval 20;
AdvLinkMTU 1480;
AdvDefaultPreference medium;
prefix 2001:470:d:1085::20/128 {
DeprecatePrefix on;
AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
};
route ::/0 {
RemoveRoute on;
};
RDNSS 2a05:dfc7:5::53 2001:19f0:7402:d:5400:00ff:fe2a:7fb6 2001:41d0:8:be92::1 fd42:d42:d42:53::1 { };
DNSSL xoyu.net { };
};
-
@marjohn56:
Can you post your radvd.conf, or at least examine it to confirm that it is correct.
I obscured the prefixes and internal domains. Everything else is as generated by pfSense.
Automatically Generated, do not edit
Generated for DHCPv6 Server lan
interface hn1 {
AdvSendAdvert on;
MinRtrAdvInterval 5;
MaxRtrAdvInterval 20;
AdvLinkMTU 1500;
AdvDefaultPreference medium;
AdvManagedFlag on;
AdvOtherConfigFlag on;
prefix 2607:fcc8:xxxx:xxxx::/64 {
DeprecatePrefix on;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
};
route ::/0 {
RemoveRoute on;
};
DNSSL xxxx.local { };
};Generated for DHCPv6 Server opt1
interface hn2 {
AdvSendAdvert on;
MinRtrAdvInterval 5;
MaxRtrAdvInterval 20;
AdvLinkMTU 1500;
AdvDefaultPreference medium;
AdvManagedFlag on;
AdvOtherConfigFlag on;
prefix 2607:fcc8:xxxx:xxxx::/64 {
DeprecatePrefix on;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
};
route ::/0 {
RemoveRoute on;
};
DNSSL xxxx.local { };
};
-
@yon:
Generated for DHCPv6 Server opt8
interface gif3 {
AdvSendAdvert on;
MinRtrAdvInterval 5;
MaxRtrAdvInterval 20;
AdvLinkMTU 1480;
AdvDefaultPreference medium;
prefix 2001:470:d:1085::20/128 {
DeprecatePrefix on;
AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
};
route ::/0 {
RemoveRoute on;
};
RDNSS 2a05:dfc7:5::53 2001:19f0:7402:d:5400:00ff:fe2a:7fb6 2001:41d0:8:be92::1 fd42:d42:d42:53::1 { };
DNSSL xoyu.net { };
};prefix 2001:470:d:1085::20/128 ??? How so?
-
I've been having this issue for a few weeks now, as well. Only using one WAN. The radvd process seems to start on bootup, but the first boot after an upgrade it seems to not function. Restarting radvd or rebooting seems to fix.
If it only happens after an upgrade then it could be many things. My course of action when anything like this happens is to do a fresh install. Any junk left around after an update is then cleared.
-
@marjohn56:
prefix 2001:470:d:1085::20/128 ??? How so?
The guy's lost any track of what's configured on his box. There are multiple threads here showing the mess configured there, 12 or so WANs (mostly tunnels and VPNs). The info he posted on this thread is vastly incomplete.
-
@doktornotor - I may be being dense, but can you have /128 prefix?
-
He enabled DHCPv6 server on something where's it not supposed to be enabled at all… I have no idea what's his opt8 interface, nor any desire to debug this mess.
I frankly doubt that nonsense has ever worked. Look at this:
Or this:
-
@marjohn56:
I've been having this issue for a few weeks now, as well. Only using one WAN. The radvd process seems to start on bootup, but the first boot after an upgrade it seems to not function. Restarting radvd or rebooting seems to fix.
If it only happens after an upgrade then it could be many things. My course of action when anything like this happens is to do a fresh install. Any junk left around after an update is then cleared.
I stand corrected. I tried another reboot and it stopped working again until I restarted radvd. I think it might have been a coincidence and it arbitrarily works or doesn’t work on a reboot.
-
Your issue is not the same as the OP.
Try a fresh install and go from there.
-
He enabled DHCPv6 server on something where's it not supposed to be enabled at all… I have no idea what's his opt8 interface, nor any desire to debug this mess.
I frankly doubt that nonsense has ever worked. Look at this:
I only have one question after seeing that…
Why? :o
-
@marjohn56:
He enabled DHCPv6 server on something where's it not supposed to be enabled at all… I have no idea what's his opt8 interface, nor any desire to debug this mess.
I frankly doubt that nonsense has ever worked. Look at this:
I only have one question after seeing that…
Why? :o
No idea… Have I mentioned that there's allegedly BGP involved as well? Sure like hell would like to be on the receiving end of it. :o ;D
-
Strange thing, delete the dns fd42:d42:d42:53::1, then radvd service can start. this is bug ? the dns fd42:d42:d42:53::1 only for an VPN interface. ???
-
@marjohn56:
@yon:
Generated for DHCPv6 Server opt8
interface gif3 {
AdvSendAdvert on;
MinRtrAdvInterval 5;
MaxRtrAdvInterval 20;
AdvLinkMTU 1480;
AdvDefaultPreference medium;
prefix 2001:470:d:1085::20/128 {
DeprecatePrefix on;
AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
};
route ::/0 {
RemoveRoute on;
};
RDNSS 2a05:dfc7:5::53 2001:19f0:7402:d:5400:00ff:fe2a:7fb6 2001:41d0:8:be92::1 fd42:d42:d42:53::1 { };
DNSSL xoyu.net { };
};prefix 2001:470:d:1085::20/128 ??? How so?
this /128 not config by myself, it is pfsense system auto config. GIF tunnel local address is 2001:470:d:1085::20
-
He enabled DHCPv6 server on something where's it not supposed to be enabled at all… I have no idea what's his opt8 interface, nor any desire to debug this mess.
I frankly doubt that nonsense has ever worked. Look at this:
this is not config by me. i don't know why it is on DHCPv6.. ???
Generated for DHCPv6 Server opt8
-
@yon:
Strange thing, delete the dns fd42:d42:d42:53::1, then radvd service can start. this is bug ? the dns fd42:d42:d42:53::1 only for an VPN interface. ???
https://en.wikipedia.org/wiki/Unique_local_address
@yon:
@marjohn56:
@yon:
Generated for DHCPv6 Server opt8
interface gif3 {
AdvSendAdvert on;
MinRtrAdvInterval 5;
MaxRtrAdvInterval 20;
AdvLinkMTU 1480;
AdvDefaultPreference medium;
prefix 2001:470:d:1085::20/128 {
DeprecatePrefix on;
AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
};
route ::/0 {
RemoveRoute on;
};
RDNSS 2a05:dfc7:5::53 2001:19f0:7402:d:5400:00ff:fe2a:7fb6 2001:41d0:8:be92::1 fd42:d42:d42:53::1 { };
DNSSL xoyu.net { };
};prefix 2001:470:d:1085::20/128 ??? How so?
this /128 not config by myself, it is pfsense system auto config. GIF tunnel local address is 2001:470:d:1085::20
WTH are you enabling DHCPv6 server on a (apparently completely misconfigured) GIF tunnel interface?
-
The GIGO principle… 8)