Proscend 180-t vdsl2 SFP Support
-
I think our next move is to order a few more of the
Proscend 180-T devices and pop them into a selection
of 2100/4100/6100/7100's and see how they perform
on Australian NBN connections.I think there are two main points here in this case for you.
- Is it compatible to the lokal ISP xDSL
- How it performs in x86_64 and the ARM (Marvel) hardware (compatibility)
Would be nice to hear about that in the future if will
be able to tell something about real life made experiences.We have a several of the APU6B4, a bunch of Supermicro
C3958/C3858 devices together with pfSense.And now we are also want to insert sfp modems into this
boxes. -
@madheff23 we did get the VDSL modules working, and they are working well.
The key trick for us on the 2100 was actaully the pfSense version - we needed to update (we were running 2.4.5x).We didn't need to do any specific VLAN tagging on our service (i.e. ISP didn't require), but in the case where we do need to pass a VLAN tagged traffic, we created a vlan interface on top of the WAN interface.
I haven't got round to writing the documentation on doing that yet; I will get to it but in the meantime happy if you DM me and we can work it through together.
-
We have uncovered what we believe to be a bug with the Netgate 2100 SFP port, where the link state is lost when the device reboots, and requires the module to be removed from the SFP port and then re-inserted.
We have tested the Netgate 2100, 4100 and 6100 (Base models, but I don't expect there would be any material difference here for the MAX editions). The process we have gone through is:
- Power on Device
- Observe Media state in "Status -> Interfaces"
- Insert SFP Module
- Observe Media state in "Status -> Interfaces"
- Reboot appliance
- Observe Media state in "Status -> Interfaces"
For the 4100 and 6100 appliances, the Media state is consistent across reboots, showing the expected media state. For the 2100, the media state is as expected after inital installation into the appliance, then reverts to "none" after reboots.
The results are consistent between power loos / power restore, and graceful reboots.
The Combo ports were used in all cases (i.e. not the dedicated WAN3/4 on the 6100).Confusingly, the 2100 continues to power the SFP module, and power to the SFP module is not interrupted during the graceful reboot cycle. Any troubelshooting steps have proven unhelpful on the 2100 to recover the link state - such as disable / enable the port, down/up the interface (ifconfig xxxx down && ifconfig xxxx up, etc). The only tangible change was physically remove and re-insert.
Screen shot of no media state after a 2100 reboot: (which is also represented in the ifconfig output at console with "media: Ethernet autoselect (none)"
Screen Shot of expected state (observed on 4100 and 6100 consistently):
I'll be raising support request with Netgate to see if we can ascertain exactly what the difference here between the 2100 and the 41/6100 devices.
I'll post back here when we have an update for those who are interested.
-
@etsau What software version are you running?
@etsau said in Proscend 180-t vdsl2 SFP Support:
I'll be raising support request with Netgate to see if we can ascertain exactly what the difference here between the 2100 and the 41/6100 devices.
They are completely different platforms. The ARM processor in the 2100 does not use the same hardware as the Atom processor in the 4100/6100 series devices.
Ryan
Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
Requesting firmware for your Netgate device? https://go.netgate.com
Switching: Mikrotik, Netgear, Extreme
Wireless: Aruba, Ubiquiti -
@rcoleman-netgate Sorry for not including that!
We (months ago) had 2.4.5x - with which nothing worked.We then upgraded to 22.01 - the device was detected and we were all good.
The testing we've just completed last week and posted a few minutes ago; was tested on version 22.01 and version 22.05.
-
@rcoleman-netgate re Hardware - acknowledge the difference in processor - do you know anything about the combo ports? I was thinking something like that might be relevant.
Does feel odd that's a problem if it's the CPU architecture, but this is well outside my wheelhouse.
-
E ETSAU referenced this topic on
-
@etsau They're not the same NICs, and thus not the same drivers.
On the 4100/6100 they are Intel SoC NICs, on the 2100 they're Marvell.Ryan
Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
Requesting firmware for your Netgate device? https://go.netgate.com
Switching: Mikrotik, Netgear, Extreme
Wireless: Aruba, Ubiquiti -
@rcoleman-netgate do you see this as being something that's fixable in some way? Not sure about other regions but we're seeing a good amount of interest (Australia), and it's really a very tidy solution for the 2100
I'm willing to put a bit of effort in to see what we can do.
-
@etsau I'll leave this ticket for my colleague to see in the morning... he has better thoughts when it comes to the hardware and engineering side. If he has anything for me to test in the lab he'll reach out to me directly.
Not sure what we can do about reproducing your specific media converter, however. It might be a limitation of the hardware device itself.
Ryan
Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
Requesting firmware for your Netgate device? https://go.netgate.com
Switching: Mikrotik, Netgear, Extreme
Wireless: Aruba, Ubiquiti -
@rcoleman-netgate Thank you very much for your assistance there. FWIW, we are a partner for Australia.
-
What does
ifconfig -m mvneta0show in either state? -
@stephenw10 the below are my notes from doing the testing on the 2100 a couple days ago - I didn't use the -m argument; but can re-run using the -m if needed:
OKAY - so; from boot (of a factory defaulted 2100) PROSCEND modem was inserted from boot (and had line sync...) enabled ssh; checked interface stats: mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> Followed by a re-seat: (no other changes): mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseSX <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> graceful restart: mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> Followed by a re-seat: mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseSX <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>Is this sufficient or would you like me to get fresh results with the "-m"?
-
The -m flag asks ifconfig to show what media types it thinks are available which could be important here since the presence of the module would dictate that. If the NIC for some reason simply doesn't see the module or maybe sees it as the wrong type that could be a clue.
Steve
-
@stephenw10 Please find below the ifconfig logs requested. The initial set are after a restart with the SPF module installed. The second is with the unseating are reseating of the SPF module, pfSense remained on during the seating of the card.
After device startup
[22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root:Un-seat and re-seating SFP module
[22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseSX <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseSX <full-duplex>) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: -
Hmm, so more like it just doesn't see the device in the combo port.
If you connect an active cable to the RJ-45 port and disconnect it without removing the SFP module does that trigger the port switch and allow it to come up?
Steve
-
@stephenw10 We have run through the tests suggested on the RJ-45 port and included two additional tests which may assist you. Please see below the results:
After device startup
[22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>Plugged in active RJ-45 cable alongside SFP module in the combo port
[22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>Cable removed from RJ-45 in combo port
[22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>Cable plugged in, Cycle interface state, down then up.
[22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 down [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 tentative scopeid 0x1 media: Ethernet autoselect (none) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 tentative scopeid 0x1 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 up [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>Cable out, cycle interface down then up.
[22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 down [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 tentative scopeid 0x1 media: Ethernet autoselect (none) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 tentative scopeid 0x1 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 up [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> [22.05-RELEASE][admin@pfSense.home.arpa]/root: ifconfig -m mvneta0 mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> capabilities=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: Ethernet autoselect (none) status: active supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media none nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> -
Hmm, so no observable change...
You tried setting the interface to 1000baseSX <full-duplex> fixed?
-
@stephenw10 yes indeed - we've tried a few of the of static media states (we originally thought the interface HAD to be set to 1000base SX) - but since disproved that.
When we have the link set statically, the ifconfig output shows:
mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: WAN options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE> ether 00:e0:ed:bc:2e:eb inet6 fe80::2e0:edff:febc:2eeb%mvneta0 prefixlen 64 scopeid 0x1 media: Ethernet 1000baseSX <full-duplex> (none) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>Quite the conundrum.
If it's interesting, we did have to be on firmware 21.01 or later before the sfp port would work at all. -
Hmm, there may not be much we can do here. The combo port in the 2100 is hardcoded to be only 1000baseSX in the SFP. It doesn't detect the media there.
The correct fix here would probably be at the driver level or even in the hardware description but to so that would require significant developer resources for a device relatively few users will ever see. That's unlikely to happen unfortunately. An alternative might be a startup script that power cycled the module. I'm looking to see if that's possible.If one of our developers in Australia hits this they might suddenly be motivated.
Steve
-
Thanks @stephenw10 ,
Do you have any insights on why the device is fine in all the other models, and only the 2100 has issues? I don't have anyone with skills to edit drivers or firmware for either of the devices; but it just seems a shame that the modem works fine if inserted after boot; but the 2100 can't detect it if present at boot.
I appreciate there would be a reasonable workaround to power cycle the port - do you know of any way I can do that? (obviously a down / up on the interface has no effect).
