Access after restore to factory default
-
hello
case 1
iam using APU1d4 and after doing a lot of config i ended up restoring to factory default
there was a pre-message saying it will be on ip= 192.168.1.1 etc. and so after few min i tried pinging the said ip address on all the lan ports and there was no reply at all….question 1. is this what is to be expected?
========
case 2
so i grab a serial cable and found it was back to asking for vlan config, then the wan int and lan int..until it completes and gave the succeess BEEP sound. but to my surprise it is not showing the 16 console menus.question 2. why it is not showing the console menus
Note: i have repeated the scenarios (case 1 and 2) and both was replicated...means the behavior was proven to be like that,,
-
question 1. is this what is to be expected?
Yes.
There was a thread with the same question, last week (?).
What happens is that the list with 'known' NIC driver names are also wiped.
You have to use on-device screen/keybaord (or even the serial cable) to assign theses two NIC's again - as you did before the first major reset == new install.
This isn't a new situation, things are as is for years (decades) now.Some how, this question starts popping up more often now …
question 2. why it is not showing the console menus
Humm …
Need more info - or send me over your device ;)Just a wild guess : pfSense boots and switches the serial bit rate ?
-
1, the ip address on the pre- message was giving a strong message to the user that it was reachable instantly.
2. well no doubt the baud rate was right..the fact that i was able to to redo the config..only thing is that it doesnt show the 16 munu options after booting
-
also 2.2.4 baud=115200 which is not switching
-
Some how, this question starts popping up more often now …
I'd say high profile hacking cases, and privacy concerns are beginning to make people test their contingency planning because hacking is becoming so wide spread and people dont want their data or personal details nicked off their computers at home.