actually, better depiction and idea improvements:
wireless area Internet
| |
LRP LRP
| |
-------LAN-------------
Both LRP's masq, both LRP's treat the top interface as default network.
Wireless LRP forwards everything into the LAN, masqing it as a single
IP. The hard part now is Internet access from the wireless LAN, because
you can't give the LRP two default routes pointing in two different
directions :-) Nor can you use the massively annoying "static routes
supernetting the whole Internet" trick because you're likely to get
registered addresses on the wireless net from time to time. Routing into
the LAN is easy, but routing from the wireless area to the Internet is
going to be challenging.
I think you're better off changing people's IP addresses.
--
Jack Coates
Monkeynoodle: It's what's for dinner!
On Sat, 21 Apr 2001, Jack Coates wrote:
> I don't think it's going to work, then. "On the fly" reconfiguration
> would mean downing the interface everytime a new machine joined the
> wireless LAN, which would get really annoying to the users. But if you
> treat the LAN like the Internet (0.0.0.0/0) then you can't route to it.
>
> Actually, that could work, I think, with proxy arp.
>
> wireless int -> 192.168.254.254, bridging enabled
> def route forwards all traffic to eth1
> masquerade as 192.168.1.1
> eth1 -> 192.168.1.254
>
> another LRP is the Internet gateway. Double-NATing is goofy as hell and
> will probably break something.
>
>
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
