SEO

Amd64

When I installed gentoo on an empty system, only eth0 was there. It's a
static address in the local lan 192.168.42.0

Later I added another ethernet adaptor intended to be exposed to the
outside world. This I setup as dhcp. Eventually I'll install bind and
iptables but for now the routing is goofy. The whole system is crawling
when it boots. This command took 30 seconds to execute:

dave@penrose ~ $ netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.42.0 * 255.255.255.0 U 0 0 0 eth0
70.66.12.0 * 255.255.252.0 U 0 0 0 eth1
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.42.1 0.0.0.0 UG 0 0 0 eth0
default 70.66.12.1 0.0.0.0 UG 0 0 0 eth1

Can anyone tell me how to find what I'm missing?

dave@penrose ~ $ cat /etc/conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
#iface_eth0="dhcp"
#dhcpcd_eth0=""
config_eth0=( "192.168.42.7 netmask 255.255.255.0" )
routes_eth0=( "default gw 192.168.42.1" )
config_eth1=( "dhcp" )

when I do

dave@penrose ~ $ sudo /sbin/ifconfig eth1 down

the machine snaps back to its normally speedy self.

I have no idea how to configure beyond this. There is no net-config that
I can find.

tnx
Dave

Zam <NOSPAM@hotmail.com> wrote:
> Amd64
>
> When I installed gentoo on an empty system, only eth0 was there. It's
> a static address in the local lan 192.168.42.0
>
> Later I added another ethernet adaptor intended to be exposed to the
> outside world. This I setup as dhcp. Eventually I'll install bind and
> iptables but for now the routing is goofy. The whole system is
> crawling when it boots. This command took 30 seconds to execute:
>
> dave@penrose ~ $ netstat -r
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 192.168.42.0 * 255.255.255.0 U 0 0 0 eth0
> 70.66.12.0 * 255.255.252.0 U 0 0 0 eth1
> loopback * 255.0.0.0 U 0 0 0 lo
> default 192.168.42.1 0.0.0.0 UG 0 0 0 eth0
> default 70.66.12.1 0.0.0.0 UG 0 0 0 eth1
>
> Can anyone tell me how to find what I'm missing?

You almost certainly should have only one default route.

> dave@penrose ~ $ cat /etc/conf.d/net
> # This blank configuration will automatically use DHCP for any net.*
> # scripts in /etc/init.d. To create a more complete configuration,
> # please review /etc/conf.d/net.example and save your configuration
> # in /etc/conf.d/net (this file :]!).
> #iface_eth0="dhcp"
> #dhcpcd_eth0=""
> config_eth0=( "192.168.42.7 netmask 255.255.255.0" )
> routes_eth0=( "default gw 192.168.42.1" )
> config_eth1=( "dhcp" )

If 192.168.42.1 doesn't route packets to the world, remove that line.
Otherwise, if 70.66.12.1 doesn't route packets to the world, you have a
borked DHCP setup, and should probably set up eth1 statically, without a
gateway.

Regards,
--
*Art

On 2007-02-17, Zam wrote:
> This command took 30 seconds to execute:
>
> dave@penrose ~ $ netstat -r
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 192.168.42.0 * 255.255.255.0 U 0 0 0 eth0
> 70.66.12.0 * 255.255.252.0 U 0 0 0 eth1
> loopback * 255.0.0.0 U 0 0 0 lo
> default 192.168.42.1 0.0.0.0 UG 0 0 0 eth0
> default 70.66.12.1 0.0.0.0 UG 0 0 0 eth1

My guess is that netstat tries, and fails, to resolve the addresses
through DNS. Try netstat -rn to avoid DNS lookups and see if that's
faster.

Two default gateways? Not a problem in itself, but it's probably
redundant. You might want to remove one, or configure metrics on the
devices/routes to have more control over which link is supposed to be
the primary one.

I can't quite decide with myself whether the two gateways might have
something to do with the delay, as in DNS queries being routed the wrong
way. On the other hand, the fact that the delay only happens when eth1
is up might also be because lookups for 70.66.12.* for some reason take
a long time. Again, netstat -rn is your friend

--
Jesper Cheetah <xyborx+usenet@xyborx.dk>

Jesper Cheetah <xyborx+usenet@xyborx.dk> wrote:

>> loopback * 255.0.0.0 U 0 0 0 lo
>> default 192.168.42.1 0.0.0.0 UG 0 0 0 eth0
>> default 70.66.12.1 0.0.0.0 UG 0 0 0 eth1
>
> My guess is that netstat tries, and fails, to resolve the addresses
> through DNS. Try netstat -rn to avoid DNS lookups and see if that's
> faster.
>
> Two default gateways? Not a problem in itself, but it's probably
> redundant.

Thanks, that sorted it. I will explore netstat a little.

-z