I am ordering this soon, was wondering which sfp+ that support multigig do you use?
This is unfortunately much harder to answer than one would think. The relatively low priced ones are programmed on demand, usually with extremely generic data to ensure compatibility with whatever.. And the hardware inside could change anytime, depending on the price and availability of chips.
So I hesitate giving recommendationsā¦.
The one Iāve had most success with is an older module from FiberStore. It comes coded as an SR module like most of them, but is recognised as copper by the sfp driver based on vendor name āFSā and PN āSFP-10G-Tā. It contains an Aquantia AQR113C phy. But I bought this several years ago so it could be different from what they sell now.
One reason to recommend FiberStore though, is that they do document the phy vendor and power consumption of their different SFP+ copper modules. And they also provided me with a spec of the āRollBallā protocol when I asked for documentation of how to access the phy registers. So thatās working by more than just accident.
Iāve had less success with the cheaper AliExpress alternatives. Harder to know what you get, even if the sellers often request eeprom programming preferences.
2 Likes
fair enough, thank you, will start researching fs website and hope for the best
I recently bought this one: https://de.aliexpress.com/item/1005008290777883.html. It works well the BPI R4 and the Onti Switch with original firmware. It also works on OpenWRT (for some reason it currently flaps as you can read above but I guess I will figure that out eventually - might be the cable or the other side). Gets reasonably hot (as most Copper modules do). You definitely want some active cooling if you use more than one of those.
1 Like
I've had better luck on my 10G switch using the 10/2.5/1 SFP+ in 1G mode than using a dedicated 1G SFP module. My 1G module flaps up/down too.
On original Firmware or OpenWRT? Seems like I only get flapping in OpenWRT. Need to debug this a bit more though.
My Onti still runs on 6.6 (r29961-79f097faae to be exact). Contemplating an update but wondering about two points:
- Is 6.12 stable enough for daily use (6.6 has been rock solid)?
- Whatās the state on support for 2.5gbit copper SFP+? 6.6 needed a patch for thatā¦
Any comments would greatly be appreciated.
Iāve been running 6.12 on my RTL9303 and RTL9302 since support was added. Rock solid stability.
2 Likes
That should work now in general. Only modules that require auto-negotiation to be disabled still need a small patch: https://github.com/openwrt/openwrt/pull/19518
1 Like
Thanks, just flashed from firmware selector, seems to work just fine.
Slightly offtopic question but I wanted to ask anyway: why we canāt flash the OpenWRT image directly? For what I see with i.e. Cudy devices, there is an image provided by Cudy that installs an old version of OpenWRT that disables some signing requirements on the device? If thatās the reason, is there a safe way to test if different versions of official firmware may have this check disabled so we can try to install OpenWRT directly?
is there any guide to configure dhcp snooping using nftables
thanks in advance
For some vendors you can - see Netgear GS308T
However, most people who use this type of switch for a living are used to having serial console access. In case of configuration errors this serial console enables you to regain access to the switch management functions without a full hardware reset that might disrupt user network access.
Plus, once you have access to the console you can proceed without any worries about ābrickingā the device or leaving it in an unreachable state.
Iām familiar with using the serial console. Iām also pretty lazy, so if there was a chance any of the firmware files I have allowed me to skip all the serial console part and just load the software, it is worth trying 
Flashing from OEM firmware should also work on the GS1900 Zyxels. But youāre advised to have a serial adapter ready in case something goes wrong.
BEWARE: You must flash in 2 steps. First flash an initramfs image. Boot from that and then sysupgrade to the final image. And do make sure the switch is configured to boot from the first firmware partition before running sysupgrade (chek thatfw_printsys bootpartitionreturns 0 or fix with fw_setsys)
The OEM firmware might accept an OpenWrt sysupgrade image for flashing, but that will result in a soft brick because it fails to write the complete image to flash. It only validates and writes the kernel part.
3 Likes
Has anyone started a DTS for the XikeStor SKS8300-12X? I just ordered one with back2school and another discount as a low cost (EUR 171 incl. shpping) way to get a RTL931x based switch to play around with on cold winter evenings.
I donāt suppose anyone would have SVD files for the rtl838x / rtl839x / rtl930x / rtl931x chip families already?
Iām trying to reverse engineer a bit of the PoE stuff from the Hasivo switch range (rtl930x / rtl931x series) and it would be great if I could easily tell Ghidra what addresses all the peripheral registers and flags were at.
If itās not already done, then Iāll likely try to find a way to autogenerate it from the register listings at https://svanheule.net/realtek/
1 Like
- Autogenerated by https://github.com/svanheule/realtek-registers
- Autogenerated from files like https://github.com/plappermaul/realtek-doc/tree/main/sources/rtk-dms1250/src/hal/chipdef
1 Like
I tried balance-xor and 802.3ad with 2 links to between GS1900-24E and a mediatek openwrt device and I cant get it to work. Sometimes ping goes through and sometimes absolutely nothing. And sometimes the switch kinda crashes like a memory leak (I suspect a loop). Before I had both modes working between the same mediatek openwrt device and a TPLINK switch with Broadcom so I config should not be an issue. Can someone atleast throw me a bone if bonding should be working?
Im doing this on 6.6. Should 6.12 be better?
EDIT: On 6.12 with one of the modes:
-
ping from switch to mediatek works and the other way around
-
ping from client connected to mediatek to switch works but not the other way around
Why would switch be pingable but client connected to the switch cant ping through bond? Something is seriously broken at L2?
EDIT2: Can I revert to stock firmware?
EDIT3: Flashing stock .bix with āsysupgrade -Fā reverted to OEM.
Hi @Everyone,
Can anyone help us with DTS file for a HW with below details ? We are quite unable to decide the parameters to fill in the DTS file.
The HW we have is from UniPoE, we want to check if it can come up with OpenWRT based FW.