Can you please send screenshots of how you did it ? Or maybe explain it ? Thank youI tried, it works
Keeplink KP-9000-9XHPML-X-AC / fw 100.9.4
Horaco 2.5GbE Managed Switch (8 x 2.5GbE + 1 10Gb SFP+)
- Thread starter kevindd992002
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Nothing special, i use a static ip (no vlan possibility there) and have the vlans and port memberships configured.
Te SFP+ ports is member of all vlans and connected to my uplink switch on a port that has also all vlans configured.
The GUI is reachable on the static ip address that has its subnet on one of the vlans (from my PC that is part of another vlan and connected to the main switch and router)
Te SFP+ ports is member of all vlans and connected to my uplink switch on a port that has also all vlans configured.
The GUI is reachable on the static ip address that has its subnet on one of the vlans (from my PC that is part of another vlan and connected to the main switch and router)
It does work. I don’t understand how, but I’ve put the ip address I wanted and it’s working. I’m wondering if internally, it’s assigning the static ip to all the interfaces and hope for the best.
Just chiming in about my Horaco HC-SWTGW218AS that I've received from AliExpress today (bought last Monday, that was fast!).
The web interface is even more basic than I was expecting, not even a logo ! But everything works so far. Even my 10Gtek DAC cable between my Cisco switch and the Horaco switch is working perfectly.
One thing I noticed though, is that the RJ45 ports are very hard to clip. Most of my home crimped cables do not clip in the ports but my off the shelf cables do clip if I push them very hard. That is my only complaint so far. VLANs are working great and thats all that matters !
Also the fact that we cant specify the VLAN for management is a bit annoying as I'm not using VLAN 1 on my network and I didn't want to add routing in my OPNsense for VLAN 1, so I ended up doing a port isolation on LAN 8, and assigned access VLAN 1 only on LAN 8. Then I connected this port to an access port on my other switch that was set to Access VLAN 10. I'm wasting a port, but at least all is well now as that switch's VLAN 1 is now flagged as VLAN 10 just like the rest of my network.
The web interface is even more basic than I was expecting, not even a logo ! But everything works so far. Even my 10Gtek DAC cable between my Cisco switch and the Horaco switch is working perfectly.
One thing I noticed though, is that the RJ45 ports are very hard to clip. Most of my home crimped cables do not clip in the ports but my off the shelf cables do clip if I push them very hard. That is my only complaint so far. VLANs are working great and thats all that matters !
Also the fact that we cant specify the VLAN for management is a bit annoying as I'm not using VLAN 1 on my network and I didn't want to add routing in my OPNsense for VLAN 1, so I ended up doing a port isolation on LAN 8, and assigned access VLAN 1 only on LAN 8. Then I connected this port to an access port on my other switch that was set to Access VLAN 10. I'm wasting a port, but at least all is well now as that switch's VLAN 1 is now flagged as VLAN 10 just like the rest of my network.
Last edited:
Hi!
I just got a couple of those switches with the idea of them floating in my workshop if I need a managed switch here and there, and have easy access to a couple of networks on my desk for random experiments.
When toying with the VLAN settings, I disabled the VLAN 1 on all ports - assuming the info here is correct and the switch listens on all VLANs. This seems to be false - I can no longer reach the switch and I'll be soldering serial console over the weekend it seems
.
On a second switch, I tested this and I can confirm i listens for management only on VLAN 1. At least 1.9.0 and 1.9.1 do.
On the other hand, I might buy something different soon, since I have little confidence in these switches...
I just got a couple of those switches with the idea of them floating in my workshop if I need a managed switch here and there, and have easy access to a couple of networks on my desk for random experiments.
When toying with the VLAN settings, I disabled the VLAN 1 on all ports - assuming the info here is correct and the switch listens on all VLANs. This seems to be false - I can no longer reach the switch and I'll be soldering serial console over the weekend it seems
.On a second switch, I tested this and I can confirm i listens for management only on VLAN 1. At least 1.9.0 and 1.9.1 do.
On the other hand, I might buy something different soon, since I have little confidence in these switches...
a trunk port that carries vlan 10 is also connected to the switch and cannot reach the specified IP through the trunk port. It seems like it is only on VLAN 1
Mine is hardware rev 1.1 and firmware 1.9.1 if that matters
Hmmm, I am confused why mine is working now. I will modify my post to not make others try this as well.Hi!
I just got a couple of those switches with the idea of them floating in my workshop if I need a managed switch here and there, and have easy access to a couple of networks on my desk for random experiments.
When toying with the VLAN settings, I disabled the VLAN 1 on all ports - assuming the info here is correct and the switch listens on all VLANs. This seems to be false - I can no longer reach the switch and I'll be soldering serial console over the weekend it seems
On a second switch, I tested this and I can confirm i listens for management only on VLAN 1. At least 1.9.0 and 1.9.1 do.
On the other hand, I might buy something different soon, since I have little confidence in these switches...
Do you not have a reset button on the switch?
For reference I have a Keeplink KP-9000-9XHPML-X-AC
| Firmware Version | V100.9.4 |
|---|---|
| Firmware Date | Aug 07 2024 |
| Hardware Version | V1.1 |
Last edited:
I think I see where I went wrong;
I did not bother to disable vlan1 on the ports of this switch. I only added al my vlans I needed to the ports.
On the uplink (core) switch port all vlans are also present and vlan1 is not assigned to that port, so I assumed it must be vlan10 (my mgt vlan) that carried the request to the switch because that is the only route between my workstation (vlan150) and the switch (via my pfsense router doing its routing thingy) .... until I remembered that I set a PVID 10 to that port on the core switch, so all untagged traffic (vlan1) is tagged as vlan10 there when entering the core switch, which makes it routable through the rest of my network.
Sorry for my previous misinformation.
Yeah, the reset button worked fine. It was a bit too late and i glanced right over it, figured out it's not there, and went to sleep. UART works fine, 3.3V, well labelled, there is a repo that documents some of the commands on github. They seem to work, no command to change the management vlan though.
Hi i have a strange issue with a SWTG115AS-V2 Managed .... after a power outage only the sys blinks fast, was able to flash unmanaged boots fine but on flashing the managed version i get no boot and no serial output... anybody had the same error, tried to grab the dump from a the same model but ended up not beeing able to boot the new one ... any hints or tips or am i stuck now with an unmanaged version?
Thanks
Thanks
I’ve dump the ROM of my KP-9000-9XHPML-X-AC switch. It is version 100.9.5. It’s a dump after a reset. The defaut IP is 192.168.1.168 and the password is admin / admin. The MAC Address of the switch is at position 1FC000, you should change it if you plan on using this dump. If you want to download it : KP-9000-9XHPML-X-AC_V100.9.5.bin .
Thank you for that at least the uart is working on that...
but it seams to be for the wrong switch. how can i dump from a working switch? a read from the chip inside the circuit didn´t work even when the crc looks good.
sadly esc doesn´t bring me into download mode on the switch so i could load the right firmware again
==========Loader start V0.2===========
Press any key to start the normal procedure.
To run SPI flash viewer, press [v]
To enforce the download of the runtime kernel, press [ESC] .
cmd 27
sal_sys_runtime_crc_set
loader start
init_8373N_8224N_QC, Error CHIP_MODE chip_mode =0, Please Confirm DUT & Tool_Channel!Ver8372N=2
Ver8373N=2
Hi guys. Some time ago I asked for help unbreak my SKS3200-8E1X-P. After firmware upgrade the device has been quiet and only one led blinking all time. The full dump could helped to make up for a life the router.
drive.google.com
This is full dump from another same router and if you want change MAC or other default settings you may it do on http://192.168.10.12/ftdft.cgi
SKS3200-8E1X-P-V100.9.6-dump.bin
drive.google.com
Hi all: There has been a question about the difference between 1.9 and 1.9.1, and a clue was provided in previous post 289..
I think (one difference): In version 1.9 If the switch is set for DHCP and it fails to get an IP, it sets itself as static at 192.168.2.1
In version 1.9.1 it appears to use the previously saved static IP (which might also be 2.1 if that was not changed and saved).
This is a problem for those using 192.168.2.x LANs where 2.1 is often the router since it will collide and cause all sorts of weird problems.
For 1.9 you probably do not want to use DHCP at all if you cannot guarantee the DHCP server is always up prior to powering switch.
For 1.9.1 if you want to use DHCP, make sure you configure it first with an innocuous static IP address (saving it) prior to configuring DHCP.
Of course in both cases if the DHCP fails the web address will move to the above addresses (and appear to vanish from assumed DHCP one).
I determined this using Mokerlink5+1 with 1.9.1 and Sodola8+1 (non-POE) with 1.9.
Quick update for 1.9: If DHCP fails (initially or during lease renewal), it will occupy ..2.1 irrespective of the static setting as noted above. But additionally, if you have set a different static (as suggested for v1.9.1) the management interface fails! That is, it will respond to ...2.1 pings and port 80 is open, but the switch's management interface returns blank pages. [This behaviour has been noted in previous posts] (Recovery is to power down and repower with DHCP server up, so the switch can complete the dynamic DHCP assignment properly.) Because a DHCP failure could occur at any time (e.g. with incorrect power sequencing) I would not be using dynamic DHCP address assignments, just use static only and remember what was set and forget about 192.168.2.1.
I think (one difference): In version 1.9 If the switch is set for DHCP and it fails to get an IP, it sets itself as static at 192.168.2.1
In version 1.9.1 it appears to use the previously saved static IP (which might also be 2.1 if that was not changed and saved).
This is a problem for those using 192.168.2.x LANs where 2.1 is often the router since it will collide and cause all sorts of weird problems.
For 1.9 you probably do not want to use DHCP at all if you cannot guarantee the DHCP server is always up prior to powering switch.
For 1.9.1 if you want to use DHCP, make sure you configure it first with an innocuous static IP address (saving it) prior to configuring DHCP.
Of course in both cases if the DHCP fails the web address will move to the above addresses (and appear to vanish from assumed DHCP one).
I determined this using Mokerlink5+1 with 1.9.1 and Sodola8+1 (non-POE) with 1.9.
Quick update for 1.9: If DHCP fails (initially or during lease renewal), it will occupy ..2.1 irrespective of the static setting as noted above. But additionally, if you have set a different static (as suggested for v1.9.1) the management interface fails! That is, it will respond to ...2.1 pings and port 80 is open, but the switch's management interface returns blank pages. [This behaviour has been noted in previous posts] (Recovery is to power down and repower with DHCP server up, so the switch can complete the dynamic DHCP assignment properly.) Because a DHCP failure could occur at any time (e.g. with incorrect power sequencing) I would not be using dynamic DHCP address assignments, just use static only and remember what was set and forget about 192.168.2.1.
Last edited:
hi if i flash your pathed version i don´t get any output from UART, SWTG115AS-V2.0 bougt as web managed, if i flash the firmware for the 8 port i at least get the bootloader but then errors out because of hardware missmatch ... flash installed 25Q16, can not use firmwar from git as it is 4MB oposed to 2MB available on that chip
