Interfaces assignment?
-
Good morning from London,
I have a friend who uses Pfsense. He was on 2.6 (UFS) and upgraded to 2.7 with no errors. Then he had a power outage and from console pre- power outage there are LAN: 192.168.1.1 and WAN: his IP address.
Now whenever he tries to assign interfaces using option 1: he as normal has to restart his virgin media cable modem to assign a WAN, then next Pfsense asks for a LAN cable to be plugged in. After asking for the config to be written no interfaces can be seen.
That is IG0 WAN is has no IP
IG1 LAN has no IP.
He has tried a factory reset from console with same results. His Pfsense box is a Qotom i3 gen 4 4GB RAM and 64GB SSD. All interfaces light up with an orange and green LED whenever a Ethernet cable is plugged in.
I said to him to download the memory stick installer and start from a fresh install.
But why is this happening?
His setup is:
cable modem -> Pfsense WAN -> Pfsense LAN -> TP link 4 port - port1 Ethernet -> ASUS wireless and TP link 4 port - port2 -> Ethernet to his desktop. -
@Waqar-UK said in Interfaces assignment?:
He was on 2.6 (UFS) and upgraded to 2.7 with no errors.
UFS ? Do this How to Run a pfSense Software File System Check
pfSense is like any other disk based operating system.
Try the same thing with your phone, pad or PC : remove the power (battery). No need to do this many times, your system won't boot any more as the file system gets corrupted.My advise : got console access ? Get a good copy from the config.xml (in /cf/config/).
Re install, so you can chose ZFS hich is far more resilient.
If you can plan power outages : get an UPS, and connect the USB to pfSense, so it can do a gracefull shut down if needed. -
I will pass this onto him. I said that he should a fresh re-install to ver 2.7 as it is ZFS.
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
I wouldn't expect to have to reboot the modem to get an IP. If he just releases/renews the WAN DHCP lease from the GUI does it get a public IP?
One thing that changed between 2.6 and 2.7 was the timing of the start processes. For some users this can affect the WAN if both pfSense and the upstream modem are rebooted at the same time.
Steve
-
@stephenw10
Good evening Stephen,virgin media cable Internet to get a WAN, the cable modem has to be switched off and left for about 2-3 minutes then rebooted. Only then a WAN is recognised during the setup from option 1 in console.
VM uses DHCP. -
If you change router device, and hence the MAC, the modem would likely have to be rebooted. But otherwise you should be able to disconnect the WAN cable or reboot pfSense and it will pull an IP again. Is that not the case?
-
I far as I know what I have seen on my search on the Internet, for VM is what I said to obtain a WAN IP the cable modem has to re-booted after leaving it off for about 2 minutes.
He cannot get to the Web GUI. -
Like every time they reboot pfSense? That seems ridiculous. Can we see a boot log DHCP log?
But that didn't happen in 2.6?
-
@stephenw10 said in Interfaces assignment?:
Like every time they reboot pfSense? That seems ridiculous. Can we see a boot log DHCP log?
But that didn't happen in 2.6?
He has decided to re install 2.7. No it it did not take place with 2.6.
Nothing has changed apart from a new Asus wireless. But that should not stop Pfsense from getting a WAN or LAN. -
I agree. If it still does so after after reinstalling 2.7 clean I'd say it's almost certainly because of the timing change at boot.
If you look through the system logs and see the WAN interface show link UP during boot and ignoring it that's probably the problem. -
At boot, part of the sequence shows that the WAN is OK.
Is that part of what I should look out for?
How can I see system logs? -
You can see the logs in the gui in Status > System Logs. The main System tab there will show it if it's just booted.
If you see log entries showing the WAN link going UP and DOWN during boot and possibly
/rc.linkup: Ignoring link event during boot sequence.Then you might be hitting this. Adding a boot delay may prevent it. See for example: https://forum.netgate.com/topic/181890/pfsense-router-does-not-receive-ip-adress-from-isp
-
I will ask him, but he has made up his mind to do a fresh install of version 2.7.
-
Reinstalling is always a good test. That will show if it;s something in the config or something brought across in an upgrade.
-
I helped him to do a clean new install of ver 2.7.
All is working now.
