Messages

TLDR; buying a "dumb" media converter and an SFP-to-RJ45 module, and making a down-up-dhclient script for the interface that runs on boot makes things at least work.

So - after what seems like an age I've got a mostly acceptable workaround.

Step 1 was to order the previously mentioned FS SFP module. It kind of worked, except that it absolutely didn't. `ifconfig` reported the link as "active", but the ISP saw nothing on their end. So instead I went to step 2 and bought an media converter (Omada) and a SFP-to-RJ45 module (Ubiquiti). At first this didn't want to play ball either. The media converter worked nicely. No problems. But the SFP-to-RJ45 was behaving - strangely. Similar to how the ISP supplied SFP module; switching around the speed and duplex modes sometimes would make it work. In the end I, through what seemed like infinite keyboard bashing and countless power cycles, figured out that leaving the "speed and duplex" as default and pulling the interface down, putting it back up, and then running `dhclient ax0` would consistently just - work. So wanging tiny a script in `/usr/local/etc/rc.syshook.d/start/` to down-up-dhclient ax0, and now we're finally and consistently getting a DHCP assignment at boot 🥳

...now I just have to configure the thing so everything actually works. But that shouldn't be that hard, right? 😉

Ok, so I tried some things. But no love.

First off; I was thinking I should fiddle around a bit "on bench" (because I can't sit very comfortably within reach of the other networking equipment and the fiber) to see if I could find something out. To my surprise ax0 was configured as 1000baseLX on boot! 🎊🥳🎉 No carrier obviously, because the fiber is on different floor.

So I plugged everything in where it should be, and - nothing. Back to "autoselect" and no carrier. I tried poking ax0 via the CLI. From autoselect to LX went as expected; nothing. Setting KX then LX worked insofar that the link showed as a-ok, but I couldn't get a DHCP lease. No biggie, I thought, it's probably some ISP shenanigans with not allowing multiple leases on the same line or some such. Just release the lease on the USG and re-acquire on DEC. NOPE! No more DHCP leases for me!

Ok - maybe OPNSense does something when doing things via the GUI? Reboot - fiddle with the GUI - no DHCP 🤬

So now I'm actually one step further away from a working device than I was before 😭 Contemplating trying to get a different SFP module. I know (from work) that they can be a bit temperamental at times, but my searches for a replacement have been - ambiguous. (https://www.fs.com/eu-en/products/20140.html?attribute=10440&id=3952148 is probably ok? According to the spec sheet it shouldn't burn out the ISP side at least 😉) Or maybe getting a "dumb" media converter. But I'd really prefer to use the SFP port on the DEC for internet so I can have both my 2 port LAGG and a dedicated management port, which I've already tentatively configured. Can someone suggest a resonable course of action? I'm really at my wits end here, I feel.
(Using the ISP supplied media converter is - problematic. It's screwed onto the wall in a relatively bad spot, and has been partially painted over. I'm not keen on having to re-paint the walls just for this 😅)

Hmm, I'm gonna have to try that and see what happens 😊 I'll report back on the results when I can find 2 minutes to rub together and do the work 😉
Cheers!

Hi there forum!

I'm having some interesting problems with my (ISP supplied) SFP module (not SFP+ mind you) in my DEC750. I knew from the get-go that it would probably not be as plug-and-play as it was in my old USG 4 Pro, the port being SFP+ and all, but what I've encountered is somewhat beyond me.

I've determined that the SFP module is supposed to run at 1000baseLX (see spec sheet below), and it is quite possible to get it up and running. But it requires some manual work. I've set the module, in `ax0` to run at the specified speed/duplex:
You cannot view this attachment.
But after (re-)booting it looks like this in the console;
You cannot view this attachment.
Specifically the `media: Ethernet autoselect` and `status: no carrier` are a bit troubling, for I hope obvious reasons.
The workaround I've been able to come up with is to set the s/d to 1000Base-KX;
You cannot view this attachment.
which gives me a carrier, but no connectivity. (I'm guessing the final lines are just remnants from previous successful DHCP requests as I re-created the errors and fixes a few times.) Then switching back to 1000baseLX I get both a carrier and proper connectivity until reboot;
You cannot view this attachment.

Things I've tried so far;

• Going from `autoselect` to `1000baseLX` ❌
• Going from `autoselect` to `1000base-SGMII` ❌
• Going from `autoselect` to `1000baseSX` ❌
• Going from `1000base-SGMII` to `1000baseLX/code] ❌
• Setting `1000Base-KX` rebooting and then selecting `1000baseLX` ❌

So, if I've not been clear about what my problem is; I can, after some workarounds, get the link up and working, but I'd like to not have to as it stops me from retiring the USG 4 Pro and switching over the DEC750. I'm fine with having to do some automated post-ax0-up-scripting if that would solve my issue, but I've not found a straightforward way to change the s/d setting via the CLI or where I'd put a script to do it 😅
Thoughts? Idea? Suggestions? Dare I say, solutions? 😁

Thank you for your time regardless!

SFP module spec sheet, if that matters 😉