I wonder if anyone could help me with suggestions for software and configeration for the following hardware network set up :-
wifi link to isp via router(A).
Local ip allocation by router(A) (say 192.168.2.3 ... but could be different depending upon state of router and other connections to it.)
Wifi network card(A) in relatively low spec pc (B)... ideally 256-512 M memory ... x86 ... cd live or flash drive boot ... hopefully also sans monitor and keyboard and supporting web based interface for set up from local network administered by C (below)
Ether Net card in same pc(B) connects to a separate wifi router(C) .. which sees this link as its route to the intenet/isp and accepts ip allocation from B ..
Router(C) allocates local ip numbers on another domain (say 10.1.1.1-256) Router C supports both wifi and ehternet connections.
I suppose B is a sort of router .. except that it is working in reverse to the normal expectation?
Suggestons for live cd or flash distributions that might suit B appreciated .. as would commnets on how to set up router C
Hi Stephen It generally helps to draw a diagram of what you're trying to achieve, and it may also help in this case to give a higher-level description of why you're trying to do it this way. There may be a simpler way of doing things. I can't tell if you're talking about two different ISP connections (via A and C), or if there is just one. Is this what you're talking about? ISP | | Router A ---------- wifi --------- Router B ----- wired ------ Router C ------- wifi ------- clients | ------------ wired ------ clients If it is, do you really need all three routers? Your question about B being a "sort of router" - it's definitely a router, if it routes between two networks. Who allocates IPs to who is a different question, as that's done by something like DHCP, although with routers I'd strongly recommend using static IP addresses, even if it's only for the routers. In terms of distros, Id tend to use debian myself, but you want web management, so you should consider something like pfsense or m0n0wall At a higher level, Router A will have to do NAT at the connection to the ISP. It's probably tempting to do NAT at each router along the way, although it's not really needed, depending on what kind of control you have over the route tables on all the routers, and whether or not you can do bridging rather than routing.