NUC running OPNsense 24.7 can't see WAN interface from Adtran 422G GFast NTU

[Old_Rager]

Hey Guys,

A bit of a newbie here but I recently upgraded my internet service at home in Australia to 500Mbps down and 40Mbps up on a FTTB solution.  To achieve this, my ISP provided a dedicated NTU (being an Adtran 422G GFast NTU) that then plugged directly into the WAN port of my existing TP-Link AX-5400 WI-FI 6 modem/router that was also provided by my ISP.  What I am wanting to do now is to insert a dual gigabit ethernet port NUC running OPNsense (version 24.7) between the NTU and WIFI router - the latter which will be converted to a simple access point with the OPNsense NUC running all firewall, DHCP, and DNS activities for my network.

As can be seen in the attached OPNsense screenshot, the WAN interface is not being detected.  The only things active (plugged in) on my network in the attached screenshot was my NTU (that is plugged into the wall by an RJ11 cable) and the RJ45 cable that goes from it to the NUC.  There was no downstream connectivity beyond the NUC and yet OPNsense still cannot see the WAN interface at all after it boots.

Any help here would be greatly appreciated.

[dseven]

You need to find out what configuration your ISP requires (unless you already know) - perhaps they do PPPoE (in which case you'll need a username and password), or/and use a tagged VLAN.

It's also possible that you are required to use a registered MAC address - if so, you might be able to get around that by spoofing the one from the ISP router.

Are you able to access the LAN side of your OPNsense NUC? If not, you may have the NICs backwards....

[Old_Rager]

Hey, thank you for that.  Yes they do PPPoE and do require a username and password.  The only thin is, I do not know how to get OPNsense to use that username and password during its bott-up sequence.

With respect to it being plugged into the incorrect port on the NUC.  I have tried both ports but to no avail.

Is there an easy way to get to input the WAN username and password into the bootup script to help OPNsense access the WAN interface that you know of?

Again, thank you very much for your response - very much appreciated indeed!!! 😉

[Patrick M. Hausen]

Is there an easy way to get to input the WAN username and password into the bootup script to help OPNsense access the WAN interface that you know of?

In the UI go to Interfaces > WAN, set  IPv4 Configuration Type to PPPoE and further down the page enter your credentials ...

[dseven]

With a PC connected to the LAN, point a browser at 192.168.1.1. The first time you login to the WebUI as root, you should be presented with a wizard. One of the wizard steps is "Configure WAN Interface". That's where you'd select PPPoE and enter your credentials. Alternatively (or if you've already dismissed the wizard) you could navigate as Patrick suggests...

[Old_Rager]

Awesome Guys - thank you very much.  Will do this tomorrow as my wife is working from home today so I can't get on to do the changes just yet.  Again, big thanks indeed!!!  😜

[Old_Rager]

Just by way of update, I wasn't able to get my existing TP-Link AX5400 router to work as a simple access point so that I can login to the NUC running OPNsense even after following everything that this guy said to do from the 2:20 min mark - https://www.youtube.com/watch?v=krcjZNSXsGs&t.  I did as the guy said, but when I rebooted the NUC, it hung at a certain (I should have taken a photo, soz) and would go no further in the boot process until I unplugged the router.  I will try again on Monday Oz time as my wife needs the network up when she's home on the weekend as I need to go back and reconfigure and set everything up again.  😔

So, this is a real bummer for me as I am now reliant on getting the following TRENnet TEG-S762 switch (https://www.amazon.com/dp/B09LNLMH9Y?tag=toptenreviewed-20&linkCode=ogi&th=1&keywords=10+gigabit+switches) which is going to take a while as there is nil stock here in Australia.  If anyone else knows of a switch like the TRENDnet TEG-S762 that they think will do the same job, please do not hesitate in reaching out to me here as I unfortunately cannot log in to the OPNsense GUI without having at least some sort of switch on my network to access the 192.168.0.1 interface, yes?!? 🤔😒

[Old_Rager]

With a PC connected to the LAN, point a browser at 192.168.1.1. The first time you login to the WebUI as root, you should be presented with a wizard. One of the wizard steps is "Configure WAN Interface". That's where you'd select PPPoE and enter your credentials. Alternatively (or if you've already dismissed the wizard) you could navigate as Patrick suggests...

DSeven, will the OPNsense device be on 192.168.0.1, or will it default to 192.168.1.1?  I only ask now because I only just saw this and had set my router to 192.168.0.1 - and not 192.168.1.1 as you have stated here? 🤔

[dseven]

192.168.1.1 is the "out of the box" default for OPNsense. You could change it, of course....

[Old_Rager]

DSeven - thank you!  Wow, what a bad mistake from me...  🤣😔

[Old_Rager]

DSeven, well I disabled the router's DHCP and gave it a static 192.168.1.2 address, and the attached pic is what occurred during the bootup of the OPNsense bare metal device...  😒

After a minute or so, it continued to boot but my PC couldn't see either 192.168.1.1 or 192.168.1.2

Any thoughts on where I should go from here?

[dseven]

Google says that ng_ubt is a Bluetooth USB thing, so I don't think that's related - it's just a driver trying to initialise in the background (you can see the same message further up in the screenshot).

What are you trying to do now? I thought you were trying to setup PPPoE on your WAN interface. When you say you disabled DHCP, do you mean the DHCP server for LAN, or DHCP client on your WAN interface, or? Which interface did you put 192.168.1.2 on, and why?

[Old_Rager]

Hey DSeven, did a newb error.  I plugged the ethernet cable from my OPNsense bare metal box into the WAN port of the router that I had configured to just be a WAP.  After plugging it into just a normal network port, I was able to get the network up and running - I.E., I could ping the OPNsense box but could not get through to it from my browser as per attached pics.  Any chance in letting me know what I am doing wrong here?  🤔

[dseven]

That all looks fine - it's just that OPNsense is using a self-signed certificate, so your browser can't verify it. You should be able to click on "Advanced", then something to the effect of "Continue Anyway".

[Old_Rager]

Oh my goodness, getting old is not fun.  I should have thought of this as I thought the issue was it not being HTTPS compliant due to the HTTPS being strike through on the pic.

I really do hate getting old as your brain is nowhere like it used to be when younger.  I was an MSCP back in the day on Windows 3.1.  Again, thank you for your patience here.  I will try again tomorrow when my wife's not working from home (as she is today)... 😜