Mailinglist Archive: opensuse (4417 mails)
| < Previous | Next > |
Re: [SLE] First time Network/Internet in need.
- From: "Anders Lundin" <linux@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 22 Nov 2003 18:20:25 +0100
- Message-id: <000901c3b11c$eeae8040$9dd9d7d9@server>
Pardon me list members as i had to take a brief route of the list to have
Marshall check
my numbers. As i dont whant them public. I have exchanged the numbers whith
X to
keep it on the list.
Thanks
------------------------------------
> >Switched to next nic, btw both my nic ar ON/IN the mobo. And i got
patrial
> >sucess :-)
> >When i start SuSE both my nic are reported 'Fault' in startup list. And
when
> >pinging i got following result.
>
> >andlun@linux:~> su
> >Password:
> >linux:/home/andlun # route -n
> >Kernel IP routing table
> >Destination Gateway Genmask Flags Metric Ref Use
Iface
> >linux:/home/andlun # ifconfig
> >lo Link encap:Local Loopback
> > inet addr:X Mask:X
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:40 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)
>
> >linux:/home/andlun # ping -c 4 X
> >connect: Network is unreachable
> >linux:/home/andlun #
> --------------------------------------------------
>
> I have this issue with a server machine that is on my network. What is
>happening is that the NIC is not >getting a address from the DHCP server in
>your modem and therefore is not up yet. If you was to do as >root
"ifconfig
>eth0 up" and "dhcpcd eth0" then you should see your interface up and
running
>with the >addresses you need to get the network up and running. Do the
>above without the quotes.
>
> >Then i start yast and open both nic's, letting yast load them. I then
close
> >them whithout changin anyting, and whats below comes up !!
>
> >linux:/home/andlun # route -n
> >Kernel IP routing table
> >Destination Gateway Genmask Flags Metric Ref Use
Iface
> >X X X U 0
0 0 eth0
> >X X X UG 0
0 0 eth0
> >linux:/home/andlun # ifconfig
> >eth0 Link encap:Ethernet HWaddr 00:0D:61:03:8F:73
> > inet addr:X Bcast:X Mask:X
> > inet6 addr: fe80::20d:61ff:fe03:8f73/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:298 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:20612 (20.1 Kb) TX bytes:1520 (1.4 Kb)
> > Interrupt:5 Base address:0x9800 Memory:e9000000-e9020000
>
> >lo Link encap:Local Loopback
> > inet addr:X Mask:X
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:40 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)
>
> >linux:/home/andlun # ping -c 4 X
> >PING 217.215.217.1 (217.215.217.1) 56(84) bytes of data.
> >64 bytes from 217.215.217.1: icmp_seq=1 ttl=255 time=14.9 ms
> >64 bytes from 217.215.217.1: icmp_seq=2 ttl=255 time=13.1 ms
> >64 bytes from 217.215.217.1: icmp_seq=3 ttl=255 time=13.2 ms
> >64 bytes from 217.215.217.1: icmp_seq=4 ttl=255 time=13.5 ms
>
> >--- X ping statistics ---
> >4 packets transmitted, 4 received, 0% packet loss, time 3002ms
> >rtt min/avg/max/mdev = 13.127/13.707/14.933/0.735 ms
> >linux:/home/andlun #
>
> >Only eth0 is showing and no eth1. Locking in yast eth0 is avalebel but
not
> >configured. eth1 is both avalebel and configured. eth0 is the one
conecting
> >to gateway. NO settings ar changed conserning numbers. the old one showed
> >up by themself. So this has to rool out any misstyping.
> >So why are the settings not sticking. And why is only one nic showing up
?
>
> Ok here goes the long winded explanation of the above phenominia. When
>yast configures the cards, it >wil configure them in the order that it sees
>them and will set them up accordingly. The first one that it sees >will be
>eth0 and the second eth1. Now what has happened when the system (network)
>was brought up, >For some reason, eth0 in Yast could not get configured.
So
>then the script went on to try and configure >the other card that was in
the
>system. This one was able to be configured and was brought up by
>ifconfig.
>Then ifconfig brought up the interface, it brought it up as eth0 instead of
>eth1. This is why you >might be seeing this phenomenon. Now to the
>question of why the interface did not get configured, Well >let us see
what
>we can find here.
>
> 1) Was it configured in Yast? Just becuase Yast found it doesn't mean
>that it will configure it.
Yes i cofigured it in yast.
> 2) Could the NIC's be conflicting with each other? Another words, can
>they be sharing the same >memory address or IRQ?
>
Where can i check the irq and adresses ? i'we tried hw info. But the file i
save from
there seems to bee empty.
> Let us get the above questions answered before we move on to trying to get
it fixed.
>
> What motherboard is this to have 2 NIC cards in it? This is very unusual!
Is this a server mobo?
>
Gigabyte 7-NNXP with AMD +2500 Barton.
> >By the way if you get this i'm sending it from SuSE 'kmail' :-)))
>
> Cool! Looks like we are getting somewhere and you are getting closer to
getting the machine to do >what you want it to do!
>
> Marshall
Phiew, steep learning curve :-)
Marshall check
my numbers. As i dont whant them public. I have exchanged the numbers whith
X to
keep it on the list.
Thanks
------------------------------------
> >Switched to next nic, btw both my nic ar ON/IN the mobo. And i got
patrial
> >sucess :-)
> >When i start SuSE both my nic are reported 'Fault' in startup list. And
when
> >pinging i got following result.
>
> >andlun@linux:~> su
> >Password:
> >linux:/home/andlun # route -n
> >Kernel IP routing table
> >Destination Gateway Genmask Flags Metric Ref Use
Iface
> >linux:/home/andlun # ifconfig
> >lo Link encap:Local Loopback
> > inet addr:X Mask:X
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:40 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)
>
> >linux:/home/andlun # ping -c 4 X
> >connect: Network is unreachable
> >linux:/home/andlun #
> --------------------------------------------------
>
> I have this issue with a server machine that is on my network. What is
>happening is that the NIC is not >getting a address from the DHCP server in
>your modem and therefore is not up yet. If you was to do as >root
"ifconfig
>eth0 up" and "dhcpcd eth0" then you should see your interface up and
running
>with the >addresses you need to get the network up and running. Do the
>above without the quotes.
>
> >Then i start yast and open both nic's, letting yast load them. I then
close
> >them whithout changin anyting, and whats below comes up !!
>
> >linux:/home/andlun # route -n
> >Kernel IP routing table
> >Destination Gateway Genmask Flags Metric Ref Use
Iface
> >X X X U 0
0 0 eth0
> >X X X UG 0
0 0 eth0
> >linux:/home/andlun # ifconfig
> >eth0 Link encap:Ethernet HWaddr 00:0D:61:03:8F:73
> > inet addr:X Bcast:X Mask:X
> > inet6 addr: fe80::20d:61ff:fe03:8f73/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:298 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:20612 (20.1 Kb) TX bytes:1520 (1.4 Kb)
> > Interrupt:5 Base address:0x9800 Memory:e9000000-e9020000
>
> >lo Link encap:Local Loopback
> > inet addr:X Mask:X
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:40 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)
>
> >linux:/home/andlun # ping -c 4 X
> >PING 217.215.217.1 (217.215.217.1) 56(84) bytes of data.
> >64 bytes from 217.215.217.1: icmp_seq=1 ttl=255 time=14.9 ms
> >64 bytes from 217.215.217.1: icmp_seq=2 ttl=255 time=13.1 ms
> >64 bytes from 217.215.217.1: icmp_seq=3 ttl=255 time=13.2 ms
> >64 bytes from 217.215.217.1: icmp_seq=4 ttl=255 time=13.5 ms
>
> >--- X ping statistics ---
> >4 packets transmitted, 4 received, 0% packet loss, time 3002ms
> >rtt min/avg/max/mdev = 13.127/13.707/14.933/0.735 ms
> >linux:/home/andlun #
>
> >Only eth0 is showing and no eth1. Locking in yast eth0 is avalebel but
not
> >configured. eth1 is both avalebel and configured. eth0 is the one
conecting
> >to gateway. NO settings ar changed conserning numbers. the old one showed
> >up by themself. So this has to rool out any misstyping.
> >So why are the settings not sticking. And why is only one nic showing up
?
>
> Ok here goes the long winded explanation of the above phenominia. When
>yast configures the cards, it >wil configure them in the order that it sees
>them and will set them up accordingly. The first one that it sees >will be
>eth0 and the second eth1. Now what has happened when the system (network)
>was brought up, >For some reason, eth0 in Yast could not get configured.
So
>then the script went on to try and configure >the other card that was in
the
>system. This one was able to be configured and was brought up by
>ifconfig.
>Then ifconfig brought up the interface, it brought it up as eth0 instead of
>eth1. This is why you >might be seeing this phenomenon. Now to the
>question of why the interface did not get configured, Well >let us see
what
>we can find here.
>
> 1) Was it configured in Yast? Just becuase Yast found it doesn't mean
>that it will configure it.
Yes i cofigured it in yast.
> 2) Could the NIC's be conflicting with each other? Another words, can
>they be sharing the same >memory address or IRQ?
>
Where can i check the irq and adresses ? i'we tried hw info. But the file i
save from
there seems to bee empty.
> Let us get the above questions answered before we move on to trying to get
it fixed.
>
> What motherboard is this to have 2 NIC cards in it? This is very unusual!
Is this a server mobo?
>
Gigabyte 7-NNXP with AMD +2500 Barton.
> >By the way if you get this i'm sending it from SuSE 'kmail' :-)))
>
> Cool! Looks like we are getting somewhere and you are getting closer to
getting the machine to do >what you want it to do!
>
> Marshall
Phiew, steep learning curve :-)
| < Previous | Next > |