We've set this particular inside my rc_firewall order, and it's functioning following a reboot. Devoid of the stop/start support, it does not function.
I examined this kind of by using a ping into a system on the regular interface, which usually worked well. Unplugging that and relocated this on the WAN interface halted the particular ping. Operating swconfig would not bring about called ping.
Hi guys, thanks for the information so far and sorry for my bump as well. Running 21676 on a wr1043ND.
The trick to assign the wan port to the switch works for me as well, however I then loose my wireless connection to the router providing the internet connection.
Thomson wifi router connected to the internet
|| wireless (shared network)
TL - WR1043ND
|| wired (private network)
So I guess I should re-enable something else as well?
After I run commands:
swconfig dev rtl8366rb vlan 1 set ports '0 1 2 3 4 5t'
I can connect to the ethernet (private network) using the WAN port. But when I run a DHCP release/renew under status -> wan it does not get an ip from the Thomson.
When I revert the port assignment by restarting the tp-link the connection to the wifi router re-establishes and I see correct ip config (obtained via DHCP) under status WAN. But of course I can't use the wan port for the private network...
Hopefully someone knows how to fix this? This config worked with an old firmware I was using before (I think even without running the commands but I'm not sure anymore).