[1045] in linux-net channel archive
Re: Ethernet + Slip ? possible ?
daemon@ATHENA.MIT.EDU (Aidan Dixon)
Mon Sep 4 23:34:36 1995
Date: Mon, 4 Sep 1995 14:44:35 +0100 (BST)
From: Aidan Dixon <aidan@prismtech.co.uk>
To: Wim Valcke <Wim.Valcke@rug.ac.be>
cc: linux-net@vger.rutgers.edu
In-Reply-To: <Pine.SOL.3.91.950903122137.10672A-100000@eduserv.rug.ac.be>
On Sun, 3 Sep 1995, Wim Valcke wrote:
> hello
> I have a Linux server (Kernel 1.2.1) I think shipped with Slackware 2.2.0.
> Now this server is running as a nfs server for a few pc's and this works
> great !. What i now want to do is attaching a second linux server to
> the first server with a serial cable (null-modem). So the first
> server will have 2 !! IP adresses . I tried without sucess.
> Is it possible to have 2 ip adresses on a Linux server ? Can i
> put 2 ethernet cards in one pc, so that i can route between 2 subnets ?
> Is it possible to have an ethernet connection and a slip connection
> at the same time ? ....
>
> thanks in advance for an answer.
>
> wvalcke@eduserv.rug.ac.be
>
>
Hi, Wim!
This is indeed possible. I'm not entirely sure about the serial stuff
but some-one else should be able to advise you on that; I suspect you'll
need to use slattach.
As for the IP addresses, it is possible to have more than one network
card in a pc and have serial IP working too. The network cards will have
to have (AFAIK) seperate interrupt settings as well as seperate IO and
MEM addresses. Personally I'd recommend SMC ULTRA ELITE cards - I've got
two running in a machine acting as a router between local ethernet and
the Internet. (Kernel 1.2.11, libc 4.7.2, 486SX-25, 8MB, 850MB)
My application of IP forwarding (which must be configured in your kernel)
is slightly different from yours but I think the configuration of IP is
not so dissimilar. For each net device, the machine has an associated
interface: eth0..N-1 for N detected ethernet cards and sl0..N for N
serial line based IP interfaces. You can configure each to have either
the same or different internet addresses. In either case each the
machine would normally have some kind of "unique" route associated with
each interface.
Here's how I've done mine.
^
| sl0 (158.152.18.107)
+--------+--------+ +--------------------+
| INet Gateway |eth0 | NAT LANB/290 Router|
| 193.118.255.253 +-------------+ 193.118.255.254 +----> to internet
| prism | | router |
+--------+--------+ +--------------------+
|eth1
|
|to our network
eth0 : route add -host 193.118.255.254 eth0
route add default gw 193.118.255.254 eth0
eth1 : route add -net 193.118.255.0 eth1
The "prism" machine also used to run a dialup IP connection to Demon
Internet Systems but doesn't now. I don't know so much about the
subnetting arrangement as I've not actually used that myself but I guess
you'll have to install routes through your "middle" linux machine on either
side of the middle machine
As I see it, ifconfig for the interfaces is the simpler part: the routing
is the more important thing to get right.
Hope this is some help.
Cheers,
Aidan
-----------------------------------------------------------------------------
Prism Technologies Ltd. | Tel. +44 191 491 3983 | To you, Baldrick, the
Kingfisher House | Fax. +44 191 491 3973 | renaissance was just
Kingsway, T.V.T.E, | | something that happened to
Gateshead. | Aidan.dixon | other people, wasn't it?
NE11 0JQ, UNITED KINGDOM| @prismtech.co.uk | EB, Head, Blackadder II
-----------------------------------------------------------------------------
