🚀 go-pugleaf

On 19 Aug 1996 12:31:41 GMT, Robert Paul Pham <zzppham@dingo.cc.uq.oz.au> wrote:
>terry@baldric.no.itg.telecom.com.au (Terry Dawson) writes:
>
>I would really appreciate some more elaborate wisdom :-).
>Being a tcp/ip newbie I tried everything, but as soon as a 
>default route is setup to my ISP, all packets from other machines just 
>seems to head straight down sl0 and into oblivion. Do you mean I can 
>setup more than one default route on the Linux box?
>

OK, I'm not sure If I'm right or am merely exposing my ignorance for all
to see (and make mental notes never to hire me...) but here goes.

Each machine you have has to have some clue where to send its packets.

Your SLIP machine has a "default route" that points to it's slip
interface and thence to the ISP.  "All packets go here and seek your
destiny".

Note - all packets.  Before you made  your SLIP link, all packets
headed out the ethernet port and around the local network.

So... for  your SLIP box to talk to the things on the ethernet again,
you have to have a "static route".  First stop, "man route" :) (second
stop man netstat BTW)

Let's say you have a local box 203.44.1.1 which is your SLIP box and
another box on your private net which is 203.44.1.100.

On the SLIP box, you need a static route that says "all packets for
203.44.1.* machines, kindly head out the ethernet port".  It would look
like:

route -v add -net 203.44.1.0 netmask 255.255.255.0 dev eth0


OK, what about elsewhere?  YOur other machine?

I freely admit to being hazy on this, as I run a firewall, and so don't
have to route to the internet as such.  But I imagine that you need
to set up your other machine's default route to point to your SLIP box.

Has this helped?

Zebee