strange network behavior after setup finished - Debian

This is a discussion on strange network behavior after setup finished - Debian ; Hi I recently installed Debian 4.0R1 on my box. The installation process really has improved. For the first time ever I didn't have to manually setup X. Worked quite well. Some nice changes to the number of programs installed by ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: strange network behavior after setup finished

  1. strange network behavior after setup finished

    Hi
    I recently installed Debian 4.0R1 on my box. The installation process
    really has improved. For the first time ever I didn't have to manually
    setup X. Worked quite well. Some nice changes to the number of programs
    installed by default. Good job.
    Unfortunately I encountered a small problem - most probably a bug, but
    I'm not sure.

    When I installed - from DVD - I setup eth0 as my default internet link,
    it was accepted and the setup routine retrieved all necessary stuff from
    a debian site. So far everything OK.
    After rebooting however, I - or rather my box - couldn't establish an
    internet conection. So i did the following:
    -- all done as root, + indicates my commands and the resulting output --

    + ifconfig
    + eth0 Link encap:Ethernet HWaddr 00:40:F4:6E3:81
    + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    + RX packets:133 errors:0 dropped:0 overruns:0 frame:0
    + TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    + collisions:0 txqueuelen:1000
    + RX bytes:8650 (8.4 KiB) TX bytes:1399 (1.3 KiB)
    + Interrupt:12 Base address:0xb400
    +
    + eth1 Link encap:Ethernet HWaddr 00:01:02:9B:C4:90
    + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    + RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    + TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
    + collisions:0 txqueuelen:1000
    + RX bytes:60 (60.0 b) TX bytes:1938 (1.8 KiB)
    + Interrupt:11 Base address:0x6000
    +
    + lo Link encap:Local Loopback
    + inet addr:127.0.0.1 Mask:255.0.0.0
    + inet6 addr: ::1/128 Scope:Host
    + UP LOOPBACK RUNNING MTU:16436 Metric:1
    + RX packets:8 errors:0 dropped:0 overruns:0 frame:0
    + TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
    + collisions:0 txqueuelen:0
    + RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)

    + route
    + Kernel IP routing table
    + Destination Gateway Genmask Flags Metric Ref Use Iface
    + link-local * 255.255.0.0 U 0 0 0 eth1

    eth1 hadn't been setup so far. And the system should know - from
    installation - that eth0 was the default route.

    So, lets look at
    + cat /etc/network/interfaces
    + # This file describes the network interfaces available on your system
    + # and how to activate them. For more information, see interfaces(5).
    +
    + # The loopback network interface
    + auto lo
    + iface lo inet loopback
    +
    + # The primary network interface
    + allow-hotplug eth0
    + iface eth0 inet dhcp

    No eth1 here, just eth0.

    As I dont't want eth1 to be the default, I tried to kill it:
    + ifdown eth1
    + ifdown: interface eth1 not configured

    As eth1 had never been setup, this answer makes sense, but where had it
    been setup and where did it get its values from and what made it the
    default gateway?

    eth0 still doesn't connect to the web, so we will have to kill eth0 and
    restart it, so it will behave as expected.
    + ifdown eth0
    + There is already a pid file /var/run/dhclient.eth0.pid with pid 2364
    + killed old client process, removed PID file
    + Internet Systems Consortium DHCP Client V3.0.4
    + Copyright 2004-2006 Internet Systems Consortium.
    + All rights reserved.
    + For info, please visit http://www.isc.org/sw/dhcp/
    +
    + Listening on LPF/eth0/00:40:f4:6e:d3:81
    + Sending on LPF/eth0/00:40:f4:6e:d3:81
    + Sending on Socket/fallback
    + DHCPRELEASE on eth0 to 80.69.100.110 port 67
    + send_packet: Network is unreachable
    + send_packet: please consult README file regarding broadcast address.

    followes by
    + ifup eth0
    + eth0: link up, no IPv6 routers present

    and
    + ifconfig
    + eth0 Link encap:Ethernet HWaddr 00:40:F4:6E3:81
    + inet addr:62.143.21.124 Bcast:62.143.21.255 Mask:255.255.255.0
    + inet6 addr: fe80::240:f4ff:fe6e:d381/64 Scope:Link
    + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    + RX packets:406 errors:0 dropped:0 overruns:0 frame:0
    + TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
    + collisions:0 txqueuelen:1000
    + RX bytes:25676 (25.0 KiB) TX bytes:3633 (3.5 KiB)
    + Interrupt:12 Base address:0xb400
    +
    + eth1 Link encap:Ethernet HWaddr 00:01:02:9B:C4:90
    + inet addr:169.254.96.205 Bcast:169.254.255.255 Mask:255.255.0.0
    + inet6 addr: fe80::201:2ff:fe9b:c490/64 Scope:Link
    + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    + RX packets:3 errors:0 dropped:0 overruns:0 frame:0
    + TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
    + collisions:0 txqueuelen:1000
    + RX bytes:240 (240.0 b) TX bytes:3669 (3.5 KiB)
    + Interrupt:11 Base address:0x6000
    +
    + lo Link encap:Local Loopback
    + inet addr:127.0.0.1 Mask:255.0.0.0
    + inet6 addr: ::1/128 Scope:Host
    + UP LOOPBACK RUNNING MTU:16436 Metric:1
    + RX packets:720 errors:0 dropped:0 overruns:0 frame:0
    + TX packets:720 errors:0 dropped:0 overruns:0 carrier:0
    + collisions:0 txqueuelen:0
    + RX bytes:56192 (54.8 KiB) TX bytes:56192 (54.8 KiB)

    So two questions:
    1. Is it a bug or a - maybe undocumented - feature.
    2. How do I get rid of the spooky eth1 settings - read: where are they
    hidden?

    Thanks for any help.

    Axel


    --
    please don't answer to meiwakudone..., it will never be read.
    For private answers s/meiwakudome/kaigisha/, but better answer to the list.


    --
    To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Re: strange network behavior after setup finished

    Op 28-11-2007 om 15:56 schreef Axel Schlicht:

    > So two questions:
    > 1. Is it a bug or a - maybe undocumented - feature.
    > 2. How do I get rid of the spooky eth1 settings - read: where are they
    > hidden?


    I see traces of "zeroconf" in the setting of eth1.
    See `man avahi-daemon` for more information about zeroconf.

    Why eth1 is preferred above eth0 might also be an avahi thing.


    > Thanks for any help.


    You are too generous ;-)


    Cheers
    Geert Stappers


    --
    To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread