All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: FW: [LARTC] Static ip addresses/aliases previously (my mistake)
Date: Tue, 06 Jul 2004 10:33:40 +0000	[thread overview]
Message-ID: <40EA8004.9000502@wildgooses.com> (raw)
In-Reply-To: <200407051616.i65GGcx94225@smtp.shellnet.co.uk>


>eth1 & eth2 are both connected to the EN5861 router.  I've done that
>because I couldn't work out any other way to use the static IP address that
>out ISP have given us.  
>

Aha, this is a config question.  You can just add as many ip addresses 
to each physical card as you like.  I forget the exact syntax, but check 
man pages for "ifconfig" and look for "aliases".

Chances are your distro already has support for this.  For example in 
gentoo you edit /etc/conf.d/net and edit the aliases line.  Different 
configs for all "normal" distros, but same idea
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-07-06 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 16:14 [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work conserving ? Chris Bolton
2004-07-05 19:21 ` [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work conservi James Sneeringer
2004-07-06  7:22 ` FW: " Chris Bolton
2004-07-06 10:33 ` Ed Wildgoose [this message]
2004-07-06 12:54 ` FW: FW: [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work cons Chris Bolton
2004-07-06 15:07 ` FW: FW: [LARTC] Static ip addresses/aliases previously (my mistake) Ed Wildgoose
2004-07-06 15:52 ` FW: [LARTC] Static ip addresses/aliases previously (my mistake) htb: class 10007 isn't work cons James Sneeringer
2004-07-06 16:15 ` FW: " Chris Bolton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40EA8004.9000502@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.