public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How to configure eth1:1 ?
Date: Mon, 17 Oct 2011 22:19:32 +0000 (UTC)	[thread overview]
Message-ID: <j7i9lk$190$1@dough.gmane.org> (raw)
In-Reply-To: 4E9CA283.1060000@binarywings.net

On 2011-10-17, Florian Philipp <lists@binarywings.net> wrote:

> Ugh, sorry. Just ignore that. I didn't see the second line in
> config_eth1. The odd quoting confused me.

Sorry about that.  I was trying various quoting schemes I'd found in
examples.

My current configuration works:

  modules_eth0=( !plug )
  config_eth0=( "192.168.8.4/16" )
  routes_eth0=( "default via 192.168.0.254" )

  modules_eth1=( !plug )
  config_eth1=( "10.0.0.1/8" "192.168.250.1/24" )

$ /sbin/ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:1b:21:b1:d1:e9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.4/16 brd 192.168.255.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:16:17:84:a7:b3 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.1/8 brd 10.255.255.255 scope global eth1
    inet 192.168.250.1/24 brd 192.168.250.255 scope global eth1
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:18:e7:08:20:33 brd ff:ff:ff:ff:ff:ff

  
And the lack of eth1:1 is presumably explained if the system is using
the iproute2 module instead of the ifconfig module.  My current theory
is that iproute2 is getting used because I have openvpn installed with
the iproute2 use flag. [I'm not actually using openvpn, but it's still
istalled from a couple years ago when I was using it.]

Yes, I know that the /24 subnet defined by the second eth1 address
overlaps the /16 subnet defined by the eth0 address. 

For historical reasons, 192.168.250.nnn is on eth1, and
192.168.everything-but-250.nnn is on eth0.

And eth2 is used only by a VM client OS.

Yea, it's a messy, but it's still easier than using 4 different
machines....

-- 
Grant Edwards               grant.b.edwards        Yow! I appoint you
                                  at               ambassador to Fantasy
                              gmail.com            Island!!!




  reply	other threads:[~2011-10-17 22:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 21:25 [gentoo-user] How to configure eth1:1 ? Grant Edwards
2011-10-17 21:37 ` [gentoo-user] " Grant Edwards
2011-10-17 22:04   ` Grant Edwards
2011-10-17 21:42 ` [gentoo-user] " Florian Philipp
2011-10-17 21:47   ` Florian Philipp
2011-10-17 22:19     ` Grant Edwards [this message]
2011-10-18 15:09       ` [gentoo-user] " YoYo Siska
2011-10-18 16:18         ` Grant Edwards
2011-10-19 15:19           ` james
2011-10-19 15:45           ` Grant Edwards
2011-10-18 16:23         ` Grant Edwards
2011-10-20  2:56       ` Walter Dnes
2011-10-20 14:12         ` Grant Edwards

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='j7i9lk$190$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox