cancel
Showing results for 
Search instead for 
Did you mean: 

Installation problems with NW 2004s test-drive

Former Member
0 Kudos

Hi

I'm installing N4S testdrive on a Dell notebook under openSUSE 10.2 with wireless connection. I mention the wireless part because I suspect by wlan0 settings may have something to do with it, but then, I'm not sure and need some advice.

When first installed, I checked with startsap n4shost and stopsap n4shost, and all seemed fine. When rebooted, I got on startsap n4shost:

<i>Warning: Could not found virtuell host in ifconfig list</i>

OK, checked a few settings, and ammended network config to look like

inspiron:/ # cat /etc/sysconfig/network/ifcfg-eth-id-00:19:b9:57:a3:08
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='20'
IPADDR='192.168.155.1'
MTU=''
NAME='Dell BCM4401-B0 100Base-TX'
NETMASK='255.255.255.0'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='ifplugd'
UNIQUE='rBUF.HQwXbECfpC4'
USERCONTROL='no'
_nm_name='bus-pci-0000:08:00.0'

Then when I started/stopped, I got same cryptic message when trying to stop (yes, starting looked OK) and <i>Waiting for cleanup of resources</i> took a lot longer than I've experienced with NW4 under RH9.

So I think it might be my inexperience with setting up a non-fixed IP address for my WiFi connection, as I can start N4S when on-line (sometimes). Also <i>ping n4shost</i> fails. I feel I should get it to work first, but not sure where to start.

Hope some kind soul(s) can help.

Thanks

Phil

Message was edited by:

Philip Kisloff

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Philip,

can you pls. post the output of the

ifconfig

command?

Best regards,

Elmar.

philip_kisloff
Active Participant
0 Kudos

Hi Elmar

I've attached the output,

thanks Phil

inspiron:~ # ifconfig

eth0 Link encap:Ethernet HWaddr 00:19:B9:57:A3:08

UP BROADCAST MULTICAST MTU:1500 Metric:1

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

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

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Interrupt:217

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

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

collisions:0 txqueuelen:0

RX bytes:9949 (9.7 Kb) TX bytes:9949 (9.7 Kb)

wlan0 Link encap:Ethernet HWaddr 00:19:7D:A7:D6:6E

inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

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

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

collisions:0 txqueuelen:1000

RX bytes:415632 (405.8 Kb) TX bytes:202352 (197.6 Kb)

Interrupt:209 Memory:c0200000-c0204000

Former Member
0 Kudos

Hi Phil,

the install script should have set up a "fake" ip address, this is missing in your network configuration.

Please try

~n4sadm/S99_n4shost.sh start

and check if

ifconfig

then contains a device "eth0:1".

If not, please post the output of the script here.

Best regards,

Elmar.

philip_kisloff
Active Participant
0 Kudos

Hi Elmar

There was the file eth0:0 left in root directory.

BOOTPROTO='static'

IPADDR_0='192.168.155.1'

LABEL_0='eht0:0'

(going from memory here, as I don't have access to my laptop at the moment)

I didn't know how to incorporate it into network configuration. Is it as simple as just adding the file to /etc/sysconfig/network ?

Former Member
0 Kudos

Hi Philip,

the script S99_n4shost.sh (which should be linked to /etc/rc.d/rc3.d) should set up this device. eth0:0 should be available after booting, if not, run the script manually and post the results/error.

Without eth0:0, NW will not start.

Best regards,

Elmar.

Message was edited by:

Elmar Billen

philip_kisloff
Active Participant
0 Kudos

Hi Elmar

You're marvellous! When I ran <b>/etc/rc.d/rc3.d/S99n4shost start</b> I no longer the got the "virtuell" error message, eth0:0 was in ifconfig and could ping n4shost. But it never starts on boot. I'll investigate.

Thank you very much

Phil

Answers (0)