On Tue, 23 Sep 2003 16:21:50 GMT, Beat Naef <(E-Mail Removed)> wrote:
> The network consists of 2 Lin boxes, 3 dual boot Lin/ W2k systems and a
> 802.11 router that connects to DSL.
>
> One Lin box, the file server, contains three interfaces: wlan0, eth0, eth1
> and is connected wirelessly to the 802.11 router. 2 Lin/Win systems connect
> to the interfaces eth0 and eth1 respectively. This box runs the dhcpd (on
> eth0 and eth1), named and smb server.
One problem is that your gateway probably only knows about the subnet
directly connected to it and knows nothing about how to route to your
other subnets. So for those other subnets to access your gateway
(actually so the gateway knows where to return packets) you either need to
masquerade the other subnets, or have them be subsets of your main subnet,
using proxy_arp. Example of my setup:
Gateway 192.168.1.1 192.168.1.0/255.255.255.0
|
|--printserver 192.168.1.200 192.168.1.0/255.255.255.0
|
eth0 192.168.1.2 192.168.1.0/255.255.255.0 proxy_arp enabled
default gw 192.168.1.1
eth1 192.168.1.241 192.168.1.240/255.255.255.248
|
WAP 192.168.1.246 192.168.1.240/255.255.255.248
wlan0 192.168.1.245 192.168.1.240/255.255.255.248
default gw 192.168.1.241
Note that since proxy_arp is enabled on eth0, it answers arp requests for
IPs on eth1. So the Gateway or printerserver can find my wireless laptop
as though they were local (with arp broadcasting) instead of needing a
gateway to find the smaller subnet (ie, the small subnet is within and
becomes part of the main subnet).
Proxy arp for eth0 is enabled by:
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
I have not tried 3-way proxy arp, but you could try:
wlan0 some_ip netmask 255.255.255.0
default gw gateway_ip
eth0 some_ip netmask 255.255.255.255 broadcast (same as IP)
host route to remote IP on eth0
eth1 some_ip netmask 255.255.255.255 broadcast (same as IP)
host route to remote IP on eth1
Then enable proxy_arp for wlan0, eth0 and eth1
On the boxes connected to eth0 and eth1 use normal 255.255.255.0 netmask
and gateway to respective Linux eth0 or eth1 IP.
The IPs for Linux interfaces and the 2 boxes connected to it should be
outside of dhcp range assigned by main gateway (wireless router).
--
David Efflandt - All spam ignored
http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/