On 08.01.2013 21:49, lux-integ wrote: > On Tuesday 08 January 2013 18:49:43 Bruce Dubbs wrote: >> Just to be picky, it's not a router, it's a bridge. It works at layer 2 >> and there is no 'routing' decision to be made. > > Yippie (I hope) > So does this mean you can hook up a machine that routes one or more > subnets to this device ?
yes > Any recipes where this kind of setuphas been implemented ( (ii.e. using a > modern low-cost-adsl2-firewall-router-modem-network-appliance-thingie) on a > blfs-running maching routing multiple subnets would be gratefully received. i can't provide you with blfs-compatible network-scripts as i use my own set of script for those setups. but i try to show you what to do. assume the following networks: external 192.168.0.0/whatever network1 192.168.1.0/24 network2 192.168.2.0/24 network3 10.0.0.0/8 the 'big iron', connected to the router has all static 192.168.0.1 (external, to the adsl-router) 192.168.1.1 192.168.2.1 10.0.0.1 for all internal networks the big iron is dhcp server and propagates the default route for the client to itself, thus 192.168.1.1, 196.168.2.1 and 10.0.0.1. the big iron has its default gateway set to 192.168.0.9 (to what i set the router). all other nets don't have a default gateway. the big iron has firewall, nat, dns and whatever more you want. but stop the firewall for your first experiments - most routing problems are due to wrong firewall rules! you don't have to disable the services on the adsl-router as you just can ignore them. maybe you gain a little speed when nat and firewall are disabled, but i usually don't spend the time to read the manual... the adsl-router should be set to a fix ip. you don't have to disable the dhcp server on the router. you won't get conflicting addresses as long as no other device will ever be connected to the router. tobias -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
