QUOTE(sub7 @ Mar 2 2013, 12:29 PM)
Thanks Cloud computer,
There is an overhead with NATing (which I dislike) suggested. The NATing at layer 3 consume memory and processing power (especially when number of IP sessions exceed few hundreds thousand). Both URLs is suggesting NATing while what I am looking for is layer 2 bridging capability. No filtering, no NATing, no ACL is required, no routing... just bridge the WAN interface through.
Eg:
Network/subnet id: 212.212.212.0/29
ISP Gateway: 212.212.212.1/29
Router WAN: 212.212.212.2/29
Router LAN (or host ip): 212.212.212.3, .4, .5 and .6 #WAN and LAN is bridged
Broadcast: 212.212.212.7
Any clue? I don't need IP feature set (firewall/PBR/LB) but just dedicated WAN bridging feature. Funny though, Dlink615 can do that...
Cheers and thanks for your input.
Your setup is even simpler, the references are just some ideas for you on what MikroTik can do, you can just create default gateway in routing table to route mangled traffic from preferred source IPThere is an overhead with NATing (which I dislike) suggested. The NATing at layer 3 consume memory and processing power (especially when number of IP sessions exceed few hundreds thousand). Both URLs is suggesting NATing while what I am looking for is layer 2 bridging capability. No filtering, no NATing, no ACL is required, no routing... just bridge the WAN interface through.
Eg:
Network/subnet id: 212.212.212.0/29
ISP Gateway: 212.212.212.1/29
Router WAN: 212.212.212.2/29
Router LAN (or host ip): 212.212.212.3, .4, .5 and .6 #WAN and LAN is bridged
Broadcast: 212.212.212.7
Any clue? I don't need IP feature set (firewall/PBR/LB) but just dedicated WAN bridging feature. Funny though, Dlink615 can do that...
Cheers and thanks for your input.
Mar 2 2013, 01:37 PM

Quote
0.0288sec
0.40
6 queries
GZIP Disabled