Can’t access opnsense on https://192.168.1.1

[12Mexxx]

I have the protectli vault FW4B preconfigured with opnsense. After a session where i failed to connect to the internet, with the PPOE settings given to me by Vodafone UK (I tried VLAN 101 and 900) I decided to reset my vault to default settings. Now I can’t connect to opnsense on https://192.168.1.1. Am i missing something here? I have tried my initial custom LAN IP address which is not working as expected. I’m totally new to opnsense. Can anyone suggest what to do other than pulling my hair out 😀?

[Maurice]

Use the serial console to check what's going on and, if required, assign interfaces and IP addresses.

Cheers
Maurice

[12Mexxx]

Thanks for the suggestion. Sorry to be such a pain but I am a newbie... From what I have read I need to connect the cable to the COM port but will need a USB to serial adapter to connect with my laptop. Does that sound right? I will have to go grab one real quick.

[Maurice]

Yes that's right. Or you can get a USB to RJ45 console cable, these have an integrated converter chip.

[12Mexxx]

Or you can get a USB to RJ45 console cable, these have an integrated converter chip.

I got one of that. will give it a try

[12Mexxx]

This is what I've got. It looks ok to me _ I can see LAN is set at 192.168.1.1/24. Any ideas what next to do?

[chemlud]

...plug the RJ45 in the other port...

[12Mexxx]

Quick question…is igb0 supposed to be LAN or WAN?

[12Mexxx]

I see what the problem is. The ports were switched when I reset opnsense. My WAN port is now LAN and LAN port is WAN. I switched them around (plugged WAN to LAN and vice versa) and now I can reach opnsense on 192.168.1.1.
I’ve heard this talked about before.
Any newbie proof way to reassign them real quick?

[chemlud]

watch boot on serial consol, as you did. Log in as root and choose from menu "assign interfaces"...

[12Mexxx]

Thanks. I suppose that means get to the screen i showed earlier and then use a command to get to the menu… I’m sorry to be a pain. Newbie here

[Patrick M. Hausen]

On a newly installed OPNsense the first port is always LAN and the second is WAN. If your device has some labels printed above or below the network ports - this is just paint, it bears no connection to what a particular firewall distribution actually does.

pfSense assigns LAN and WAN the other way round. But it was them who changed it after the OPNsense fork.

Chinese manufacturers of firewall appliances print on their devices whatever they see fit. Just ignore the labels.

HTH,
Patrick

[12Mexxx]

Thanks. My FW4B came with opnsense preinstalled and the first port was WAN corresponding to what was printed on it. I guess that’s why I was bothering to change it. But I agree with you.. ignoring it will save me all the trouble anyway.

[Patrick M. Hausen]

Ah ... so obviously that's why it switched ports after the config reset.

The device comes with 4 identical network interfaces - igb0, igb1, igb2, igb3. Which interface is assigned to which role is at the discretion of the software running on the device. The labels are just paint.

If you have a nice "professional" label printer, you might decide to stick something on top of the factory print.

I also have a Protectli FW4B but I run all interfaces but WAN as VLANs on top of a link aggregation - which makes the printed labels extra meaningless.