IPv6 dhcp not starting
-
Currently I'm running the snapshot from July 25.
Last saturday I tested the snapshot from August 31 because I saw a lot of link flaps on the system (still think this is a driver issue, but that's another thread), and it had the same issue.
I have to start the daemon by hand. -
I think that the only issue you are seeing here is that dhcp6c is started before pppoe has been connected and fails.
Can you confirm this is the case ? -
@ermal:
I think that the only issue you are seeing here is that dhcp6c is started before pppoe has been connected and fails.
Can you confirm this is the case ?My log was pulled after pppoe has connected for about 12hours, in that 12hours watchdog just showing the same thing every mins.
Unless I start it manually. -
@ermal:
I think that the only issue you are seeing here is that dhcp6c is started before pppoe has been connected and fails.
Can you confirm this is the case ?Upgraded to Sep 3 02:29:12 EDT image and can confirm dhcp6c is still not started on boot.
Don't know if it is dhcp6c is started to early. You can check from attached (anonymized) system.log pulled after boot and after manually starting dhcp6cThen upgraded to Sep 3 14:08:44 EDT image and can confirm dhcp6c IS not started on boot.
(anonymized) system.log attached too.system-anon_Sep-3-14:08:44.txt
system-anon_Sep-3-02:29:12.txt -
You seem to be low on resources since php processes are getting killed all over.
Also can you share your configuration seems you have some strange thing in there!EDIT: Can you try with todays snapshot since there were some changes done for low resource systems.
-
@ermal:
You seem to be low on resources since php processes are getting killed all over.
Also can you share your configuration seems you have some strange thing in there!Am running pfSense on an Alix 2D13 which has 256 MB RAM. EDIT: nanoBSD version of pfSense.
PM sent for config.@ermal:
EDIT: Can you try with todays snapshot since there were some changes done for low resource systems.
Will try later today.
-
Try this commit https://github.com/pfsense/pfsense/commit/d6df2c4c71678b5edd98892ca40facbb80f4ed1c manually or use a tomorrow snapshot and see if this behaves better.
-
Just upgraded to the "Sep 4 01:46:07" snapshot. This snapshot and the Sept 3 14:08:44 snapshot both DID start dhcp6c correctly
On memory usage: both Sep 3 snapshots had 8 lines with the word "kill" in them. The Sep 4 snapshot has only 3.
-
@ermal:
Try this commit https://github.com/pfsense/pfsense/commit/d6df2c4c71678b5edd98892ca40facbb80f4ed1c manually or use a tomorrow snapshot and see if this behaves better.
Tried it. What should it improve? I still have 3 lines with "kill" in sysem.log and dhcp6 is started too.
-
ok now dhcp6c doesn't crash, .. however the ipv6 routes are not working
/usr/local/sbin/dhcp6c -f -d -D -c /var/etc/dhcp6c_wan.conf -p /var/run/dhcp6c_pppoe0.pid pppoe0makes them work though, ..
if i do sockstat -46lp546, it shows a lot of dhcp6c clients on that port and also a php and sh script. however they keep cycling, as if they crash constantly
