Ipv6 down
-
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