Ipv6 down

[doktornotor]

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.

[yon]

@doktornotor:

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.

[doktornotor]

Well, good luck with that.

[grandrivers]

you need to make sure you have unique gateways for each tunnel

[yon]

DHCPv6 Server  not work. no push ipv6 gateway to lan's client.

[yon]

@yon:

DHCPv6 Server  not work. no push ipv6 gateway to lan's client.

client can't get default ipv6 gateway ip.

[doktornotor]

DHCPv6 is not the thing that's pushing GWs. You need RA enabled.

[yon]

@doktornotor:

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

[yon]

@doktornotor:

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)


[yon]

Router Advertisement Daemon

[doktornotor]

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.

[yon]

@doktornotor:

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]

@yon:

@doktornotor:

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

[xpxp2002]

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.

[yon]

@xpxp2002:

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

[Guest]

@yon:

@xpxp2002:

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.

[yon]

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  { };
};

[xpxp2002]

@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  { };
};

[Guest]

@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?

[Guest]

@xpxp2002:

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.