• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1164
  • Last Modified:

SuSE9.1 Networking problem

Last 8 years working with linux I was never stumped by a networking problem.
I can confirm that
a) The laptop is working and network cards all ok.
I boot with Dynabolic and I can configure the network and telnet or ssh to my servers.
b) The SuSE distribution is a purchased version.

So, when I installed SuSE and configure network strange things happen.

I ping a machine on my network (actually my gateway itself) and then after 16 seconds, I start getting ping responses, but the first one was 2seconds then 1 second then 0.1 seconds...exactly for 7 pings...
Then it goes dead for about 35 seconds.
Then it pings again for 7 pings as above.

The routing table looks like novell has changed a lot of stuff. My default is there but my interface itself with host IP is not there etc etc.

Anyone can help me out of this tight spot.

Please dont answer I need to check the hardware. The exact setup works with dynabolic SuSE8.0, Redhat Fedora2 etc etc without the mess as described above.
0
dryzone
Asked:
dryzone
  • 16
  • 11
  • 2
1 Solution
 
wesly_chenCommented:
> The routing table looks like novell has changed a lot of stuff
Could you post your routing table?
# netstat -rn

Also please post
# ifconfig eth0
# ethtool eth0
error messages in /var/log/messages

Sometimes, the auto-negotiation of switch port cause the packet delay and drop.
You might want to force the switch port to full duplex as well as your NIC port (eth0)
# ethtool -s speed 1000 duplex full autoneg off

Regards,

Wesly
0
 
dryzoneAuthor Commented:
Here follows.


A20:~ # ifconfig eth0


eth0      Link encap:Ethernet  HWaddr 00:04:AC:90:31:6E  
          inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::204:acff:fe90:316e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1184 errors:0 dropped:15 overruns:0 frame:0
          TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:168980 (165.0 Kb)  TX bytes:8718 (8.5 Kb)
          Interrupt:11 Base address:0x4000

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:2939 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2939 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:192891 (188.3 Kb)  TX bytes:192891 (188.3 Kb)

A20:~ # ethtool eth0
Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half
                                100baseT/Half
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
A20:~ #



A20:~ # cat /var/log/messages |grep eth0

Apr  7 20:38:31 A20 kernel: eth0: no IPv6 routers present
Apr  8 04:38:55 A20 kernel: eth0: Xircom Cardbus Adapter rev 3 at 0x4000, 00:04:AC:90:31:6E, IRQ 11.
Apr  8 04:38:55 A20 kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
Apr  8 04:38:55 A20 kernel: eth0: Link is up, running at 100Mbit half-duplex
Apr  8 04:39:04 A20 kernel: eth0: no IPv6 routers present



0
 
dryzoneAuthor Commented:
I have a deadline with this by this evening therefore I up the points.
 
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
dryzoneAuthor Commented:
Please note the stupid SUSE YAst config runs my network card as HALF DUPLEX.
Why on earth would any distribution want to do that?

Please inform me where I can set it to full duplex.
My router is autonmegotiating but 100baseT FULL duplex.

This could be the problem.
SuSE is a real pain, but my wife unfortunately likes the doze-like interface.
0
 
dryzoneAuthor Commented:
I tried speed 100 but also 1000 as you specified

The problem remains the same.
Below is an example of what happens.


--- gateway ping statistics ---
9 packets transmitted, 0 received, +7 errors, 100% packet loss, time 8000ms
, pipe 3
A20:~ # ethtool -s eth0 speed 1000 autoneg off duplex full
A20:~ # ping gateway
PING gateway (192.168.1.254) 56(84) bytes of data.
From A20 (192.168.1.9): icmp_seq=2 Destination Host Unreachable
From A20 (192.168.1.9) icmp_seq=2 Destination Host Unreachable
From A20 (192.168.1.9) icmp_seq=3 Destination Host Unreachable
From A20 (192.168.1.9) icmp_seq=4 Destination Host Unreachable
64 bytes from gateway (192.168.1.254): icmp_seq=5 ttl=64 time=2000 ms
64 bytes from gateway (192.168.1.254): icmp_seq=30 ttl=64 time=1998 ms
64 bytes from gateway (192.168.1.254): icmp_seq=8 ttl=64 time=23994 ms
64 bytes from gateway (192.168.1.254): icmp_seq=9 ttl=64 time=22994 ms
64 bytes from gateway (192.168.1.254): icmp_seq=10 ttl=64 time=21995 ms
64 bytes from gateway (192.168.1.254): icmp_seq=11 ttl=64 time=20995 ms
64 bytes from gateway (192.168.1.254): icmp_seq=12 ttl=64 time=19995 ms
64 bytes from gateway (192.168.1.254): icmp_seq=13 ttl=64 time=18995 ms
64 bytes from gateway (192.168.1.254): icmp_seq=14 ttl=64 time=17995 ms
64 bytes from gateway (192.168.1.254): icmp_seq=15 ttl=64 time=16995 ms
64 bytes from gateway (192.168.1.254): icmp_seq=16 ttl=64 time=15995 ms
64 bytes from gateway (192.168.1.254): icmp_seq=17 ttl=64 time=14996 ms

--- gateway ping statistics ---
34 packets transmitted, 12 received, +4 errors, 64% packet loss, time 33007ms
rtt min/avg/max/mdev = 1998.102/16579.468/23994.756/7027.639 ms, pipe 24
A20:~ #
0
 
dryzoneAuthor Commented:
And here is the routing table.
*254 is my gateway.

A20:~ #
A20:~ # netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0 eth0
A20:~ # emacs &
[2] 5714
0
 
dryzoneAuthor Commented:
IMPORTANT:
Just to confirm that I have untill 9pm this evening.
I will withdraw the question if no answer which solved till then or award partial points if it was helpful.
Since the points is the max allowed, I think the time-limit is also reasonable.

I think I presented all the details needed and would appreciate help.

thanks
0
 
wesly_chenCommented:
> ifconfig eth0
> RX packets:1184 errors:0 dropped:15 overruns:0 frame:0
There are aome packages drop on eth0.

> # ethtool -s speed 1000 duplex full autoneg off
Then
# ethtool -s speed 100 duplex full autoneg off
Don't use "speed 1000" if don't have Gigabit card and switch.
0
 
wesly_chenCommented:
Or edit your /etc/sysconfig/network-scripts/ifcfg-eth0
add this line:
ETHTOOL_OPTS="speed 1000 duplex full autoneg off"

Then
# /etc/init.d/network restart
and
ethtool eth0
to check the speed of eth0

That's autonegotiation cause the no-duplex. On the switch side, you can also set it to 100MB full duplex if that switch
is manageable.
0
 
dryzoneAuthor Commented:
I already done this as you request above.
Does not work problem remains.
it seemingly does not route properly.
Did you check my routing table?

0
 
wesly_chenCommented:
Your routing table looks ok to me.
Can you do
traceroute 192.168.1.254  
traceroute www.yahoo.com
to compare the response time.
0
 
dryzoneAuthor Commented:

From the same machine booting with a dynabolic cd, I get

[d:b] ~ #traceroute 192.168.1.254                                                                               12:59
traceroute to 192.168.1.254 (192.168.1.254), 30 hops max, 40 byte packets
 1  gateway (192.168.1.254)  0.292 ms  0.175 ms  0.129 ms
[d:b] ~ #  

Booting back into SuSE I get.
traceroute to 192.168.1.254 (192.168.1.254), 30 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  A20 (192.168.1.9)(H!)  2970.563 ms (H!)  2968.575 ms (H!)  2966.583 ms

Weird !!!
0
 
wesly_chenCommented:
Could you compare the difference between SuSE and Dynabolic CD in
lspci
lsmod
ethtool
ifconfig -a
0
 
rindiCommented:
Don't forget that SuSE installs the SuSEFirewall. Maybe that is causing your problem.
0
 
wesly_chenCommented:
Good pont rindi.
0
 
dryzoneAuthor Commented:
========================================================================================
With Dyne
========================================================================================

lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:03.0 Communication controller: Agere Systems (former Lucent Microelectronics) WinModem 56k (rev 01)
00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
02:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03)
05:00.0 Network controller: Texas Instruments ACX 100 22Mbps Wireless Interface


lsmod
Module                  Size  Used by    Not tainted
smbfs                  42160   0  (unused)
ppp_deflate             3320   0  (unused)
zlib_deflate           18360   0  [ppp_deflate]
ppp_async               9184   0  (unused)
ppp_generic            22304   0  [ppp_deflate ppp_async]
slhc                    5136   0  [ppp_generic]
snd-seq-oss            29728   0  (unused)
snd-seq-midi-event      3776   0  [snd-seq-oss]
snd-pcm-oss            39872   0
snd-mixer-oss          13752   0  [snd-pcm-oss]
snd-seq                43024   2  [snd-seq-oss snd-seq-midi-event]
keybdev                 1984   0  (unused)
mousedev                4632   0
hid                    23588   0  (unused)
snd-cs46xx             65252   0
snd-ac97-codec         51872   0  [snd-cs46xx]
snd-pcm                66880   0  [snd-pcm-oss snd-cs46xx snd-ac97-codec]
snd-timer              17060   0  [snd-seq snd-pcm]
gameport                1660   0  [snd-cs46xx]
snd-rawmidi            16032   0  [snd-cs46xx]
snd-seq-device          4264   0  [snd-seq-oss snd-seq snd-rawmidi]
snd                    37572   0  [snd-seq-oss snd-seq-midi-event snd-pcm-oss snd-mixer-oss snd-seq snd-cs46xx snd-ac97-codec snd-pcm snd-timer snd-rawmidi snd-seq-device]
soundcore               4100   8  [snd]
snd-page-alloc          5256   0  [snd-seq-oss snd-mixer-oss snd-seq snd-cs46xx snd-pcm snd-timer snd-rawmidi snd-seq-device snd]
ds                      7144   2
yenta_socket           10464   2
xircom_cb               5920   1
i82092                  6632   0  (unused)
pcmcia_core            44704   0  [ds yenta_socket i82092]
usb-storage           118064   0  (unused)
sd_mod                 11532   0  (unused)
usb-uhci               22732   0  (unused)
vfat                    9836   1
fat                    33720   0  [vfat]
loop-aes               49424   3

ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:04:AC:90:31:6E  
          inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1651 (1.6 Kb)  TX bytes:4384 (4.2 Kb)
          Interrupt:11 Base address:0x4000

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)




I added ping sio you can see that the same hardware has absolutely no problem getting to the gateway under Dyne.
ping -c10 192.168.1.254
PING 192.168.1.254 (192.168.1.254): 56 octets data
64 octets from 192.168.1.254: icmp_seq=0 ttl=64 time=4.3 ms
64 octets from 192.168.1.254: icmp_seq=1 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=2 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=3 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=4 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=5 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=6 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=7 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=8 ttl=64 time=0.1 ms
64 octets from 192.168.1.254: icmp_seq=9 ttl=64 time=0.1 ms

--- 192.168.1.254 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.5/4.3 ms

========================================================================================
WITH SUSE9.1
========================================================================================
A20:~ # lspci
0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
0000:00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
0000:00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
0000:00:03.0 Communication controller: Agere Systems (former Lucent Microelectronics) WinModem 56k (rev 01)
0000:00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
0000:00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
0000:02:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03)
0000:06:00.0 Network controller: Texas Instruments ACX 100 22Mbps Wireless Interface
A20:~ #


Module                  Size  Used by
usbserial              26856  0
parport_pc             37824  1
lp                     10536  0
parport                37960  2 parport_pc,lp
nvram                   8328  0
speedstep_lib           4228  0
freq_table              4356  0
processor              25640  0
edd                    10012  0
snd_pcm_oss            57896  0
snd_mixer_oss          19200  3 snd_pcm_oss
snd_seq_midi            9504  0
snd_seq_midi_event      7424  1 snd_seq_midi
snd_seq                53008  2 snd_seq_midi,snd_seq_midi_event
snd_cs46xx             87880  5
snd_rawmidi            24356  2 snd_seq_midi,snd_cs46xx
snd_seq_device          8716  3 snd_seq_midi,snd_seq,snd_rawmidi
snd_ac97_codec         69728  1 snd_cs46xx
snd_pcm                96776  4 snd_pcm_oss,snd_cs46xx,snd_ac97_codec
snd_timer              24708  2 snd_seq,snd_pcm
snd                    60164  16 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_seq_midi_event,snd_seq,snd_cs46xx,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer
soundcore               9056  3 snd
snd_page_alloc         10248  2 snd_cs46xx,snd_pcm
gameport                4608  1 snd_cs46xx
ipv6                  237312  13
joydev                  9664  0
sg                     35872  0
st                     37404  0
sd_mod                 16912  0
sr_mod                 16292  0
scsi_mod              111308  4 sg,st,sd_mod,sr_mod
ide_cd                 38176  0
cdrom                  36508  2 sr_mod,ide_cd
acx_pci               145792  0
ds                     17796  4
uhci_hcd               29712  0
binfmt_misc            11272  1
intel_agp              21024  1
agpgart                32168  1 intel_agp
xircom_tulip_cb        18096  0
yenta_socket           19840  2
pcmcia_core            66100  2 ds,yenta_socket
subfs                   7552  2
nls_utf8                2176  1
nls_cp437               5888  1
vfat                   13056  1
fat                    43168  1 vfat
evdev                   8960  0
dm_mod                 54524  0
usbcore               106724  4 usbserial,uhci_hcd
reiserfs              242000  1


A20:~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:04:AC:90:31:6E  
          inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::204:acff:fe90:316e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:64 errors:0 dropped:1 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10898 (10.6 Kb)  TX bytes:460 (460.0 b)
          Interrupt:11 Base address:0x4000

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:3872 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3872 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:252424 (246.5 Kb)  TX bytes:252424 (246.5 Kb)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  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:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

A20:~ #




0
 
dryzoneAuthor Commented:
To Rindi.

Requesting STATUS of the firewall by running the firewall setup daemon in /etc/rc.d, returns the message UNUSED.
That is therefore not the problem.
I also checked for ipchains and tables-- not even installed it seems as locate could not find them neither could I flush chains with
ipchains -F as it is nowhere in any binary directory bin or sbin included or etc or X11.



0
 
wesly_chenCommented:
1.
> Dyne (lsmod)
> xircom_cb               5920   1

> SUSE9.1 (lsmod)
> xircom_tulip_cb        18096  0

The load the different driver for Xircom Cardbus Ethernet 10/100.

2.
> SuSE 9.1 (ifconfig -a)
>    inet6 addr: fe80::204:acff:fe90:316e/64 Scope:Link
The SuSE load the ipv6. Could you turn off ipv6 on YaST? Sometimes ipv6 enable cause the problem

3. What's the output of ethtool on Dyne?
0
 
rindiCommented:
I think the SuSE firewall uses something other than iptables. And look for something like SuSEfirewall...
0
 
dryzoneAuthor Commented:
I did as I mentioned and actually removed all the firewal programs. It cannot even be started!
0
 
dryzoneAuthor Commented:
Wesley

Dyne has no Ethtool and I will have to install.
In the mean time I will see if I cannot insmod the other Xircom driver
BTW, there was nowhere in Yast to switch off IPV6, I reverted to textfiles which in the end always gets the configuration problems sorted out. These fancy GUI's js just another layer of error.  



I took your advice and IPV6 was set to OFF in /etc/system/config/network.

I then restarted the network as
/etc/rc.d/network restart ans I got the following mess!!!
There is definatley a routing problem here.
I think if we resolve this one then it is going to work.

Nothing to flush.                                                    done
Shutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  . done.
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8  
Device "lo" does not exist.                                          done
    eth0      device: Xircom Cardbus Ethernet 10/100 (rev 03)
    eth0      configuration: eth-id-00:04:ac:90:31:6e
    eth0      IP address: 192.168.1.9/24  
    eth0      Error while excuting:
              Command 'ip route replace to 192.168.1.9/24 via 192.168.1.254 dev eth0' returned:
              RTNETLINK answers: Invalid argument
              Configuration line: 192.168.1.9 192.168.1.254 255.255.255.0 eth-id-00:04:ac:90:31:6e
Nothing to flush.                                                    done
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  . done.
A20:/etc/sysconfig/network # emacs &
[3] 7314
A20:/etc/sysconfig/network #
0
 
dryzoneAuthor Commented:
There is seemingly a loopback problem and also routing problem.
That's a mess.
Believe it or not that is how SuSE ships!
I did not fiddle with the loopback at all.!
0
 
wesly_chenCommented:
Could you post
/etc/system/config/network
0
 
dryzoneAuthor Commented:
Its getting curiouser and curiouser as Alice would say.

Networks is not as where it is in Redhat ...correctly in sysconfig, but in suse it is in /etc.../beats me why.

In any case, seams it is muisconfigured.  What the heck is link-local? and why this IP?
I really wish I am back at Slack or RedHat.

#
# networks      This file describes a number of netname-to-address
#            mappings for the TCP/IP subsystem.  It is mostly
#            used at boot time, when no name servers are running.
#

loopback      127.0.0.0
link-local      169.254.0.0

# End.


Also I attach the "routes"    file in /etc/sys..../
#cat  routes_bup                                                                                  
192.168.1.9 192.168.1.254 255.255.255.0 eth-id-00:04:ac:90:31:6e
default 192.168.1.254 - -



0
 
wesly_chenCommented:
I don't have SuSE on hand at this moment.
I know you can comment out
# link-local     169.254.0.0
for sure.
0
 
dryzoneAuthor Commented:
Already did does not help.

I think your remark about the different driver has some merrit. Did you see the size of the SuSE driver?

As this did not resolve I will split points to you as you made one heck of an effort, but it is to me clear that there is something pretty bad going on .

Would you be happy with a 250 point allocation for the effort?
0
 
wesly_chenCommented:
I don't mind the points.
What I care more about the root cause.
IPv6 is one possibility.
Driver is another one.
Routing ? Could you just do
route del -net 169.254.0.0/16
To see if this help....
0
 
dryzoneAuthor Commented:
Hi wesly, no way to split, so I gave you the points.
Thanks for the help.
I am convinced it is a broken driver..
I went and dug up an old wireless card and that worked, but Xircom (which was trusty on all linux distros) just is broken on SuSe9.1 it seems.

Worse is, now that I haev a network connection with a wireless card, there seems to be X-access problems too.
I can xhost +  all the hosts on the SuSe box and then ssh in to a server, but I cannot open X-applications.
Xtlib balks that it cannot open the display on the SuSe box.

So speaking to you I ended up with some sort of solution but SuSE just keep coming with surprises.

I dont know... this SuSE9.1 is just a plain nightmare.  
0
 
wesly_chenCommented:
> then ssh in to a server, but I cannot open X-applications.
ssh -X <remote host>
so it do X forwarding.

My experience with SuSE is not that bad. Only thing I got into trouble is the modem card which made my network card
fail. After pulled it out (someday this idea just came out my mind) and everything went smoothly.

You have built-in modem, right?

The latest verion of SuSE is 9.2 and my friends and a lot of people love it very much. You might want to try that version.
Some people have problem with SuSE 9.1 since it is the first version of SuSE using kernel 2.6.x.
There is a lot of bugs on it (of course, a lot of patches for them)....
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 16
  • 11
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now