South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
add chain=srcnat action=masquerade src-address=xxxxx/24 out-interface=pppoe-out1
add chain=srcnat action=masquerade src-address=xxxxxxx/24 out-interface=ether-gateway
Or an even simpler option is just to put everything onto the same physical ethernet segment. ROS is perfectly capable of running IP routing (for the internal LAN) and a pppoe-client on the same interface (e.g. ether1). And if one uses the same IP range as the IDU, you retain access to its mgmt interface (e.g. to checks signal strength etc.).Setup ether2 with the ip 192.168.88.1/24.
The DHCP server resides on the logical router interface, so one must make sure all the switch ports are mapped to that interface. For example if the interface used is 'ether1' ...How do I set the dhcp to run across all the port on the router as oppise to just one.. the onther port still using the 192.168.88.10-254
Yeah true, but the advantage of associating the ports at a switch level is GbE type inter-port switching performance. Pushing any traffic through the router process significantly reduces this performance.Just remember that if you use a master-slave setup like Roman suggested, that you cannot do interface specific routing/firewalling any more.