Bridge mode to hAPax seem like the right call – essentially your turning it into just a cable modem. So while you'd lose Wi-Fi from the Technicolor, I'd imagine the AX from hAPax3 is going to be better than the Technicolor. And routing/NAT on hAPax3 certainly more flexible in this mode.
In terms of DoS protections I doubt the Mikrotik is any worse than whatever technicolor one is doing. e.g. it's already using your bandwidth once it get to the cable modem & ISP DoS protections be on the DOCSIS headend side, not the router.
If "cable TV" package from your cable company, might want to search the forum since there is some tricks to allow "normal TV" (e.g. multicast / RTSP ) when in bridge mode. That be the other complexity with bridge mode. If you don't have a TV package, it wouldn't come up.
Now if you really want to use Technicolor Wi-Fi and LAN in a routed mode. I believe SOME technicolor routers support RIP dynamic routing protocol. And RouterOS supports RIP protocol, so you could enable that on both RouterOS & Technicolor to allow 192.168.0.0/24 and 192.168.88.0/24 routers to be exchange. IF it supported, that is.... that allow "workstations on LAN-B can't connect to workstations on LAN-A" while in routed mode. You'd have to check the UI to see if that was possible.
But routed mode only help if you really wanted to use the Technicolor's built-in Wi-Fi along with hAPax3's (perhaps for coverage if the hAPax3 were connected via long ethernet).
In terms of DoS protections I doubt the Mikrotik is any worse than whatever technicolor one is doing. e.g. it's already using your bandwidth once it get to the cable modem & ISP DoS protections be on the DOCSIS headend side, not the router.
If "cable TV" package from your cable company, might want to search the forum since there is some tricks to allow "normal TV" (e.g. multicast / RTSP ) when in bridge mode. That be the other complexity with bridge mode. If you don't have a TV package, it wouldn't come up.
-Routing scenario: configure the Mikrotik with routing, firewall and NAT.Two LAN: LAN-A:192.168.0.0/24 and LAN-B: 192.168.88.0/24. Seems to Work fine in despite of double NAT. I tried removing Mikrotik NAT but workstations on LAN-B can't connect to workstations on LAN-A; i guessed that the cause is that router CGA4233vdf and workstation in LAN-A doesn't known the gateway to LAN-B (and you can't setup an static route to LAN-B in the Technicolor, even advanced user interface doesn't have this option). Works out-of-the-box with dhcp-client setup on ethernet 1 port (WAN).
WAN <---> Technicolor CGA4233vdf <--- LAN-A 192.168.0.0/24 ---> Mikrotik router <--- LAN-B 192.168.88.0/24 >
Now if you really want to use Technicolor Wi-Fi and LAN in a routed mode. I believe SOME technicolor routers support RIP dynamic routing protocol. And RouterOS supports RIP protocol, so you could enable that on both RouterOS & Technicolor to allow 192.168.0.0/24 and 192.168.88.0/24 routers to be exchange. IF it supported, that is.... that allow "workstations on LAN-B can't connect to workstations on LAN-A" while in routed mode. You'd have to check the UI to see if that was possible.
But routed mode only help if you really wanted to use the Technicolor's built-in Wi-Fi along with hAPax3's (perhaps for coverage if the hAPax3 were connected via long ethernet).
Statistics: Posted by Amm0 — Sat Apr 06, 2024 3:56 am