[Sussex] Anyone into bondage?

Brendan Whelan b_whelan at mistral.co.uk
Thu Sep 29 13:51:15 UTC 2005


Ronan,

Thanks for the response. You are right, I am sure that the ifconfig listed
more information before I had to reconfigure the system.
The question is how do I get the eth devices to reappear?

Hi Brendan

On Thu, 29 Sep 2005 11:51:18 +0100
"Brendan Whelan" <b_whelan at mistral.co.uk> wrote:

<snip>
> service network restart
> ifup eth0
> ifup eth1
>
</snip>

But I notice that below in your ifconfig output, neither device shows
up, only bond0 and lo?  Strange - on my debian machine both eth*
devices appear as well as the bond0 device...

<snip>
> -------------------------------
> ifconfig
> bond0     Link encap:Ethernet  HWaddr 00:C0:9F:39:3F:20
>           inet addr:nnn.nnn.40.30  Bcast:nnn.nnn.40.255
> Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
>           RX packets:273 errors:0 dropped:4294966607 overruns:0
> frame:0 TX packets:146 errors:0 dropped:455 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:18050 (17.6 KiB)  TX bytes:9474 (9.2 KiB)
>
> 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:4751 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:4751 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:5610892 (5.3 MiB)  TX bytes:5610892 (5.3 MiB)
</snip>

Cheers

Ronan






More information about the Sussex mailing list