🚀 go-pugleaf

In <greggh.0bc4@laserage.DIALix.oz.au>, greggh@laserage.DIALix.oz.au (Gregory Helleren) wrote:
> I've seen the example in the networking faq, but I can't see how this would
> work if machine (A) has a realm with a dynamic IP. I don't really want to go
> through the ethernet configuration every time I connect.

To deal with dynamic addressing for your route to the outside world,
you need your own (probably class C) subnet. Your local network
(whether slip, ethernet, token ring) uses IP address from that
network. The machine not connected to the outside world (B) has a
default route pointing to the local network address of the other
machine (A). A does it's dynamic SLIP thing just like always, and has
a route for the local net as well. Packets on B get sent to A (by
default) which sends them down the SLIP line (after you set
GATEWAY=YES in amitcp:db/amitcp.conf) because they aren't destined the
local net.

The trick with all this is that your provider has to be willing to
route packets for your local network back to your gateway. This is
*always* true. If they won't route packets for you, nothing else
matters. Check with them about all this. Don't be surprised if they
ask for a (possibly significantly) higher monthly fee.

If all you want is for web browsing with HTTP to work, I've started
working on it :-).

	<mike