Gentoo Archives: gentoo-user

From: Bill Longman <bill.longman@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Issue with Multiple Networks in Gentoo...
Date: Fri, 18 Jun 2010 21:03:37
Message-Id: 4C1BD8A1.2070707@gmail.com
In Reply to: [gentoo-user] Issue with Multiple Networks in Gentoo... by Christopher Kurtis Koeber
1 On 06/18/2010 11:29 AM, Christopher Kurtis Koeber wrote:
2 > I am sure this is simple but I can't figure this out. I added a network
3 > card to an existing Gentoo installation to have two in total. *ETH1* is
4 > my new network card which is a Gigabit connection and *ETH0* is my old
5 > network card with just an 100 Mbit connection.
6 >
7 > I would like for the new network card (*ETH1*) to connect to a
8 > 10.10.50.X (class C) network which accesses out local LAN and the old
9 > network card (*ETH0*) to connect to a 10.10.60.x (class C) network which
10 > is a wireless network that _does not communicate_ with the 10.10.50.X
11 > network. This network also has internet access, if that is important.
12 >
13 > I am not sure what to do. Right now both interfaces get DHCP but I
14 > cannot ping either card or get network access.
15 >
16 > Here is my current /etc/conf.d/net file:
17 > -------------------------------------------------------------------------------------
18 > config_eth1=( "dhcp" )
19 > dhcpcd_eth1="-N"
20 > routes_eth1=( "10.10.50.0/24 via 10.10.50.1"
21 > "10.10.1.0/24 via 10.10.50.1"
22 > "10.10.10.0/24 via 10.10.50.1"
23 > "10.10.20.0/24 via 10.10.50.1"
24 > "10.10.30.0/24 via 10.10.50.1"
25 > )
26 > config_eth0=( "10.10.60.3 netmask 255.255.255.0 brd 10.10.60.255" )
27 > routes_eth0=( "10.10.60.0/24 via 10.10.60.1" )
28 > -------------------------------------------------------------------------------------
29 >
30 > And here are my current routes:
31 > -------------------------------------------------------------------------------------
32 > Kernel IP routing table
33 > Destination Gateway Genmask Flags Metric Ref Use Iface
34 > 10.10.20.0 10.10.50.1 255.255.255.0 UG 0 0 0 eth1
35 > 10.10.50.0 10.10.50.1 255.255.255.0 UG 0 0 0 eth1
36 > 10.10.50.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
37 > 10.10.1.0 10.10.50.1 255.255.255.0 UG 0 0 0 eth1
38 > 10.10.30.0 10.10.50.1 255.255.255.0 UG 0 0 0 eth1
39 > 10.10.60.0 10.10.60.1 255.255.255.0 UG 0 0 0 eth0
40 > 10.10.60.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
41 > 10.10.10.0 10.10.50.1 255.255.255.0 UG 0 0 0 eth1
42 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
43 > 0.0.0.0 10.10.50.1 0.0.0.0 UG 0 0 0 eth1
44 >
45 > Anything else I need to do or change?
46
47 This won't help you ping the card, but why do *you*, rather than DHCP,
48 force a route for 10.10.50.0/24? And especially since your default route
49 points the same direction. Why not just set the default route to
50 10.10.50.1 and let it do its job?
51
52 But to answer your question, you should make sure the /etc/udev/rules.d
53 files haven't changed your NIC numbering. What do you mean that they
54 both get DHCP but you can't ping them. How do you know they're getting
55 DHCP then?
56
57 Can you even plumb the interface?
58
59 ifconfig eth0 up
60
61 Try ifconfig eth3 up.