pfSense problems tonight with access
-
Hi all,
I've been running pfSense for a while without much issues (previously used smoothwall) and had it working with my sky fibre, but tonight I thought my internet had gone down as lost all connection to internet across all my devices. I tried connecting to the web interface to see what was happening and was unable to connect to it.
I thought that the unit had shut down, so went to power it back on but found it was fully powered up, so thought ok, its hung and rebooted it. Again nothing, no wired connections and no wifi connections (i have netgear orbi connected for the wifi side) which I thought was odd. I connected a monitor and keyboard and the bootup showed it had received my internet ip and on testing from the console menu I was able to ping external addresses, but still had no wifi or wired connections.
I reset the web configurator and this did not work, i tried factory defaults from the unit and tried to reconfigure the lan ip, but it would not accept this, i also tried restoring from one of its backups but that never resolved the problem.
I'm thinking I may need to rebuild the unit, but can it now be done via USB stick instead of DVD, also is there a way of getting the configuration from the system if managed to get it up and running and use this on the new setup?
Or is there something simple I am missing that may resolve the problem I'm having.
thanks
-
@mirdragon said in pfSense problems tonight with access:
Or is there something simple I am missing that may resolve the problem I'm having.
Like : the device that stores the system started to go bad ?
As usuall - in cae of troubles : restart pFsense, see it starting on the console. Check the dmesg log afterwards. Other logs.@mirdragon said in pfSense problems tonight with access:
and tried to reconfigure the lan ip, but it would not accept this,
Like what IP / mask ?
And, when you test, leave everything to default, just establish a WAN connection - and go up from there. -
Yeh managed to reboot and no errors were showing during boot, will have to check the logs tomorrow.
As for wan wasn't able to get ip when default settings as uses mer connection and couldn't configure via the Web configuration.
I've currently got up and running with my sky q router, so will check the pfsense box over the weekend.
If I need to rebuild I need to get the config off it as had a few rules configured on it, plus need to find old dvd drive to temporary connect up.
-
midragon, I run pfsense with sky fttc, and had a very similar problem at a very similar time it just stopped working one day after months ans months of stable operation. I had to dig out an old SR102 as i didn't have the time to fix.
Looking at it now, did you discover anything?
-
@jashaw30 said in pfSense problems tonight with access:
midragon, I run pfsense with sky fttc, and had a very similar problem at a very similar time it just stopped working one day after months ans months of stable operation. I had to dig out an old SR102 as i didn't have the time to fix.
Looking at it now, did you discover anything?
Yep, I moved to OpnSense - if pfsense updated to the latest version it stops working
-
I’m back working (24 hours so far) with Sky FTTC (MER) and pfSense and a BT Openreach Modem.
With a little help from wireshark I came to the following conclusion.
In pfSense within DHCP Client Configuration - Hostname in now DHCP option 12. I believe this used to be DHCP option 61 Client ID and during an update this has been changed.
To get working again within DHCP Client Configuration (Advanced Configuration), Lease Requirements and Requests, Send options I have added the following.
dhcp-client-identifier "<SKYLANMAC@skydsl|<PASSWORD>"
e.g
dhcp-client-identifier "010101010101@skydsl|000000000"
I found I needed the quotation marks for it to work.
-
@jashaw30 that's all you've ever needed since that changed that you no longer need to use their kit.
dhcp-client-identifier "woteveryouwanr@skydsl|woteveryouwant"
