Messages

What would be the difference between WAN and pppoe0?

One is just an assigned name for the underlying PPPoE interface - unless you made the mistake of naming the physical NIC (or VLAN) as WAN.

That is the problem with many of those videos: There is no such thing as a step-by-step tutorial, because each situation is different, like your example clearly shows.

You have to understand how things work, otherwise you will be stuck at each crossing.

With a PPPoE connection, you can have one of these topologies on the WAN side:

1. ISP ONT/modem -> physical NIC ("ONT") -> PPPoE interface ("WAN")
2. ISP ONT/modem -> physical NIC ("ONT") -> VLAN ("VLANXX") -> PPPoE interface ("WAN")

With OpnSense, you have either two or three logical interfaces. Name them according to the scheme above. Firewall rules should always be applied to "WAN", which usually is the same thing as "pppoe0". You do not even need explicit names for ONT and VLANXX, unless you want to have direct ONT/modem access. You also do not need firewall rules for "ONT" either, as per default, everything is blocked.

You obviously use it differently, which causes your confusion:

ISP ONT/modem -> physical NIC ("WAN") -> PPPoE interface ("???")

Many thanks

I have a very simple setup. No VLANS. 

ISP -> PPPoE (WAN) -> LAN Devices

So I did apply the firewall rules to the WAN interface as per the video, so what could be wrong?

Is there a way to check logs or something else that I can identify the problem?

Hi

I have setup wireguard instance and clients as exactly in this video, it clearly shows

what to do.

However when I connect to the server, it establishes connection but packets are not received.

The only difference is I have pppoe connection (as interface), however I have  allowed Wireguard port on the WAN firewall only.

Do I need to open firewall port on pppoe interface rather than WAN? Or how can I trouble shoot? Thanks.

Thank you,

As a starting point, I will try as you have suggested, 1 network range for each physical interface.

So from what I understand, these separate LANs still can communicate with each other and to eliminate this, I will need firewall rules to block traffic. I need a search on this.

Out of curiosity, if my whole network is good enough with 3 separate LANs, and I already have separate ports on the firewall, I won't need to implement any VLANs?

Is there any advantage to implement VLANs, I believe the goal is to create separate networks, which I am already doing it with separate physical ports?

Hi

I am new to Opnsense and watching related videos.

I have a 5 port firewall device where 1 is WAN and the other is LAN by default.

Just wondering without buying managed switches, use the existing unmanaged switches that I have and use:

The default LAN port for trusted network (192.168.1.0 range)

The 2nd LAN port for Guest network (192.168.10.0 range)

The 3rd LAN port for IoT devices
(192.168.20.0 range)

And add use the remaining LAN port same way if required.

The ports do not have to communicate with each other, as long as there are assigned correct IP ranges and have access to the internet, that will be a start for me.

Can you explain briefly or send me links to read how this can be done?

VLANs using the same physical port and managed switches will be my next step forward.

did you try my last suggestion, what was the outcome ?

Yes your solution has worked. I removed the USB  mouse (kept the keyboard on) and rebooted the system. I can now see the console.

I am not asking the reason (do I need to know?) At the end of the day we would need keyboard, not the mouse using the console?

All I can guess is that the console needs waking up but that is actually "there". I can't think of a way the console would be only available on boot but not reboot.
Can you try that, reboot, wait for the time when you can get to the UI so the system is fully initialised, then use the keyboard to see if the console (the login prompt in this case) comes up?

Or at a wild guess on a reboot if you are using EFI, that maybe there's a buffer variable kept and is not initialised ? Truly wild guess, thinking aloud here.

Thank you, if anyone else has a suggestion I will appreciate. As I said I am new to Opnsense, if I have to send the hardware back and get another one, I will do so.

Thanks, I've checked and there is only 1 x NVme Drive + with UEFI

I have disabled the boot logo, now I can see attached Image 1 (before this, the screen was blank). Every time I reboot the system, from this stage it does not go forward to the login page.

However, Opnsense boots fine in the end and I can access to the web interface with another device (Image 2)

This now only happens on reboot. If I power on + off, everything works fine.

Let me know the possible causes pls.

If you cannot get a BIOS update from your vendor that fixes it, return the device and buy another brand.

I have got a BIOS update

The crash seems to be fine now however this time every time I reboot, after the BIOS beep, Opnsense does not load?

If I power off the system and turn on, Opnsense loads with no issues. Do you recommend another clean install?

Is there something else I should do?

Thank you for the information, I was not aware of such a problem. Do you recommend a particular mini PC with similar spec or CPU model?

I am very new to Opnsense and purchased a new mini PC with specs below:

Intel Quad Core N100, DDR5 8GB RAM with Intel I226-V Ethernet Controller

However almost everytime I reboot Opnsense it is either stuck at Boot (where it says autoboot 3,2,1, the screen is stuck at 3) or enters kernel panic.

I checked this forum for some solutions, applied suggestions about Bios settings etc.

I replaced the SSD, did memory test, still the same result.

Opnsense seems to work fine when running (I tried 1-2 hours by connecting to the internet) however when rebooted, system crashes.

Where do I start from please? You may request some log files, at what stage and from where do I need to provide them?