*) added option to set forced 2.5G for SFP+ ports;
*) css610: added a distinct “Health” menu;
*) css610pi: updated PoE firmware;
*) fixed multicast forwarding after disabling IGMP snooping;
*) fixed SNMP ifSpeed OID reporting in certain cases;
*) ftc11xg: fixed DHCP packet forwarding;
*) limit the number of displayed GUI “Hosts” entries up to 512;
*) improved SwOS Lite web interface stability and responsiveness;
Follow up:
On CSS610 I set an S+RJ10 to forced 2.5Gb, connected to ether1 of AX3 using VLAN trunk.
Link becomes active. So far so good.
On AX3 log files I see it determines speed as being 2.5Gb, which is ok however …nothing passes (after the facts I can see in log files what happened).
Only when I enable autonegotiation, I can get access via that link.
I understand what you say but I don’t understand why that would be needed… doesn’t make sense from a practical point of view.
Auto MDX is something from the previous century !
Anyhow, SUP-146041 created. Let’s see what support says about it.
Actually I believe onnoossendrijver is correct, modern ethernet controllers use standard IEEE 802.3ab auto negotiation protocol to automatically determine MDI, speed and duplex and for a practical standpoint it makes perfect sense, and once you disable auto negotiation you must use crossover cable…
It is Rev 2.
That module will adjust on its own to lower speed when needed (e.g. when connected to 2.5G port of AX3) but it can not be configured to do so (e.g. when connecting 2 S-RJ10 to each other and not wanting full 10G because it will burn your fingers).
Good to see more development, I’m running a few Netpower Lite 7R devices currently at 2.17.
Please consider feature requests for new releases:
option to not save all config changes immediately, instead keep them only in RAM, and have a separate “Save” button (this way previous working config can be restored by reboot/power-cycle if you lost access due to wrong change)
option to reboot (optionally including power-cycling the PoE powered device) after some number of failures to get IP address by DHCP, to recover from wrong config change or hung uplink radio without power-cycle (tricky to do with reverse-PoE redundant power from multiple customers)
