no connection at all with new install of 12.2

Have tried about a dozen suggestions from this forum (turn off IPv6, etc). No joy.


ping 192.168.1.1
connect: Network is unreachable

and


/sbin/route -n
(displays only loopback information)

Sorry for not cutting and pasting, but I’m using a Windows laptop physically connected to the same network to submit this.

Are we talking wired or wireless?

/sbin/lspci -nnk | grep -iA2 net

On 12/29/2012 11:56 PM, jburgeson wrote:
>
> Have tried about a dozen suggestions from this forum (turn off IPv6,
> etc). No joy.
>
> Code:
> --------------------
>
> ping 192.168.1.1
> connect: Network is unreachable
>
> --------------------
>
> and
>
> Code:
> --------------------
>
> /sbin/route -n
> (displays only loopback information)
>
> --------------------
>
> Sorry for not cutting and pasting, but I’m using a Windows laptop
> physically connected to the same network to submit this.
>
>
jburgeson;

There is not much to go on here. Is your connection wired or wireless? Are you
using network manager or traditional ifup? Is your network card recognized by
YaST? Are you using dhcp or a static configuration? Do you have an IP? Check
ifconfig for an IP.


/sbin/ifconfig -a


P.V.
“We’re all in this together, I’m pulling for you” Red Green

Wired
traditional ifup
not sure how to answer whether the network card is recognized by YaST, but I see this in the Overview tab of YaST2’s Network Settings.
191 Gigabit Ethernet Adapter
MAC : 00:1b:fc:f2:1f:18
BusID : 0000:00:04.0

  • Device Name: eth0
  • Started automatically at boot
  • IP address assigned using DHCP

DHCP


/sbin/ifconfig -a
eth0  Link encap:Ethernet  HWaddr 00:1B:FC:F2:1F:18
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:406 errors:0 dropped:0 overruns:0 frame:0
         TX packets:843 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:29814 (29.1 Kb)  TX bytes:288306 (281.5 KB)
         Interrupt:19 Base address:0xdead

lo      Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:363 errors:0 dropped:0 overruns:0 frame:0
         TX packets:363 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:56730 (55.4 Kb)  TX bytes:56730 (55.4 Kb)


00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] 191 Gigabit
 Ethernet Adapter [1039:0191] (rev 02)
         Subsystem: ASUSTeK Computer Inc. Device [1043:825e]
         Kernel driver in use: sis190

On 12/30/2012 1:16 AM, jburgeson wrote:
>
> venzkep;2514339 Wrote:

>> Is your connection wired or wireless?
>> Are you using network manager or traditional ifup?
>> Is your network card recognized by YaST?
>> Are you using dhcp or a static configuration?
>> Do you have an IP? Check ifconfig for an IP.
>>>
> Code:
> --------------------
> > >
> > /sbin/ifconfig -a
> >
> --------------------
>>>
>>
>>
>
> Wired
> traditional ifup
> not sure how to answer whether the network card is recognized by YaST,
> but I see this in the Overview tab of YaST2’s Network Settings.
> 191 Gigabit Ethernet Adapter
> MAC : 00:1b:fc:f2:1f:18
> BusID : 0000:00:04.0
> * Device Name: eth0
> * Started automatically at boot
> * IP address assigned using DHCP
>
> DHCP
>
> Code:
> --------------------
>
> /sbin/ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:1B:FC:F2:1F:18
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:406 errors:0 dropped:0 overruns:0 frame:0
> TX packets:843 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:29814 (29.1 Kb) TX bytes:288306 (281.5 KB)
> Interrupt:19 Base address:0xdead
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:363 errors:0 dropped:0 overruns:0 frame:0
> TX packets:363 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:56730 (55.4 Kb) TX bytes:56730 (55.4 Kb)
>
> --------------------
>
>
jburgeson;

dhcp is not giving you an address. Make sure all cables and switches are good.
Try setting up a static IP.

For an IP use 192.168.1.x where 1<x<254. Choose x outside the range of dhcp. If
you do not know the range and this a dual boot boot try the IP of Windows other
wise just try a value of x, say x=26.

For a mask use 255.255.255.0; for the gateway use 192.168.1.1 (the IP of your
router). For DNS use the Google public DNS servers 8.8.8.8 and 8.8.4.4.


P.V.
“We’re all in this together, I’m pulling for you” Red Green

PS: Not all routers have the address 192.168.1.1, so make sure that is the
correct address for your router.


P.V.
“We’re all in this together, I’m pulling for you” Red Green

jburgeson;

dhcp is not giving you an address. Make sure all cables and switches are good.
Try setting up a static IP.

For an IP use 192.168.1.x where 1<x<254. Choose x outside the range of dhcp. If
you do not know the range and this a dual boot boot try the IP of Windows other
wise just try a value of x, say x=26.

For a mask use 255.255.255.0; for the gateway use 192.168.1.1 (the IP of your
router). For DNS use the Google public DNS servers 8.8.8.8 and 8.8.4.4.


P.V.
“We’re all in this together, I’m pulling for you” Red Green[/QUOTE]

[HR][/HR]
All cables are fine. ISP requires dynamic IP. Tried static anyway and it didn’t work.
Tried the settings you suggested and that didn’t work.
Also used 192.168.2.1 for the gateway (since my router is a Belkin) and that didn’t work either.
Am willing to try most anything, but would need pretty clear/comprehensive instructions once all of these changes have been made.

[QUOTE=venzkep;2514369]PS: Not all routers have the address 192.168.1.1, so make sure that is the
correct address for your router.


route -n
Kernel IP routing table
Destination     Gateway        Genmask        Flags Metric Ref    Use Iface
127.0.0.0       0.0.0.0        255.0.0.0      U     0      0      0 lo
169.254.0.0     0.0.0.0        255.255.0.0    U     0      0      0 eth0
192.168.2.0     0.0.0.0        255.255.255.0  U     0      0      0 eth0

Thanks for your help. Keep the suggestions coming and I’ll try them.

Assuming you know the router is OK and connected to the internet

Open Yast > Network Settings
Select the wired network and just run thru the steps to OK it to completion.
Restart the PC.
(maybe you already did all that?)

It’s many many years ago since I had a wired connection not work out of the box, but SiS rings alarm bells whenever I hear it by name.

Guess a cheap D-Link PCI card would solve it, unless this is a laptop? With SiS it sounds like it could be?

The router works fine for the two other machines (wireless laptops) running XP and Windows 7. This wired PC that is not working is not a laptop. It had openSUSE 11.1 on it previously and that worked splendidly for years.

Would you give me more details on your instructions to “select the wired network and just run through the steps to OK it to completion”?

Network Settings > Overview Tab
Click to select eth0 > edit
In the next screen just click Next, no need to alter anything, just keep clicking thru the stages until it closes (ignore any errors)

Did that. No difference.:frowning:

You said it was working on an earlier version.
So it would be very odd for it to not work now.

If you have access to a Live CD of openSUSE or any new distro for that matter. Boot it. The network should be working out of the box in the live session.

Other than that I suggest a close inspection of your cables, unless for example, you can confirm that the same machine and cables are booting also to windows and it is fine??

I have double- and triple-checked the cables. That’s not the problem.

Using Windows it took me some time to download, verify, and burn a Live CD of openSUSE. The network doesn’t work for that live session either. “Networking Interface not connected” and “Connection Wired 1 connection failed”

Then I tried running Fedora-17-i686-Live-KDE and it has the same problem. “Failed to start Network Manager”

I am beginning to suspect that my ISP is doing something unusual. Of course they don’t support Linux on their help line. Do you have any suggestions for questions I could ask them (specific settings, for example) when I call them anyway?

"Connection Wired 1
Why 1?

It should be set to 0 as in eth0

I don’t know. That’s the message the Live CD gives me. The KDE Control Module for Network Connections shows none.

Try switching to Network Manager controlled in the Yast > Network Settings
Reboot

On 12/31/2012 08:16 AM, jburgeson wrote:
>
> caf4926;2514626 Wrote:
>> Why 1?
>>
>> It should be set to 0 as in eth0
>
> I don’t know. That’s the message the Live CD gives me. The KDE Control
> Module for Network Connections shows none.

As you are using ifup for this device, please post the contents of
/etc/sysconfig/network/ifcfg-eth0. That file is the one that will contain the
info needed for your device.

I would also like to see the output of ‘/sbin/lspci -nn | grep net’ so that we
can determine what driver is used by your device.

I changed the network setup method to Traditional with ifup. That let me use YaST2 to edit network settings. I also disabled IPv6, since I know my ISP does not support it. Then the connection showed as
“Ethernet Network Card DHCP eth0” but still didn’t work, so I rebooted with the installed version (not Live CD).

As you are using ifup for this device, please post the contents of
/etc/sysconfig/network/ifcfg-eth0. That file is the one that will contain the
info needed for your device.


BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.2.0/24'
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
PREFIXLEN='24'

I would also like to see the output of ‘/sbin/lspci -nn | grep net’ so that we
can determine what driver is used by your device.


00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter [1039:0191] (rev 02)