pfsense 2.7.2 - realtek sfp port down after reboot

Domex

@stephenw10
this is the module "Genuine Connector SFP I/O Dell OptiPlex Wyse 5070/57GKF 057GKF"

ifconfig re1 down; ifconfig re1 up doesn't solve

ifconfig re1 media autoselect doesn't solve

unlpug the F/O cable doesn't solve

The only solution is hot unplug cable and SPF module

stephenw10

@Domex said in pfsense 2.7.2 - realtek sfp port down after reboot:

Genuine Connector SFP I/O Dell OptiPlex Wyse 5070/57GKF 057GKF

Hmm, OK so something fairly custom then.

What is the module you're using?

Have you tried other modules?

Domex

@stephenw10
The module is DPN-100 (D-Link)
It is provided by FTTH provider.
I can't replace with another one, they register the GPON S/N.

(I have another one, huawei, but I don't know how can I overwrite the SN to bypass their check)

stephenw10

Well I'd want to try the NIC with any other SFP module just to be sure it links correctly at boot. So any 1G SFP module linked to something local.
Those GPON modules can be quirky. But so can Realtek NICs....

Domex

@stephenw10
I tryed with another module, reboted 3 time, all the times, the led starts blinking.

Then I halt 3-4 times with with D-Link module and started succesfully, till suddently again the problem...

It happen frequently but not always...

stephenw10

Hmm, I would probably try to test in some other OS if you can. Make sure it's not a hardware issue.

Though I'm not sure there's much we can do. Did you confirm it's loading the alternate driver? You see the updated driver version in the boot log?

Domex

@stephenw10 said in pfsense 2.7.2 - realtek sfp port down after reboot:

You see the updated driver version in the boot log?

I'm not sure it is mounting the updated version.
just run this command:
pkg install realtek-re-kmod

and added (in bold) 2 rows into the /boot/loader.conf

kern.cam.boot_delay=10000
kern.ipc.nmbclusters="1000000"
kern.ipc.nmbjumbop="524288"
kern.ipc.nmbjumbo9="524288"
opensolaris_load="YES"
zfs_load="YES"
kern.geom.label.gptid.enable="0"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
opensolaris_load="YES"
zfs_load="YES"
if_re_load="YES"
if_re_name="/boot/modules/if_re.ko"
boot_serial="NO"
autoboot_delay="3"
hw.hn.vf_transparent="0"
hw.hn.use_if_start="1"
net.link.ifqmaxlen="128"
machdep.hwpstate_pkg_ctrl="1"
net.pf.states_hashsize="524288"

What should I look for boot log?

If I connect the same module on another router Zyxel EX5601 (the one the FTTH vendor gave me), I never see the problem, it always boot and and the wan interface starts successufully

stephenw10

The driver version is printed at boot from the alternative driver like:

[24.03-RELEASE][admin@apu.stevew.lan]/root: dmesg | grep re0
re0: <Realtek PCIe GbE Family Controller> port 0x1000-0x10ff mem 0xf7900000-0xf7900fff,0xf7800000-0xf7803fff irq 16 at device 0.0 on pci1
re0: Using Memory Mapping!
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: version:1.99.04
re0: Ethernet address: 00:0d:b9:33:35:10
re0: Ethernet address: 00:0d:b9:33:35:10

The default driver does not show a version.

Domex

@stephenw10 said in pfsense 2.7.2 - realtek sfp port down after reboot:

dmesg | grep re

this is mine
(dmesg | grep re1) copied the part related re1, my WAN.

re1: <Realtek PCIe GbE Family Controller> port 0xd000-0xd0ff mem 0xa1104000-0xa1104fff,0xa1100000-0xa1103fff at device 0.0 on pci2
re1: Using Memory Mapping!
re1: Using 1 MSI-X message
re1: ASPM disabled
re1: version:1.98.00
re1: Ethernet address: 6c:2b:59:64:c0:5f
This product is covered by one or more of the following patents:
re1: Ethernet address: 6c:2b:59:64:c0:5f

stephenw10

Ok, it is loading the driver so that clearly doesn't help.

Domex

@stephenw10
My driver version is a bit older than yours.
Do you think I can update?

stephenw10

There's a slightly newer driver in Plus but I'd be very surprised if that made any difference on that NIC.
You can see what's been included here:
https://github.com/alexdupre/rtl_bsd_drv/tree/v1.99

Domex

@stephenw10
I did another test:
Halt the system many time and every time also unplugged power cable.
All the time the WAN went up succesfully....

Domex

This post is deleted!

stephenw10

Hmm, so it only fails to reconnect when coming out of standby?

The system could be holding the NIC powered to allow WoL etc. There may be some BIOS settings to disable that.