Does anyone have any experience of changing the management VLAN on these switches? Whilst you can set the IP of the switch into the subnet you desire, the switch is not accessible unless you are plugged into a port in VLAN1. I don't really want VLAN 1 hanging around, but I can't see any other way to avoid that with this.
Cheap Interesting Chinese 4x2.5g, 2x10G switch, (but also problems with DACs)
- Thread starter EasyRhino
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Well these switches are with basic functions and you cannot change the management VLAN. Anyway I don't see real drawback to use it. For example I have connected this switch to Aruba and my management vlan is 99 there. On the port of the Aruba I have all tagged vlans I need and the vlan 99 is untagged (PVID) so it connects with vlan1 (untagged, PVID) on the trunk port of the chinese switch. In Cisco terminology this is called 'native vlan' which is the same as PVID so you can have different internal vlan mapping on different devices and interconnect them. Btw using vlan1 for management is quite standard and also the Aruba switch I have came preconfigured that way.
Hi. I've done just that (Also bricked my switch ) Any idea how to change the MAC address?? I want to use the "cloned" switch on the same network and they are conflicting.
Thank you in advance.
Last edited:
Well.
I've found out to change the mac address so I'm leaving the info here if anyone needs it.
Someone (way smarter then me)found some hidden factory links and posted to Github and @blunden linked it here.
You have to enter your switch's address and add /ftdft.cgi at the end (192.168.0.13/ftdft.cgi in my case) and you can change it from there.
I hope this is useful to someone if they mess with one of these switches and bricks it.
This is really useful. I've unticked the Chinese language box and now when I log in it's in English only. Oh, and don't forget to save within the "Tools" tab, otherwise when you reboot the switch it will go back to the default settings.
Last edited:
Hi.
Continuing with my struggle to bring the switch back to life (after damaging the flesh chip during desoldering).
I have purchased the flash chips (FM25Q16A, SOP8-208mil).
I have programmed the flesh memory.
After soldering the chip the swich starts to boot up.
A log appears until: "#############Begin to set the web mode". At this point the swich resets, starts to boot from the beginning and so resets over and over.
The program is uploaded correctly (from another working switch).
I suppose there is a UNIQUE ID check (instruction: 4Bh) which differs and for this the program resets.
I even copied the data from the security section (instruction: 48h)
Chuba that the data from the protection section is somehow linked to the UNIQUE ID
Maybe someone has some ideas what to do with this next.
Thanks for the previous suggestions
Continuing with my struggle to bring the switch back to life (after damaging the flesh chip during desoldering).
I have purchased the flash chips (FM25Q16A, SOP8-208mil).
I have programmed the flesh memory.
After soldering the chip the swich starts to boot up.
A log appears until: "#############Begin to set the web mode". At this point the swich resets, starts to boot from the beginning and so resets over and over.
The program is uploaded correctly (from another working switch).
I suppose there is a UNIQUE ID check (instruction: 4Bh) which differs and for this the program resets.
I even copied the data from the security section (instruction: 48h)
Chuba that the data from the protection section is somehow linked to the UNIQUE ID
Maybe someone has some ideas what to do with this next.
Thanks for the previous suggestions
I got one of these - it came with 1.9 firmware. Possibly a return via Amazon ? In any case, I can't change Flow-Control for any port or group of ports.
Set it to ON and Apply, doesn't stick. I think it's kind of necessary though ...
As a test I have two systems, backup (2.5G port 4) and bondi2 (10G port 5). Running iperf3 from backup to bondi2 works fine, no retries. But running from bondi2 to backup, tons of retries
❯ iperf3 -c backup.local
Connecting to host backup.local, port 5201
[ 5] local 192.168.2.115 port 35044 connected to 192.168.2.119 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 172 MBytes 1.45 Gbits/sec 1647 52.3 KBytes
[ 5] 1.00-2.00 sec 173 MBytes 1.45 Gbits/sec 1727 79.2 KBytes
[ 5] 2.00-3.00 sec 173 MBytes 1.45 Gbits/sec 1565 62.2 KBytes
[ 5] 3.00-4.00 sec 174 MBytes 1.46 Gbits/sec 1547 58.0 KBytes
[ 5] 4.00-5.00 sec 173 MBytes 1.45 Gbits/sec 1555 43.8 KBytes
[ 5] 5.00-6.00 sec 172 MBytes 1.45 Gbits/sec 1753 48.1 KBytes
[ 5] 6.00-7.00 sec 173 MBytes 1.45 Gbits/sec 1546 58.0 KBytes
[ 5] 7.00-8.00 sec 173 MBytes 1.45 Gbits/sec 1464 58.0 KBytes
[ 5] 8.00-9.00 sec 172 MBytes 1.45 Gbits/sec 1683 62.2 KBytes
[ 5] 9.00-10.00 sec 173 MBytes 1.45 Gbits/sec 1710 52.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.69 GBytes 1.45 Gbits/sec 16197 sender
[ 5] 0.00-10.00 sec 1.69 GBytes 1.45 Gbits/sec receiver
That's indicative of the 10G side just shoveling packets down the pipe to the 2.5G side, which can't handle the rate.
Set it to ON and Apply, doesn't stick. I think it's kind of necessary though ...
As a test I have two systems, backup (2.5G port 4) and bondi2 (10G port 5). Running iperf3 from backup to bondi2 works fine, no retries. But running from bondi2 to backup, tons of retries
❯ iperf3 -c backup.local
Connecting to host backup.local, port 5201
[ 5] local 192.168.2.115 port 35044 connected to 192.168.2.119 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 172 MBytes 1.45 Gbits/sec 1647 52.3 KBytes
[ 5] 1.00-2.00 sec 173 MBytes 1.45 Gbits/sec 1727 79.2 KBytes
[ 5] 2.00-3.00 sec 173 MBytes 1.45 Gbits/sec 1565 62.2 KBytes
[ 5] 3.00-4.00 sec 174 MBytes 1.46 Gbits/sec 1547 58.0 KBytes
[ 5] 4.00-5.00 sec 173 MBytes 1.45 Gbits/sec 1555 43.8 KBytes
[ 5] 5.00-6.00 sec 172 MBytes 1.45 Gbits/sec 1753 48.1 KBytes
[ 5] 6.00-7.00 sec 173 MBytes 1.45 Gbits/sec 1546 58.0 KBytes
[ 5] 7.00-8.00 sec 173 MBytes 1.45 Gbits/sec 1464 58.0 KBytes
[ 5] 8.00-9.00 sec 172 MBytes 1.45 Gbits/sec 1683 62.2 KBytes
[ 5] 9.00-10.00 sec 173 MBytes 1.45 Gbits/sec 1710 52.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.69 GBytes 1.45 Gbits/sec 16197 sender
[ 5] 0.00-10.00 sec 1.69 GBytes 1.45 Gbits/sec receiver
That's indicative of the 10G side just shoveling packets down the pipe to the 2.5G side, which can't handle the rate.
I'm a dummy. The pulldown reverts of Off, but the config table below shows that flow-control was turned on. Sheesh 
With it turned on performance was much better, still retries but not the levels of before
❯ iperf3 -c backup.local
Connecting to host backup.local, port 5201
[ 5] local 192.168.2.115 port 38750 connected to 192.168.2.119 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 177 MBytes 1.48 Gbits/sec 25 513 KBytes
[ 5] 1.00-2.00 sec 175 MBytes 1.47 Gbits/sec 5 587 KBytes
[ 5] 2.00-3.00 sec 174 MBytes 1.46 Gbits/sec 4 496 KBytes
[ 5] 3.00-4.00 sec 174 MBytes 1.46 Gbits/sec 1 576 KBytes
[ 5] 4.00-5.00 sec 174 MBytes 1.46 Gbits/sec 4 482 KBytes
[ 5] 5.00-6.00 sec 174 MBytes 1.46 Gbits/sec 1 560 KBytes
[ 5] 6.00-7.00 sec 174 MBytes 1.46 Gbits/sec 6 461 KBytes
[ 5] 7.00-8.00 sec 174 MBytes 1.46 Gbits/sec 1 554 KBytes
[ 5] 8.00-9.00 sec 175 MBytes 1.47 Gbits/sec 6 460 KBytes
[ 5] 9.00-10.00 sec 174 MBytes 1.46 Gbits/sec 1 549 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.70 GBytes 1.46 Gbits/sec 54 sender
[ 5] 0.00-10.00 sec 1.70 GBytes 1.46 Gbits/sec receiver
With it turned on performance was much better, still retries but not the levels of before❯ iperf3 -c backup.local
Connecting to host backup.local, port 5201
[ 5] local 192.168.2.115 port 38750 connected to 192.168.2.119 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 177 MBytes 1.48 Gbits/sec 25 513 KBytes
[ 5] 1.00-2.00 sec 175 MBytes 1.47 Gbits/sec 5 587 KBytes
[ 5] 2.00-3.00 sec 174 MBytes 1.46 Gbits/sec 4 496 KBytes
[ 5] 3.00-4.00 sec 174 MBytes 1.46 Gbits/sec 1 576 KBytes
[ 5] 4.00-5.00 sec 174 MBytes 1.46 Gbits/sec 4 482 KBytes
[ 5] 5.00-6.00 sec 174 MBytes 1.46 Gbits/sec 1 560 KBytes
[ 5] 6.00-7.00 sec 174 MBytes 1.46 Gbits/sec 6 461 KBytes
[ 5] 7.00-8.00 sec 174 MBytes 1.46 Gbits/sec 1 554 KBytes
[ 5] 8.00-9.00 sec 175 MBytes 1.47 Gbits/sec 6 460 KBytes
[ 5] 9.00-10.00 sec 174 MBytes 1.46 Gbits/sec 1 549 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.70 GBytes 1.46 Gbits/sec 54 sender
[ 5] 0.00-10.00 sec 1.70 GBytes 1.46 Gbits/sec receiver