> For about a year, I've been using a dynamic IP DSL link to the internet.
 [...]

More fun with this:

I'm having trouble getting my gateway to act as a gateway *while* also
having my static IP numbers farmed out over my little home network.

The situation is something like this:

 Internet <==> [rtk0/gate  Gatewa  tlp0/prometheus] <==> [other machines]

rtk0/gate is the interface/name (IP address 66.136.7.249) used to talk to
the ISP via DSL.

tlp0/prometheus is the interface/name (IP address 66.136.7.250) used to
talk to my LAN.


Now, if my DSL link is live, then I cannot communicate to my LAN (not so
long as my LAN is using the new IP's).  Conversely, if I have my gateway
talking to my LAN, then it cannot talk to my ISP.

It appears that this is just a problem of getting packets sent to the
right spot.  It's not clear to me how I'm supposed to fix this.  Can I set
a suitable netmask?  (The ISP suggests 255.255.255.248...but unless I
typoed something, this isn't fixing it.  That *is* supposed to be for my
LAN, yes?  Or is it for the rtk0/gate interface?  Or both ethernet
interfaces?)

Then again, maybe a suitable route to force packets for 66.136.7.254 (the
gateway provided by the ISP) out through the rtk0/gate interface?  Having
read the man page for route, it's not clear how (or even if) I can do
this.

For concreteness for responses:

One machine in my LAN:
      ethernet card 1: tlp0
       network name 1: hermes      (66.136.7.251)

My DSL router/gateway:
       ethernet card 1: rtk0
        network name 1: gate       (66.136.7.249)

       ethernet card 2: tlp0
        network name 2: prometheus (66.136.7.250)

Realize that my networking skills are not particularly sharp (perhaps
obvious by my being stuck with this situation).  Please bear that in mind.
(^&

Thanks in advance for any assistance.


  ``I probably don't know what I'm talking about.'' --rauch@math.rice.edu