pfsense 2.7.2 Never completes startup process
-
Oh you were seeing the same issue in earlier versions?
How did you upgrade then if bootup never completes. You installed 2.7.2 clean and restore a config?
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
Oh you were seeing the same issue in earlier versions?
How did you upgrade then if bootup never completes. You installed 2.7.2 clean and restore a config?
You installed 2.7.2 clean and restore a config?
yes. In fact, DHCP is working, but the pfsense startup interface is not completed.
-
Ah, Ok. Are you able to connect to the firewall at all then? SSH working?
Anything shown in the system log?
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
Ah, Ok. Are you able to connect to the firewall at all then? SSH working?
Anything shown in the system log?
I just tried to delete all the "DHCPv6 Static Mappings" setting and restarted the pfsense system just now. The startup interface was completed.
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
Ah, Ok. Are you able to connect to the firewall at all then? SSH working?
Anything shown in the system log?
The LAN ipv4 I mentioned before cannot be routed through the ISP WAN. I haven't found a solution to this problem yet. I have set up static routing to let a lot of ipv4 be routed through the ISP WAN. But it doesn't seem to work.
-
What do you have in the v6 static mappings? It seems like something Kea doesn't like.
If you switch back to ISC DHCPd does it allow those mappings again?
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
What do you have in the v6 static mappings? It seems like something Kea doesn't like.
If you switch back to ISC DHCPd does it allow those mappings again?
ipv6 normal, ipv4 route not normal work.
-
@yon-0 said in pfsense 2.7.2 Never completes startup process:
ipv6 normal, ipv4 route not normal work.
That's what happens if you switch back to ISC?
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
@yon-0 said in pfsense 2.7.2 Never completes startup process:
ipv6 normal, ipv4 route not normal work.
That's what happens if you switch back to ISC?
back to ISC DHCP, it ipv4 DHCP not work. Lan pc can't get dhcp ip.
-
Hmm, but it was working before you switched to Kea?
The service is running?
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
Hmm, but it was working before you switched to Kea?
The service is running?
yes, kea is runing. but i setup Static routing like 117.32.0.0/13 to WAN, other ips via VPN. the LAN's can't route to 117.32.0.0/13 now.
-
@yon-0 said in pfsense 2.7.2 Never completes startup process:
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
@yon-0 said in pfsense 2.7.2 Never completes startup process: That's what happens if you switch back to ISC?back to ISC DHCP, it ipv4 DHCP not work. Lan pc can't get dhcp ip.
@yon-0 said in pfsense 2.7.2 Never completes startup process:
yes, kea is runing.
So.... not back to ISC?
Static routes would be completely unrelated to DHCP though anyway.
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
@yon-0 said in pfsense 2.7.2 Never completes startup process:
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
@yon-0 said in pfsense 2.7.2 Never completes startup process: That's what happens if you switch back to ISC?back to ISC DHCP, it ipv4 DHCP not work. Lan pc can't get dhcp ip.
@yon-0 said in pfsense 2.7.2 Never completes startup process:
yes, kea is runing.
So.... not back to ISC?
Static routes would be completely unrelated to DHCP though anyway.
yes, now it can't back to ISC. I see that the ISC DHCP page has changed and is different from before.
Static routes would be completely unrelated to DHCP though anyway.
Yes, but this is an urgent problem that needs to be solved. I have tried various methods but cannot solve it.
-
OK I'm confused as to what the actual problem is at this point.
You cannot switch dhcp back to ISC for some reason?
-
@yon-0 said in pfsense 2.7.2 Never completes startup process:
i setup Static routing like 117.32.0.0/13 to WAN, other ips via VPN. the LAN's can't route to 117.32.0.0/13 now
The most important thing at present is to solve the ipv4 routing problem.
-
Ok so what exactly is the routing issue you're seeing? How are you testing?
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
Ok so what exactly is the routing issue you're seeing? How are you testing?
10.50.1.254 is lan gateway ip. ipv4 to any via wan no route .
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 10.50.1.254 - 0 | 3 | 3 | 1 | 1 | 2 | 2 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 2 | 0 | 0 | 0 | 0 | 0 | |________________________________________________|______|______|______|______|______|______|WinMTR v1.00 GPLv2
-
So there is no default IPv4 route?
The IPv4 gateway is not responding?
What does the routing table look like?
-
@stephenw10 said in pfsense 2.7.2 Never completes startup process:
So there is no default IPv4 route?
The IPv4 gateway is not responding?
What does the routing table look like?
ipv4 default route is vpn interface. some ipv4 setup Static routing via pppoe wan.
IPv4 Routes default 10.16.0.1 UGS 10 1420 ovpnc12 1.0.1.0/24 link#14 U1 1 1492 pppoe2 1.0.2.0/23 link#14 U1 1 1492 pppoe2 1.0.8.0/21 link#14 U1 1 1492 pppoe2 1.0.32.0/19 link#14 U1 1 1492 pppoe2 1.1.0.0/24 link#14 U1 1 1492 pppoe2 1.2.0.0/15 link#14 U1 1 1492 pppoe2 1.8.0.0/16 link#14 U1 1 1492 pppoe2 -
Ok so what IP are you trying to reach in the traceroute above?
