Mandrake 10.1 - "Bringing up eth0: FAILED"

zhex900 · November 17, 2004

:deal:

After installing Mandrake 10.1 eth0 is running good. However after reboot, "Bringing up eth0: FAILED" . I am only basic linux user can someone help me.

%cat /etc/resolv.conf

search nsw.optushome.com.au

nameserver 203.2.75.132

nameserver 198.142.0.51

%lspci | grep Ethernet

00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL -8129/8139C/8139C+ (rev10)

00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL -8129/8139C/8139C+ (rev10)

I assume this means that my box can see the two ethernet cards, so the driver is working.

%ifconfig eth0 192.168.0.11

%ping 192.168.0.5

PING 192.168.0.5 (192.168.0.5) 56(84) bytes of data.

From 192.168.0.11 icmp_seq=1 Destination Host Unreachable

From 192.168.0.11 icmp_seq=2 Destination Host Unreachable

From 192.168.0.11 icmp_seq=3 Destination Host Unreachable

--- 192.168.0.5 ping statistics ---

5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3998ms

, pipe 3

%ping 192.168.0.11

PING 192.168.0.11 (192.168.0.11) 56(84) bytes of data.

64 bytes from 192.168.0.11: icmp_seq=1 ttl=64 time=0.065 ms

--- 192.168.0.11 ping statistics ---

1 packets transmitted, 1 received, 0% packet loss, time 0ms

rtt min/avg/max/mdev = 0.065/0.065/0.065/0.000 ms

%ifconfg

eth0 Link encap:Ethernet HWaddr 00:02:44:11:DD:24

inet6 addr: fe80::202:44ff:fe11:dd24/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:195 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b ) TX bytes:33386 (32.6 Kb)

Interrupt:9 Base address:0x9f00

eth0:9 Link encap:Ethernet HWaddr 00:02:44:11:DD:24

inet addr:127.255.255.255 Bcast:127.255.255.255 Mask:255.0.0.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Interrupt:9 Base address:0x9f00

eth1 Link encap:Ethernet HWaddr 00:50:22:E9:8E:A4

inet6 addr: fe80::250:22ff:fee9:8ea4/64 Scope:Link

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:23 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b ) TX bytes:2538 (2.4 Kb)

Interrupt:11 Base address:0xae00

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:243 errors:0 dropped:0 overruns:0 frame:0

TX packets:243 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:20570 (20.0 Kb) TX bytes:20570 (20.0 Kb)

%ifup eth0

Determining IP information for eth0... done.

/sbin/ifup: line 433: 7771 Hangup /etc/init.d/tmdns reload >/dev/null 2>&1

% /etc/init.d/network status

Configured devices:

lo eth0

Currently active devices:

lo eth1

%time /etc/init.d/network restart

Shutting down interface eth0: [ OK ]

Shutting down loopback interface: [ OK ]

Setting network parameters: [ OK ]

Bringing up loopback interface: [ OK ]

Bringing up interface eth0: [ OK ]

1.90user 0.66system 1:38.44elapsed 2%CPU (0avgtext+0avgdata 0maxresident)k

0inputs+0outputs (0major+64810minor)pagefaults 0swaps

%ping 192.168.0.11

connect: Network is unreachable

%cat /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0

BOOTPROTO=dhcp

onBOOT=yes

MII_NOT_SUPPORTED=yes

NEEDHOSTNAME=yes

check_link_down(){

return 1;

}

:-?

arctic · November 18, 2004

hi there :)

%lspci | grep Ethernet
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL -8129/8139C/8139C+ (rev10)

00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL -8129/8139C/8139C+ (rev10)

I assume this means that my box can see the two ethernet cards, so the driver is working.

do you really have two identical ethernet cards in your box or have you accidently set up your network-card twice? (which could be possible)

do you only use one eth-card or do you connect to several places with different eth-cards? from what i see, you simply have many networking devices set up although you only need one. thus, your box will try to determine an ip-adress for every card, even if you only use one card for networking at a time.

check your status/number of networking devices with harddrake and deactivate e.g. the "automatically start at system-start" for those devices you do not really need.

:)

Edited November 18, 2004 by arctic

zhex900 · November 18, 2004

:help:

Ya there is two ethernet cards in my machine. I want to use it as a server, so one in and one out. I guess I need both ethernet cards working. Now, I am pretty sure is the ip problem, since after installation it works for a little while then the box can't determine its own ip address. Is it easier if I make the ip address static?

Cheers :wall:

Jake

arctic · November 18, 2004

in case that you have a permanent connection from box a to b (that is: not constantly changing cables etc.) i think that setting up static ips would be a way to lessen the problems you are encountering. just give it a try. in case that it doesn't help, you can always roll back to the previous status.

keep us informed on your progress and good luck. :)

zhex900 · November 30, 2004

in case that you have a permanent connection from box a to b (that is: not constantly changing cables etc.) i think that setting up static ips would be a way to lessen the problems you are encountering. just give it a try. in case that it doesn't help, you can always roll back to the previous status.
keep us informed on your progress and good luck. :)

<{POST_SNAPBACK}>

trouble with setting up static IP, cannot get on to the internet :wall:

My windows machine have the following

#ipconfig /alll

Windows IP Configuration

Host Name . . . . . . . . . . . . : zhex900
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 08-00-46-99-B6-28
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 203.2.75.132
198.142.0.51

This is what I did to setup the static ip on my mandrake10 box.

# ifconfig eth0 inet 192.168.0.11 netmask 255.255.255.0

# route add default gw 192.168.0.1 eth0

The linux box only can see machine within the internal network, but can not ping anything outside.

ping 198.142.0.51
PING 198.142.0.51 (198.142.0.51) 56(84) bytes of data.
From 192.168.0.11 icmp_seq=1 Destination Host Unreachable
From 192.168.0.11 icmp_seq=2 Destination Host Unreachable
From 192.168.0.11 icmp_seq=3 Destination Host Unreachable

--- 198.142.0.51 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3998ms
, pipe 3

cat /etc/resolv.conf
search nsw.optushome.com.au
nameserver 203.2.75.132
nameserver 198.142.0.51

# ppp temp entry

Kernel IP routing table
Destination        Gateway           Genmask     Flags Metric Ref Use Iface
192.168.0.0       * 255.255.255.0                  U 0 0 0 eth0
127.0.0.0           *                     255.0.0.0    U 0 0 0 lo
default               192.168.0.1      0.0.0.0       UG 0 0 0 eth0

#cat /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.0.11
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
onBOOT=yes
MII_NOT_SUPPORTED=yes

Edited November 30, 2004 by zhex900

arctic · November 30, 2004

i guess you are connected to a router of any sort. do you have any firewall enabled on your linux-box? if yes, disable the firewall for now (e.g. via mandy-control-center). also: if you use a router for your network, (it looks like that as you are connecting to 192.168.x.x) have you made sure to disable shcp in your router settings? also: is NAT/firewall activated in your router? take a look.

zhex900 · December 7, 2004

i guess you are connected to a router of any sort. do you have any firewall enabled on your linux-box? if yes, disable the firewall for now (e.g. via mandy-control-center). also: if you use a router for your network, (it looks like that as you are connecting to 192.168.x.x) have you made sure to disable shcp in your router settings? also: is NAT/firewall activated in your router? take a look.

<{POST_SNAPBACK}>

The firewall is disabled, if I enable the firewall on the linux box, other machines in the network can't even ping the linux box. :wall:

I have a NETGEAR FR114P Router with a in build firewall, I don't think I can disable shcp.

Edited December 7, 2004 by zhex900

arctic · December 8, 2004

sorry, i made a typo. :woops: i did not mean shcp but dhcp, the dynamic host connection protocol. you can use either dhcp or static ips. if you use static ips, you need to disable dhcp on both your linux-box and your router. if your router has an option for configuring (most have a web-interface, reachable by typing 192.168.1.1 in the browser) ther should be a possibility to switch from dhcp to static ip.

don't give up or get frustrated. sometimes it is hard to find the trouble maker, but most times we succeded in here. anyway, good luck. :)

zhex900 · December 8, 2004

sorry, i made a typo. :woops: i did not mean shcp but dhcp, the dynamic host connection protocol. you can use either dhcp or static ips. if you use static ips, you need to disable dhcp on both your linux-box and your router. if your router has an option for configuring (most have a web-interface, reachable by typing 192.168.1.1 in the browser) ther should be a possibility to switch from dhcp to static ip.

don't give up or get frustrated. sometimes it is hard to find the trouble maker, but most times we succeded in here. anyway, good luck. :)

<{POST_SNAPBACK}>

Ok. Now this question is getting really elementary but I need your help.

In my router configure page, the static address section have the following default values:

IP address 211.30.99.78

IP subnet mask 255.255.255.0

Gateway IP address 211.30.99.1

Do I need to change these things?

Another thing, is that my windows machine is using static ip, while my router still is configured to use dhcp. My windows box is working fine.

Edited December 8, 2004 by zhex900

arctic · December 8, 2004

the entries look okay, imho. what worries me is that your win-box is able to run with a static ip, while mandy does not want to work with a static ip.

i am getting a bit desperate, i must admit but i came across te idea than maybe, as you are using a router, you are suffering from the (in)famous ipv6 problem. we had several topics in here with ipv6 problems on routers. check the networking section of the forum on this one.

some basic things you could try: edit your /etc/sysconfig/network file and add the following line:

NETWORKING_IPV6=0

and edit your /etc/sysctl.conf file. add a line at the ipv-section:

net.ipv4.tcp_window_scaling=0

and: edit /etc/modprobe.conf so that you have these entries in it:

alias net-pf-10 off

alias ipv6 off

i hope this is the right track and helps...

good luck :thumbs:

zhex900 · December 8, 2004

the entries look okay, imho. what worries me is that your win-box is able to run with a static ip, while mandy does not want to work with a static ip.

i am getting a bit desperate, i must admit but i came across te idea than maybe, as you are using a router, you are suffering from the (in)famous ipv6 problem. we had several topics in here with ipv6 problems on routers. check the networking section of the forum on this one.

some basic things you could try: edit your /etc/sysconfig/network file and add the following line:

NETWORKING_IPV6=0

and edit your /etc/sysctl.conf file. add a line at the ipv-section:

net.ipv4.tcp_window_scaling=0

and: edit /etc/modprobe.conf so that you have these entries in it:

alias net-pf-10 off

alias ipv6 off

i hope this is the right track and helps...

good luck

<{POST_SNAPBACK}>

After I make the above changes and `service network restart` I still cannot access the net.

:thanks: Mate, this thing is getting really complicated. The fanny thing is that even after I set my router to static ip. Other machines in the network can still use dhcp, other machines can still use the internet. Is this normal?

I have also tried to restart my router, my turning the power on/off.

Is this normal?

# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Edited December 8, 2004 by zhex900

adamw · December 8, 2004

When you set your router to static IP, I believe you're dealing with *its* IP - the IP it uses to access the network on the *other* side of it, i.e., the internet. I don't think you're dealing with whether clients on your *local* network can connect to it via DHCP or not. This is just what it looks like to me from the page you quoted, though, IMBW.

zhex900 · December 8, 2004

When you set your router to static IP, I believe you're dealing with *its* IP - the IP it uses to access the network on the *other* side of it, i.e., the internet. I don't think you're dealing with whether clients on your *local* network can connect to it via DHCP or not. This is just what it looks like to me from the page you quoted, though, IMBW.

<{POST_SNAPBACK}>

Finally its working now.

All I did was install and run pump.

Thank you very much for everyones help :thanks:

arctic · December 8, 2004

installing pump and dnsmasq would have been my last suggestions (as made in other topics).

glad to hear that your network is up and running :)

Mandrake 10.1 - "Bringing up eth0: FAILED"

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation