10.0: no net, now what

older
No access to windows fat partition...

Doug McGarrett

22 Oct 2005 22 Oct '05

03:08

I just installed Suse 10.0 from the CD's--I can't boot from DVD, for some reason--and I can not reach the internet. 9.2 worked. 8.2 worked. 10.0--zip. Maybe it's due to the firewall that is installed automatically? I have a Linksys router with a firewall, I don't know why I need one from Linux. This is the same machine, and as you see, the Windows connection to the net works fine. I'm not a computer maven, so I would appreciate a solution in words of one syllable. TIA--doug -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.4/146 - Release Date: 10/21/2005

Show replies by date

Sid Boyce

22 Oct 22 Oct

03:43

New subject: [SLE] 10.0: no net, now what

Doug McGarrett wrote:

...

I just installed Suse 10.0 from the CD's--I can't boot from DVD, for some reason--and I can not reach the internet. 9.2 worked. 8.2 worked. 10.0--zip. Maybe it's due to the firewall that is installed automatically? I have a Linksys router with a firewall, I don't know why I need one from Linux. This is the same machine, and as you see, the Windows connection to the net works fine. I'm not a computer maven, so I would appreciate a solution in words of one syllable.

TIA--doug

If it's the firewall, it can be disabled in YaST under "Security and Users". A check under "Network Devices" to make sure the ethernet card set up for DHCP and to allow DHCP to set /etc/resolv.conf (DNS server). Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks

Mike McMullin

10:32

New subject: [SLE] 10.0: no net, now what

On Fri, 2005-10-21 at 23:08 -0400, Doug McGarrett wrote:

...

I just installed Suse 10.0 from the CD's--I can't boot from DVD, for some reason--and I can not reach the internet. 9.2 worked. 8.2 worked. 10.0--zip. Maybe it's due to the firewall that is installed automatically? I have a Linksys router with a firewall, I don't know why I need one from Linux. This is the same machine, and as you see, the Windows connection to the net works fine. I'm not a computer maven, so I would appreciate a solution in words of one syllable.

First step is to open a shell and ping your router, the (4d address) 192.168.?.? address is in the manual. If that happens then you need to know the 4d address of an external site (try 65.75.184.79) if you can ping the router and not the external site then you have a gateway issue, if you can't ping the router then you have a network card issue. If both ping, then you have a DNS lookup issue.

Jerry Feldman

17:25

New subject: [SLE] 10.0: no net, now what

On Fri, 21 Oct 2005 23:08:16 -0400 Doug McGarrett wrote:

...

I just installed Suse 10.0 from the CD's--I can't boot from DVD, for some reason--and I can not reach the internet. 9.2 worked. 8.2 worked. 10.0--zip. Maybe it's due to the firewall that is installed automatically? I have a Linksys router with a firewall, I don't know why I need one from Linux. This is the same machine, and as you see, the Windows connection to the net works fine. I'm not a computer maven, so I would appreciate a solution in words of one syllable. I just installed 10 on my laptop at home (using a static IP through a Linksys box), tested both DHCP and Wireless, set up multiple profiles. Upon arrival at my hotel, the system came up, connected to their internal network with no problem. I also configured a local printer since we had a DeskJet in our conference area. The only issue I had was on printer detection, and it may be more my impatience. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

HG

17:35

New subject: [SLE] 10.0: no net, now what

Hi! On 10/22/05, Jerry Feldman wrote:

...

I just installed 10 on my laptop at home (using a static IP through a Linksys box), tested both DHCP and Wireless, set up multiple profiles. Upon arrival at my hotel, the system came up, connected to their internal network with no problem. I also configured a local printer

I more or less (what do you mean by multiple profiles) did the same. Except, that I had DHCP at home and now at my parents place nothing (i.e. cable and WLAN) works with DHCP even though in windows it all works (with the exact same DHCP and laptop). I have no idea on how to get it to work as it just worked at my home. I thought this networks stuff was very well covered on linux, but currently it seems that windows is again years ahead. I keep on rebooting this linux system and hoping that after some reboot it would start to work. In YaST everything seems the same as I've always had (DHCP-everything). I really do not know which buttons to push anymore, I'm quite disappointed. (I could go to the shell to fix things if I knew how to. But I really only know YaST and that doesn't help... And it certainly isn't an answer to the other user of this laptop. For her, I need to get linux working as smoothly as win2000.) -- HG.

Ken Schneider

17:56

New subject: [SLE] 10.0: no net, now what

On Sat, 2005-10-22 at 20:35 +0300, HG wrote:

...

Hi!

On 10/22/05, Jerry Feldman wrote:

...
I just installed 10 on my laptop at home (using a static IP through a Linksys box), tested both DHCP and Wireless, set up multiple profiles. Upon arrival at my hotel, the system came up, connected to their internal network with no problem. I also configured a local printer

I more or less (what do you mean by multiple profiles) did the same. Except, that I had DHCP at home and now at my parents place nothing (i.e. cable and WLAN) works with DHCP even though in windows it all works (with the exact same DHCP and laptop). I have no idea on how to get it to work as it just worked at my home. I thought this networks stuff was very well covered on linux, but currently it seems that windows is again years ahead. I keep on rebooting this linux system and hoping that after some reboot it would start to work. In YaST everything seems the same as I've always had (DHCP-everything). I really do not know which buttons to push anymore, I'm quite disappointed.

Just because you do not know which buttons to push does not make linux behind the times as far as networking goes. linux has always had better networking then MS -ever- will. Rebooting multiple times will not change a configuration, that is something you need to learn how to do. YaST-->Network Devices-->select your card in the lower area and then click on the change button. Highlight your card (you may only have one) and then click on the edit button. Under "Setup Method" select DHCP Click on Routing-->fill in the IP address of your router as the Default Gateway. Click on the Next button and then the Finish Button. Your networking should now work, if not let us know so that we can help you further. You may have to make some changes for your DNS servers and your Hostname/Domain Name. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

Ken Schneider

18:13

New subject: [SLE] 10.0: no net, now what

On Sat, 2005-10-22 at 13:56 -0400, Ken Schneider wrote:

...

On Sat, 2005-10-22 at 20:35 +0300, HG wrote:

...
Hi!

On 10/22/05, Jerry Feldman wrote:

...
I just installed 10 on my laptop at home (using a static IP through a Linksys box), tested both DHCP and Wireless, set up multiple profiles. Upon arrival at my hotel, the system came up, connected to their internal network with no problem. I also configured a local printer

I more or less (what do you mean by multiple profiles) did the same. Except, that I had DHCP at home and now at my parents place nothing (i.e. cable and WLAN) works with DHCP even though in windows it all works (with the exact same DHCP and laptop). I have no idea on how to get it to work as it just worked at my home. I thought this networks stuff was very well covered on linux, but currently it seems that windows is again years ahead. I keep on rebooting this linux system and hoping that after some reboot it would start to work. In YaST everything seems the same as I've always had (DHCP-everything). I really do not know which buttons to push anymore, I'm quite disappointed.

Just because you do not know which buttons to push does not make linux behind the times as far as networking goes. linux has always had better networking then MS -ever- will. Rebooting multiple times will not change a configuration, that is something you need to learn how to do.

YaST-->Network Devices-->select your card in the lower area and then click on the change button. Highlight your card (you may only have one) and then click on the edit

Should say you might only have one but multiple cards are supported.

...

button. Under "Setup Method" select DHCP Click on Routing-->fill in the IP address of your router as the Default Gateway. Click on the Next button and then the Finish Button.

Your networking should now work, if not let us know so that we can help you further. You may have to make some changes for your DNS servers and your Hostname/Domain Name.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

Doug McGarrett

24 Oct 24 Oct

03:37

New subject: [SLE] 10.0: no net, now what--more

At 02:13 PM 10/22/2005 -0400, you wrote:

...

...
YaST-->Network Devices-->select your card in the lower area and then click on the change button. Highlight your card (you may only have one) and then click on the edit

Should say you might only have one but multiple cards are supported.

...
button. Under "Setup Method" select DHCP Click on Routing-->fill in the IP address of your router as the Default Gateway. Click on the Next button and then the Finish Button.

Your networking should now work, if not let us know so that we can help you further. You may have to make some changes for your DNS servers and your Hostname/Domain Name.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

OK, I guess I was wrong. I must not have had SuSE running on this machine, but I sure thought I did. Broadcom has a driver for this hardware, but I don't understand the directions for making it. It supposedly has been tested on Suse, RedHat, etc. It says the driver has been tested on kernel versions up to 2.4.31 and 2.6.12. One of the documents on the site says you have to have GCC and compile it; another document (README.TXT) does not refer to GCC. It looks like I would need ver. 8.2.18 of the driver. If anyone would like to look at the site and comment on the files, it's at http://www.broadcom.com/drivers/downloaddrivers.php Then maybe you can lead my by the hand to make this work on 10.0. Otherwise I guess there will be no Suse Linux on this machine. I guess it would run on the little machine, but it's pretty slow. (I have to get Linspire off of there anyway--it has no apps, and they want to sell you each one. Forget the free software, etc.) Thanx guys, I know you all tried. --doug -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.361 / Virus Database: 267.12.4/146 - Release Date: 10/21/2005

Doug McGarrett

23 Oct 23 Oct

20:48

New subject: [SLE] 10.0: no net, now what, cont'd

At 01:56 PM 10/22/2005 -0400, Ken Schneider wrote:

...

/snip/

...

YaST-->Network Devices-->select your card in the lower area and then click on the change button. Highlight your card (you may only have one) and then click on the edit button. Under "Setup Method" select DHCP Click on Routing-->fill in the IP address of your router as the Default Gateway. Click on the Next button and then the Finish Button.

Your networking should now work, if not let us know so that we can help you further. You may have to make some changes for your DNS servers and your Hostname/Domain Name.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

What I have done so far: I found out how to get into yast graphical mode, from a console. I don't know how to do it from the desktop. At any rate, I followed your instructions as nearly as possible. Yast found the network card by itself. I didn't have to look in the lower area. (I looked anyway, and my "card" isn't there.) It automatically selected DHCP and it found the ip address of the router by itself for the default gateway. The following available command is not "next" but "OK". There does not seem to be a "finish" command. I forget what came next, but somehow I got back to the yast main window and closed it. At this point I tried to ping the router itself (should work, but did not) and tried to ping an outside source which I can ping from Windows or the other Linux machine. Somewhere it said that the network starts at boot, so I will reboot into Suse and see if the network starts, and I'll report back either way. Someone asked about the results of ifconfig and lsmod. Unfortunately, I do not have any way of forwarding those, since I can't save them to NTFS, and I can't send them direct from Suse--no network! Can I somehow save them to a .txt file in XP, from which I could copy and paste to this mailer? Whoever it was also asked for the type of Ethernet hardware--its Broadcom NetXtreme Gigabit Ethernet, part of the MOBO, but Yast seems to be able to find it OK. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.361 / Virus Database: 267.12.4/146 - Release Date: 10/21/2005

Doug McGarrett

22:12

New subject: [SLE] 10.0: no net, now what, cont'd

Doug McGarrett wrote:

...

At 01:56 PM 10/22/2005 -0400, Ken Schneider wrote:

/snip/

...
YaST-->Network Devices-->select your card in the lower area and then click on the change button. Highlight your card (you may only have one) and then click on the edit button. Under "Setup Method" select DHCP Click on Routing-->fill in the IP address of your router as the Default Gateway. Click on the Next button and then the Finish Button.

Your networking should now work, if not let us know so that we can help you further. You may have to make some changes for your DNS servers and your Hostname/Domain Name.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

What I have done so far:

I found out how to get into yast graphical mode, from a console. I don't know how to do it from the desktop. At any rate, I followed your instructions as nearly as possible.

Yast found the network card by itself. I didn't have to look in the lower area. (I looked anyway, and my "card" isn't there.) It automatically selected DHCP and it found the ip address of the router by itself for the default gateway. The following available command is not "next" but "OK". There does not seem to be a "finish" command. I forget what came next, but somehow I got back to the yast main window and closed it.

At this point I tried to ping the router itself (should work, but did not) and tried to ping an outside source which I can ping from Windows or the other Linux machine.

Somewhere it said that the network starts at boot, so I will reboot into Suse and see if the network starts, and I'll report back either way.

Someone asked about the results of ifconfig and lsmod. Unfortunately, I do not have any way of forwarding those, since I can't save them to NTFS, and I can't send them direct from Suse--no network! Can I somehow save them to a .txt file in XP, from which I could copy and paste to this mailer?

Whoever it was also asked for the type of Ethernet hardware--its Broadcom NetXtreme Gigabit Ethernet, part of the MOBO, but Yast seems to be able to find it OK.

I rebooted Suse. No joy, no network. Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.) If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output, but I sure can't type in the page-and-a-quarter of codes and numbers from lsmod. A little better description of the ethernet hardware: Yast says it's Broadcom NetXtreme BCM5702X Gigabit Ethernet. The result I get when I try to ping the router is "Network is unreachable" If no-one can come up with a solution, I'll reinstall and hope for the best. I'd rather not do that, because if it still doesn't work, where am I? My thanx to those who have answered so far, and any other suggestions would be appreciated. Just please remember that I am not all that familiar--I'm not much familiar at all--with Linux/Unix. This Linux machine, BTW, is going thru the same router. --doug, wa2say

...

Stephen Boddy

22:34

New subject: [SLE] 10.0: no net, now what, cont'd

On Sunday 23 October 2005 23:12, Doug McGarrett wrote:

...

Doug McGarrett wrote: <munch> I rebooted Suse. No joy, no network.

Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.)

The loopback has nothing to do with a physical network interface. pinging that means nothing.

...

If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output,

Well until you do, we don't even know if the interface (eth0) is there! Enter: # /sbin/ifconfig -a in a shell (don't type the #) and report the first two lines of each interface here. I expect to see eth0, lo and sit0.

...

but I sure can't type in the page-and-a-quarter of codes and numbers from lsmod.

A little better description of the ethernet hardware: Yast says it's Broadcom NetXtreme BCM5702X Gigabit Ethernet.

The result I get when I try to ping the router is "Network is unreachable"

If no-one can come up with a solution, I'll reinstall and hope for the best. I'd rather not do that, because if it still doesn't work, where am I?

My thanx to those who have answered so far, and any other suggestions would be appreciated. Just please remember that I am not all that familiar--I'm not much familiar at all--with Linux/Unix.

This Linux machine, BTW, is going thru the same router.

You seem to be making this a damn site harder than it ought to be. Start YaST, console or graphical, go to Network Devices -> Network Card. Do you have anything listed under the Network Cards to Configure, or Already Configured Devices sections? If it's in the Network Cards to Configure section then it is not yet configured, and your network will not work. If it's in the Already Configured Devices section then it is mis-configured, and your network will not work. If it's in neither section then the kernel does not support this NIC (doubtful, as you say it has worked in previous releases,) and your network will never work. -- Steve Boddy

Ken Schneider

22:55

New subject: [SLE] 10.0: no net, now what, cont'd

On Sun, 2005-10-23 at 23:34 +0100, Stephen Boddy wrote:

...

On Sunday 23 October 2005 23:12, Doug McGarrett wrote:

...
Doug McGarrett wrote: <munch> I rebooted Suse. No joy, no network.

Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.)

The loopback has nothing to do with a physical network interface. pinging that means nothing.

...
If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output,

Well until you do, we don't even know if the interface (eth0) is there! Enter:

# /sbin/ifconfig -a

in a shell (don't type the #) and report the first two lines of each interface here. I expect to see eth0, lo and sit0.

sit0? I have no sit0 interface, what does it refer to? What makes it necessary to have an sit0 interface? On my laptop I have eth0, lo and wlan0. No sit0. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

Anders Johansson

23:34

New subject: [SLE] 10.0: no net, now what, cont'd

On Monday 24 October 2005 00:55, Ken Schneider wrote:

...

sit0? I have no sit0 interface, what does it refer to? What makes it necessary to have an sit0 interface? On my laptop I have eth0, lo and wlan0. No sit0.

I believe sit is an ipv6 over ipv4 tunneling device, not really a necessity

Doug McGarrett

24 Oct 24 Oct

00:12

New subject: [SLE] 10.0: no net, now what, cont'd

Please tell me what to look for. I can't send you the output of the command. Very roughly, it looks like this: eth 0 Link encap:Ethernet HW addr 00: and more inet6 addr: fe80: and more UP BROADCAST NOTRAILERS MULTICAST MIU:5100 Metric:1 Rx packets:0 everything 0 TX packets 0 everything 0 collisisions: 0 txqueuelen: 1000 RX bytes 0 TX bytes 0 Interrupt 11 lo Link encap: Local loopback inet addr: 127.0.0.1 Mask 2555.0.0.0 inet6 addr: ::1/128 Scope: Host RX packets 60 errors etc TX packets: 60 errors, etc collisions: txqueelen:0 RX bytes 4476 TX bytes 4476 sit0 Link encap: IPV6-in-IPV4 NOARP MIU: 1480 Metric:1 RX packets, TX packets, collisions, txquelen, etc, all 0 Whatever all this means, the zeros seem to mean that nothing is being transferred. Now what? --doug Ken Schneider wrote:

...

On Sun, 2005-10-23 at 23:34 +0100, Stephen Boddy wrote:

...
On Sunday 23 October 2005 23:12, Doug McGarrett wrote:

...
Doug McGarrett wrote:

<munch>

...
I rebooted Suse. No joy, no network.

Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.)

The loopback has nothing to do with a physical network interface. pinging that means nothing.

...
If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output,

Well until you do, we don't even know if the interface (eth0) is there! Enter:

# /sbin/ifconfig -a

in a shell (don't type the #) and report the first two lines of each interface here. I expect to see eth0, lo and sit0.

sit0? I have no sit0 interface, what does it refer to? What makes it necessary to have an sit0 interface? On my laptop I have eth0, lo and wlan0. No sit0.

Stephen Boddy

03:10

New subject: [SLE] 10.0: no net, now what, cont'd

On Monday 24 October 2005 01:12, Doug McGarrett wrote:

...

Please tell me what to look for. I can't send you the output of the command. Very roughly, it looks like this:

eth 0 Link encap:Ethernet HW addr 00: and more inet6 addr: fe80: and more UP BROADCAST NOTRAILERS MULTICAST MIU:5100 Metric:1 Rx packets:0 everything 0 TX packets 0 everything 0 collisisions: 0 txqueuelen: 1000 RX bytes 0 TX bytes 0 Interrupt 11

Right, this is the important bit. The lack of a line looking like: inet addr:192.168.xxx.yyy Bcast:192.168.xxx.255 Mask:255.255.255.0 Obviously I'm removing the numbers where it's xxx.yyy, and the first two numbers may be different as well. The important bit is that they are there. This line means that the kernel is loading the module for the NIC, but the interface is not being configured. Now I think you said that this interface is configured for DHCP in an earlier message. Double check in YaST that the NIC is configured with DHCP. If that is the case, and the ifconfig command does not show a line like the one above, try as root: # dhcpcd -B eth0 then check ifconfig again. Incidentally, you do have a DHCP server in your network somewhere? Otherwise you are sending out a broadcast message and waiting for a response that never comes. How is your Windows machine configured? DHCP, or a static IP? -- Steve Boddy

kanenas

08:34

New subject: [SLE] 10.0: no net, now what, cont'd

I have filed a bug report on nic configuration problems for 10.0 and 10.1 bug #120332 in the 10.0 bugzilla. I can get a connection ,after 4-8 repeated configurations of the nic card thru yast, with every other config deleting the previous config. I can not find *anything* that the repeated configs change, that's the crazy thing about it... Of course the same setup works great when i switch to the 9.3 partition, it has also worked flawlesly for 9.1 and 9.2 when they were installed in the system. whatever was changed between 9.3 and 10.0 needs to be looked at very carefully. In the meantime 10.0 stays in the "play" partition. d. On Sunday 23 October 2005 05:10 pm, Stephen Boddy wrote:

...

On Monday 24 October 2005 01:12, Doug McGarrett wrote:

...
Please tell me what to look for. I can't send you the output of the command. Very roughly, it looks like this:

eth 0 Link encap:Ethernet HW addr 00: and more inet6 addr: fe80: and more UP BROADCAST NOTRAILERS MULTICAST MIU:5100 Metric:1 Rx packets:0 everything 0 TX packets 0 everything 0 collisisions: 0 txqueuelen: 1000 RX bytes 0 TX bytes 0 Interrupt 11

Right, this is the important bit. The lack of a line looking like:

inet addr:192.168.xxx.yyy Bcast:192.168.xxx.255 Mask:255.255.255.0

Obviously I'm removing the numbers where it's xxx.yyy, and the first two numbers may be different as well. The important bit is that they are there.

This line means that the kernel is loading the module for the NIC, but the interface is not being configured. Now I think you said that this interface is configured for DHCP in an earlier message. Double check in YaST that the NIC is configured with DHCP.

If that is the case, and the ifconfig command does not show a line like the one above, try as root:

# dhcpcd -B eth0

then check ifconfig again.

Incidentally, you do have a DHCP server in your network somewhere? Otherwise you are sending out a broadcast message and waiting for a response that never comes. How is your Windows machine configured? DHCP, or a static IP? -- Steve Boddy

Stephen Boddy

02:54

New subject: [SLE] 10.0: no net, now what, cont'd

On Sunday 23 October 2005 23:55, Ken Schneider wrote: <munch>

...

sit0? I have no sit0 interface, what does it refer to? What makes it necessary to have an sit0 interface? On my laptop I have eth0, lo and wlan0. No sit0.

It's a device for encapsulating IPv6 over IPv4. I've probably got an additional package or config on my system. -- Steve Boddy

Graham Smith

23 Oct 23 Oct

22:35

New subject: [SLE] 10.0: no net, now what, cont'd

On Mon, 24 Oct 2005 08:12, Doug McGarrett wrote: > BIG SNIP <

...

If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output, but I sure can't type in the page-and-a-quarter of codes and numbers from lsmod.

A little better description of the ethernet hardware: Yast says it's Broadcom NetXtreme BCM5702X Gigabit Ethernet.

The result I get when I try to ping the router is "Network is unreachable"

If no-one can come up with a solution, I'll reinstall and hope for the best. I'd rather not do that, because if it still doesn't work, where am I?

To redirect the output to a file use '>' e.g ifconfig > ~/ifconfig.txt route > ~/route.txt lsmod > ~/lsmod.txt To redirect the output and append the results to a file use '>>' e.g. ifconfig > ~/network-cfg.txt route >> ~/network-cfg.txt To pipe the output to your printer ifconfig | lpr Please refer to the following sites for more information on I/O redirection. http://www.linuxsa.org.au/tips/io-redirection.html http://www.cpqlinux.com/redirect.html -- Regards, Graham Smith

Mike McMullin

24 Oct 24 Oct

09:52

New subject: [SLE] 10.0: no net, now what, cont'd

On Sun, 2005-10-23 at 18:12 -0400, Doug McGarrett wrote:

...

Doug McGarrett wrote:

...
At 01:56 PM 10/22/2005 -0400, Ken Schneider wrote:

/snip/

//snip//

...

...
What I have done so far:

I found out how to get into yast graphical mode, from a console. I don't know how to do it from the desktop. At any rate, I followed your instructions as nearly as possible.

Yast found the network card by itself. I didn't have to look in the lower area. (I looked anyway, and my "card" isn't there.) It automatically selected DHCP and it found the ip address of the router by itself for the default gateway. The following available command is not "next" but "OK". There does not seem to be a "finish" command. I forget what came next, but somehow I got back to the yast main window and closed it.

At this point I tried to ping the router itself (should work, but did not) and tried to ping an outside source which I can ping from Windows or the other Linux machine.

This is more than likely the route of the problem, here. You ought to be able to ping the router if your network card is properly configured.

...

...
Somewhere it said that the network starts at boot, so I will reboot into Suse and see if the network starts, and I'll report back either way.

Someone asked about the results of ifconfig and lsmod. Unfortunately, I do not have any way of forwarding those, since I can't save them to NTFS, and I can't send them direct from Suse--no network! Can I somehow save them to a .txt file in XP, from which I could copy and paste to this mailer?

When you're in Linux open a console shell (konsole) issue the command su - enter the root user password at the password prompt issue the command ifconfig using your mouse locate the line on the console screen where you involed the ifconfig command, and place it at the beginning of that line, left click and highlight everything until you reach the end of the output from the command. Right click in the highlighted area and choose copy. Paste the output into an e-mail. Repeat for lsmod. Frankly at this point I think you have either a driver problem, or a hardware problem.

...

...
Whoever it was also asked for the type of Ethernet hardware--its Broadcom NetXtreme Gigabit Ethernet, part of the MOBO, but Yast seems to be able to find it OK.

I rebooted Suse. No joy, no network.

Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.)

...

If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output, but I sure can't type in the page-and-a-quarter of codes and numbers from lsmod.

See above, if you actually need to do this.

...

A little better description of the ethernet hardware: Yast says it's Broadcom NetXtreme BCM5702X Gigabit Ethernet.

...

The result I get when I try to ping the router is "Network is unreachable"

If no-one can come up with a solution, I'll reinstall and hope for the best. I'd rather not do that, because if it still doesn't work, where am I?

You shouldn't have to re-install. I've had some problems with nic's under 9.1. They'd work and then they wouldn't find the network. I found that deleting the nic in Yast, closing the NIC YaST component and then going back into it, and installing a new nic (actually the old one) worked. One other thing comes to mind here. Are you sure of your cables and other hardware? swap ports on your router, and switch cables from the box that works to the box that doesn't work. Does the box that works still work?

...

My thanx to those who have answered so far, and any other suggestions would be appreciated. Just please remember that I am not all that familiar--I'm not much familiar at all--with Linux/Unix.

This Linux machine, BTW, is going thru the same router.

Mike

kanenas

23:47

New subject: [SLE] 10.0: no net, now what, cont'd

...

On Sun, 2005-10-23 at 18:12 -0400, Doug McGarrett wrote:

...
Doug McGarrett wrote:

...
At 01:56 PM 10/22/2005 -0400, Ken Schneider wrote:

/snip/

//snip//

...
...
What I have done so far:

I found out how to get into yast graphical mode, from a console. I don't know how to do it from the desktop. At any rate, I followed your instructions as nearly as possible.

Yast found the network card by itself. I didn't have to look in the lower area. (I looked anyway, and my "card" isn't there.) It automatically selected DHCP and it found the ip address of the router by itself for the default gateway. The following available command is not "next" but "OK". There does not seem to be a "finish" command. I forget what came next, but somehow I got back to the yast main window and closed it.

At this point I tried to ping the router itself (should work, but did not) and tried to ping an outside source which I can ping from Windows or the other Linux machine.

This is more than likely the route of the problem, here. You ought to be able to ping the router if your network card is properly configured.

...
...
Somewhere it said that the network starts at boot, so I will reboot into Suse and see if the network starts, and I'll report back either way.

Someone asked about the results of ifconfig and lsmod. Unfortunately, I do not have any way of forwarding those, since I can't save them to NTFS, and I can't send them direct from Suse--no network! Can I somehow save them to a .txt file in XP, from which I could copy and paste to this mailer?

When you're in Linux open a console shell (konsole) issue the command

su - enter the root user password at the password prompt issue the command ifconfig

using your mouse locate the line on the console screen where you involed the ifconfig command, and place it at the beginning of that line, left click and highlight everything until you reach the end of the output from the command. Right click in the highlighted area and choose copy. Paste the output into an e-mail. Repeat for lsmod.

Frankly at this point I think you have either a driver problem, or a hardware problem.

...
...
Whoever it was also asked for the type of Ethernet hardware--its Broadcom NetXtreme Gigabit Ethernet, part of the MOBO, but Yast seems to be able to find it OK.

I rebooted Suse. No joy, no network.

Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.)

If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output, but I sure can't type in the page-and-a-quarter of codes and numbers from lsmod.

See above, if you actually need to do this.

...
A little better description of the ethernet hardware: Yast says it's Broadcom NetXtreme BCM5702X Gigabit Ethernet.

The result I get when I try to ping the router is "Network is unreachable"

If no-one can come up with a solution, I'll reinstall and hope for the best. I'd rather not do that, because if it still doesn't work, where am I?

You shouldn't have to re-install. I've had some problems with nic's under 9.1. They'd work and then they wouldn't find the network. I found that deleting the nic in Yast, closing the NIC YaST component and then going back into it, and installing a new nic (actually the old one) worked. One other thing comes to mind here. Are you sure of your cables and other hardware? swap ports on your router, and switch cables from the box that works to the box that doesn't work. Does the box that works still work?

...
My thanx to those who have answered so far, and any other suggestions would be appreciated. Just please remember that I am not all that familiar--I'm not much familiar at all--with Linux/Unix.

This Linux machine, BTW, is going thru the same router.

Mike Mike, when the nic signs off on it's own and a yast reconfig is needeed, there is a

On Sunday 23 October 2005 11:52 pm, Mike McMullin wrote: problem. It could be hardware or software. Since The hardware works great when suse 9.1, 9.2, 9.3 is selected in the boot loader (at least in my system), but fails in suse 10.0 /10.1, i would put my money on a software problem. The possiblity of "dropped support" for an old card should not exist, my system is a 64 bit athlon, every component mature at around 1-1/2 years old. d.

Doug McGarrett

25 Oct 25 Oct

00:06

New subject: [SLE] 10.0: no net, now what, cont'd

...

Mike Mullin wrote: /snip/

...

You shouldn't have to re-install. I've had some problems with nic's under 9.1. They'd work and then they wouldn't find the network. I found that deleting the nic in Yast, closing the NIC YaST component and then going back into it, and installing a new nic (actually the old one) worked. One other thing comes to mind here. Are you sure of your cables and other hardware? swap ports on your router, and switch cables from the box that works to the box that doesn't work. Does the box that works still work?

...

Mike

I'll give that a try. It's very frustrating to spend several days trying to get something to work, that used to. I get the feeling that the new kernel doesn't like (or doesn't have) the driver that used to work. --doug -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.361 / Virus Database: 267.12.5/147 - Release Date: 10/24/2005

suse_gasjr4wd＠mac.com

01:13

New subject: [SLE] 10.0: no net, now what, cont'd

On 10/24/05 8:06 PM, "Doug McGarrett" wrote:

...

...
Mike Mullin wrote:

/snip/

...
You shouldn't have to re-install. I've had some problems with nic's under 9.1. They'd work and then they wouldn't find the network. I found that deleting the nic in Yast, closing the NIC YaST component and then going back into it, and installing a new nic (actually the old one) worked. One other thing comes to mind here. Are you sure of your cables and other hardware? swap ports on your router, and switch cables from the box that works to the box that doesn't work. Does the box that works still work?

...
Mike

I'll give that a try. It's very frustrating to spend several days trying to get something to work, that used to. I get the feeling that the new kernel doesn't like (or doesn't have) the driver that used to work.

--doug

I just had to change it from grabbing a IP via our DHCP to static, save...then back to get it to work. This is on a fresh install. Maybe try that...it's a few seconds faster than deleting and adding new. -- Thanks, George "INTEL INSIDE" It's not a marketing gimmick, it's a warning label.

Mike McMullin

21:14

New subject: [SLE] 10.0: no net, now what, cont'd

On Mon, 2005-10-24 at 20:06 -0400, Doug McGarrett wrote:

...

...
Mike Mullin wrote:

/snip/

...
You shouldn't have to re-install. I've had some problems with nic's under 9.1. They'd work and then they wouldn't find the network. I found that deleting the nic in Yast, closing the NIC YaST component and then going back into it, and installing a new nic (actually the old one) worked. One other thing comes to mind here. Are you sure of your cables and other hardware? swap ports on your router, and switch cables from the box that works to the box that doesn't work. Does the box that works still work?

...
Mike

I'll give that a try. It's very frustrating to spend several days trying to get something to work, that used to. I get the feeling that the new kernel doesn't like (or doesn't have) the driver that used to work.

Sometimes it's as simple as a configuration issue, other times it's hardware related. I spent a whole weekend doing exactly what your going through with her system only to find out that I needed to fix the cable connection in her room. Learned something form that one, sometimes it is hardware. Working from a known good helps big time. Mike

Stephen Boddy

22 Oct 22 Oct

19:31

New subject: [SLE] 10.0: no net, now what

On Saturday 22 October 2005 18:35, HG wrote:

...

I more or less (what do you mean by multiple profiles) did the same.

Multiple profiles: see YaST -> System -> Profile manager. it lets you have different configurations for different environments, without having to change your configuration manually each time. The systray applet will let you switch profiles on the fly. Very very useful for laptops, and probably of help to you. -- Steve Boddy

Doug McGarrett

23 Oct 23 Oct

02:59

New subject: [SLE] 10.0: no net, now what--partial solution

/snip

...

Multiple profiles: see YaST -> System -> Profile manager. it lets you have different configurations for different environments, without having to change your configuration manually each time.

/snip/ Well, it helps if you hook it up right. I had the router misconnected. I still don't have SuSE 10 connected to the net, but I do have my Linspire machine connected, and Windows, which could not access the router, altho it could communicate thru it, now does. I may have loused up SuSE 10, so I'll reinstall it tomorrow, and then we'll see. I was very disappointed with YaST. It's got the worst of the old Borland interface, and half the stuff didn't work at all. AAMOF, it hung completely, and I had to exit the window to get out of it. Is there a graphical installer? --doug -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.4/146 - Release Date: 10/21/2005

Stephen Boddy

03:52

New subject: [SLE] 10.0: no net, now what--partial solution

On Sunday 23 October 2005 03:59, Doug McGarrett wrote:

...

/snip

...
Multiple profiles: see YaST -> System -> Profile manager. it lets you have different configurations for different environments, without having to

change

...
your configuration manually each time.

/snip/

Well, it helps if you hook it up right. I had the router misconnected. I still don't have SuSE 10 connected to the net, but I do have my Linspire machine connected, and Windows, which could not access the router, altho it could communicate thru it, now does. I may have loused up SuSE 10, so I'll reinstall it tomorrow, and then we'll see.

Without sitting in front of your machine it is tricky to troubleshoot. Frankly there is no way in hell you should have to reinstall. I suspect you just haven't understood what it is that needs to be done.

...

I was very disappointed with YaST. It's got the worst of the old Borland interface, and half the stuff didn't work at all. AAMOF, it hung completely, and I had to exit the window to get out of it.

Strange, I find YaST to be excellent. One of the reasons I use SuSE.

...

Is there a graphical installer?

errr... YaST!?! Exactly what do you mean by installer? The OS, additional software, network adapters? All handled by YaST. -- Steve Boddy

Sid Boyce

04:13

New subject: [SLE] 10.0: no net, now what--partial solution

Doug McGarrett wrote:

...

/snip

...
Multiple profiles: see YaST -> System -> Profile manager. it lets you have different configurations for different environments, without having to change your configuration manually each time.

/snip/

Well, it helps if you hook it up right. I had the router misconnected. I still don't have SuSE 10 connected to the net, but I do have my Linspire machine connected, and Windows, which could not access the router, altho it could communicate thru it, now does. I may have loused up SuSE 10, so I'll reinstall it tomorrow, and then we'll see.

Seems likely as yast shouldn't hang, it almost suggests that it was never used during install, it starts up to let you configure your system.

...

I was very disappointed with YaST. It's got the worst of the old Borland interface, and half the stuff didn't work at all. AAMOF, it hung completely, and I had to exit the window to get out of it. Is there a graphical installer?

--doug

In VC mode yast is like what I remember of Borland C, in X, yast is graphical and is as good and probably better than most any configurator on any OS. Unless I missed it, I haven't seen the output of "ifconfig" or "lsmod" plus details of what card you have - "lspci" and anything relating to dhcpd leases in /var/log/messages. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks

6762

Age (days ago)

6765

Last active (days ago)

List overview

Download

26 comments

11 participants

participants (11)

Anders Johansson
Doug McGarrett
Graham Smith
HG
Jerry Feldman
kanenas
Ken Schneider
Mike McMullin
Sid Boyce
Stephen Boddy
suse_gasjr4wd＠mac.com