Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Rob on November 24, 2000, 02:37:38 AM

Title: second network interface card for internal network
Post by: Rob on November 24, 2000, 02:37:38 AM

Id like to know how to add a second nic for the internal network, setting up the interface  is no problem interface is up and running.
Added static routes to the routing table (the same as for the first internal nic), but this doesnt work.
Im probably missing something, if anyone can point it out to me Id be gratefull.

Title: RE: second network interface card for internal net
Post by: Stefan on November 25, 2000, 11:22:58 PM

Rob wrote:
> Id like to know how to add a second nic for the internal
> network, setting up the interface  is no problem interface is
> up and running. Added static routes to the routing table (the
> same as for the first internal nic), but this doesnt work. Im
> probably missing something, if anyone can point it out to me
> Id be gratefull.
>

I've posted near the same problem on 21.11.2000 13:55

The interface is up and running. I have added the static routes in routing table, but unfortunately I assigned wrog IP address - on same network as the primary interface.

Since I realized that I haven't tryed it again, but generally e-smith was made to work on second interface as external one. I hoped that guys from e-smith will give as an idea but until now there is no post on the subject.

Title: RE: second network interface card for internal net
Post by: Gordon Rowell on November 25, 2000, 11:32:18 PM

Stefan wrote:

> [...]
> Since I realized that I haven't tryed it again, but generally
> e-smith was made to work on second interface as external one. I
> hoped that guys from e-smith will give as an idea but until now
> there is no post on the subject.

We don't guarantee to answer every question on the boards and we have no
plans to support multiple internal interfaces at this stage.

However, I did make a change recently which means that the e-smith
manager will only touch "alias eth[01]" in conf.modules - previously it would
remove all eth aliases before adding the ones for eth[01].

I suggest you join the devinfo mailing list to talk about extensive changes such as
supporting a third interface. You should also read all of the information on
Customisation found on www.e-smith.org as you will need to modify quite a few
templates to make your changes stick.

Gordon