Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #3202

Re: Gateway config eth0<->sl0

Show all headers | View raw

On Tue, 06 Jan 2015, in the Usenet newsgroup comp.os.linux.networking, in
article <m8fajp$6cc$1@news2.open-news-network.org>, mds wrote:

>Moe Trin wrote:

>> Any particular reason you need to be using such an old release?

>I have a brother HL5350DN printer connected to that machine. The
>printer dates from the time of lenny and brother haven't kept the
>support up to date with subsequent releases. It'd be possible to make
>the printer work with wheezy but I just can't be bothered looking in
>to it at the moment.

Good reason - I'd suggest waiting a couple of weeks anyway until jessie
comes out.

>The machine running lenny has a serial port so it's other job is to
>connect to a near antique toshiba 100cs laptop. To transfer a file from
>my modern pc to the toshiba I have to scp it to the lenny box, ssh into
>the lenny box and scp it to the toshiba.

OK - 'lenny' needs to be told to forward packets - that should only take
the "echo 1 >  /proc/sys/net/ipv4/ip_forward" line, perhaps in the
script that brings up the serial link.   The routing table in your
original post (host, Ethernet and default) is fine for 'lenny'.   The
'toshiba' needs to have the routing table look something like

192.168.2.1  0.0.0.0      255.255.255.255 UH    0      0     0 sl0
192.168.1.0  192.168.2.1  255.255.255.0   UG    0      0     0 sl0

which tells it 'lenny' is reachable on the serial link, and that there
is a network beyond it reachable using 'lenny' as a gateway.   You
could just tell 'toshiba' that 'lenny' is the default route, which
would have the same result.   The 'modern pc' box has Ethernet I
assume, so it (and any other hosts on the 192.168.1.0 Ethernet) needs
a routing table that has

192.168.1.0  0.0.0.0       255.255.255.0   U     0      0     0 eth0
192.168.2.2  192.168.1.22  255.255.255.255 UH    0      0     0 eth0

which tells it that 'toshiba' can be reached by sending the packets to
'lenny' (the eth0 interface).  The syntax would likely be

  /sbin/route add -host 192.168.2.2 gw 192.168.1.22

>Anyway thanks for your suggestions

You're welcome!

>I'm sure I can make some headway with this now by following up on them.

I imagine trying to find an Ethernet adapter for the Toshiba would be a
major problem.   In the late 1990s, I recovered an Acer laptop that had
been tossed out with an intermittent display, but it had a serial port
and Ethernet dongle.  It became my dial-out firewall box - setting in
the closet in a cardboard box along with a 28.8k external modem.   "The
price was right".

        Old guy

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Gateway config eth0<->sl0 mds <mds@none.foo> - 2015-01-05 09:22 +1300
  Re: Gateway config eth0<->sl0 Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-01-05 06:29 +0000
  Re: Gateway config eth0<->sl0 Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-01-05 17:49 +0000
    Re: Gateway config eth0<->sl0 mds <mds@none.foo> - 2015-01-06 13:35 +1300
      Re: Gateway config eth0<->sl0 Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-01-07 01:17 +0000
        Re: Gateway config eth0<->sl0 mds <mds@none.foo> - 2015-01-11 12:23 +1300
          Re: Gateway config eth0<->sl0 Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2015-01-11 20:31 +0000

csiph-web