Changed to Static IP on LAN [SOLVED]
-
You need to connect to the console and use console option 2 to reassign the IP address for LAN but using a 10.10.10.20/24. That /32 is not right and is likely breaking everything.
No, that's not right. You need to google IP subnet to get some good educational results.
-
Absolutely. You need to try to understand the concept of netmasks before you do anything else. Setting a /32 mask on your LAN interface means you've masked off all of your internal hosts from accessing the internal interface. Have a look here for a bit more explanation:
https://www.iplocation.net/subnet-mask
-
Absolutely. You need to try to understand the concept of netmasks before you do anything else. Setting a /32 mask on your LAN interface means you've masked off all of your internal hosts from accessing the internal interface. Have a look here for a bit more explanation:
https://www.iplocation.net/subnet-mask
Hi muswell, thank you for the link! I've avoided subnetting all my life because I always feel like an idiot when trying to understand it…sad yes...that link helps a bit...
-
I accidentally gave bad advice to a possible solution here, apologies
-
I accidentally gave bad advice to a possible solution here, apologies
-
Looks like you're already logged in. Looks like you changed the admin username. type exit and you should get the console menu.
-
Looks like you're already logged in. Looks like you changed the admin username. type exit and you should get the console menu.
I typed "exit" after logging in as "x" and all it did was go back to a prompt asking me to login…what next?
-
The default configuration does not have a console password.
Try logging in and running /etc/rc.initial
You really should be using the default admin / root account for this. You're getting yourself into the weeds stepping outside the default config without understanding what it really does. You will not be able to change the root password using that account without having installed the sudo package and sudoing to root first, for example.
-
I accidentally gave bad advice to a possible solution here, apologies
-
Like I said, you need to use the default admin / root user or use sudo.
Stop logging in as that user you created. Log in as admin or root.
-
Like I said, you need to use the default admin / root user or use sudo.
Stop logging in as that user you created. Log in as admin or root.
I'll try logging in as root and then try different passwords but as I said previously I disabled the default administrative account.
-
Logged in successfully but now the Dashboard keeps saying "Unable to check for updates" and I can't view my installed packages or available packages under the Package Manager due to an error "unable to retrieve package information". This is of course despite having internet access to the pfSense box and having downloaded my AV updates etc on my Windows PC…
Is that indicative of some new significant issue since I had to console and restart so many dozens of times trying to fix my prior issue?
-
JFC dude really?? Seems like you borked the shit out of your install.. As to not finding updates this going going to be dns related.. What is the pfsense using for dns? Are you running the default resolver (unbound) or dnsmasq the forwarder? Where does pfsense point for dns?
Weeks to redo your setup?? Sorry but I just call BS on that to be honest.. Do you have hundreds of vlans all with different rules? Take a backup of your firewall rules, clean install and reload your firewall rules. Should be all of a few minutes.
-
JFC dude really?? Seems like you borked the shit out of your install.. As to not finding updates this going going to be dns related.. What is the pfsense using for dns? Are you running the default resolver (unbound) or dnsmasq the forwarder? Where does pfsense point for dns?
Weeks to redo your setup?? Sorry but I just call BS on that to be honest.. Do you have hundreds of vlans all with different rules? Take a backup of your firewall rules, clean install and reload your firewall rules. Should be all of a few minutes.
I said a week (didn't say weeks) of my free time to set up my box from a default configuration…suffice it to say that I have a complicated setup and quite a few packages...Snort usually eats up the most time to tune properly
I'm using DNS resolver unbound 127.0.0.1 which then points to my default gateway IP address...last night I disabled the resolver and it didn't help...
It does indeed seem that I have borked my install...shame on me...bummer...since other people are having similar problems I suppose I'll try their proposed method of consoling into the device and upgrading via option 13 I believe it was...
-
Solved
-
And what was the issue? Snort?
-
And what was the issue? Snort?
I couldn't determine what caused the inability to check for updates or access the Package Manager, but I solved the issue by accessing the console via serial and using option 13 to update. After a reboot the update check and Package Manager functionality worked like a champ.
-
so reboot?
-
so reboot?
No it wasn't a reboot that fixed it, it was consoling into the pfSense box and upgrading via option 13, which involved a reboot of course.
-
And how do you know this.. Did you reboot it and still have issues with finding updates via gui?
Why was it not finding if there was an update? Was it saying you were on latest, or was it saying could not check? Could not check is a dns or network related issue.
How many packages do you have installed? Snort can be finicky!!
