Networking issue in 12.3

English Network/Internet
1

I’ve probably missed something really obvious but it’s got me bluffed right now.

It worked up till a few weeks ago when I tried to set up thin clients on the wired network, so the wife could have a terminal in the kitchen. After I ran Kiwi-ltsp setup it all turned to custard. Thin client setup doesn’t work and now I can’t get the 12.3 machine onto the net.

Firstly WiFi works on both machine and mobile broadband router without any issues at all. I’m posting this from an 11.4 instance on the same machine and the two networks coexist happily, 10.1.x.x is the LAN and 192.x.x.x connects to the net, but when I boot 12.3 it refuses to go online.

Ping the router using ip address (http://192.168.10.50) and it connects to the router admin fine.
Do ifconfig and you get:

LTServer:/etc # ifconfig -abr0       Link encap:Ethernet  HWaddr 8E:C3:D7:ED:D7:B9  
          inet6 addr: fe80::8cc3:d7ff:feed:d7b9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:4724 (4.6 Kb)


eth0      Link encap:Ethernet  HWaddr BC:AE:C5:66:2F:F0  
          inet addr:10.1.1.3  Bcast:10.1.1.255  Mask:255.255.255.0
          inet6 addr: fe80::beae:c5ff:fe66:2ff0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:1 overruns:0 frame:0
          TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2677 (2.6 Kb)  TX bytes:23938 (23.3 Kb)


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:65536  Metric:1
          RX packets:142 errors:0 dropped:0 overruns:0 frame:0
          TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:12731 (12.4 Kb)  TX bytes:12731 (12.4 Kb)


wlan0     Link encap:Ethernet  HWaddr F4:EC:38:B9:60:9C  
          inet addr:192.168.10.189  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::f6ec:38ff:feb9:609c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1087 (1.0 Kb)  TX bytes:12211 (11.9 Kb)

I did some searching and read a post from Henk van Velden and checked a few things.

The thing that had me scratching my head was:

LTServer:/etc # netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.10.50   0.0.0.0         UG        0 0          0 wlan0
10.1.1.0        0.0.0.0         255.255.255.0   U         0 0          0 eth0
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.10.0    0.0.0.0         255.255.255.0   U         0 0          0 wlan0

I’ve no idea where 169.254.x.x has come from or for that matter how to remove it, that is of course assuming that it is a problem. Networking is not really my strong suit. Any help appreciated.

2

That’s a feature, not a bug. It is not a problem.

Here’s my “netstat -rn” output:


% netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.254.254 0.0.0.0         UG        0 0          0 eth0
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.254.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0

If you switch to NetworkManager, then the 169.254 line will probably go away, because NetworkManager hasn’t implemented support for that.

If your router ever fails, that 169.254 support is supposed to allow computers on your LAN to talk to one another.

3

Excellent, that puts that to rest. One thing I forgot to mention is that it won’t resolve name to ip address when pinging the router.

The url for the router is: my.zone - Informationen zum Thema my. which works in 11.4 but not 12.3, however in 12.3, http://192.168.10.50/index/html does work.

4

If it resolves other names, such as “forums.opensuse.org” then I would not worry about that.

You can actually add an entry for your router to “/etc/hosts” if you want to give it a name.

5

Nope, doesn’t resolve any names at all. I haven’t tried to ping an IP address out past the router, but my assumption was; given the 11.4 instance was working and getting out to the internet with the same hardware then the problem must be with a config file somewhere in the 12.3 installation.

6

Can you provide the output from:


ls -l /etc/resolv*
cat /etc/resolv.conf
7 
ltserver:/root12.3 # ls -l etc/resolv*
-rw-r--r-- 1 root root 793 Jul  9 08:54 etc/resolv.conf
-rw-r--r-- 1 root root 839 Jul  9 11:05 etc/resolv.conf.netconfig
-rw------- 1 root root   0 May  4 10:49 etc/resolv.conf.r4RKLH

and

ltserver:/root12.3 # cat etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file

I’m doing this from the 11.4 instance and I’ve mounted the 12.3 root partition at /root12.3 while I’m trying to figure this out

8

This /etc/resolv.conf does not show any DNS server entry. No wonder you can not resolve names.

Normaly when you use DHCP your DNS server is povided by the DHCP erver. If you configure your network yurself, you have to provide it yourself (can be done using YaST).

When you do not know which DNS server to use (the DHCP server most often gives his own address as such, or an address of your ISP) you can use 8.8.8.8 (sould be a very reliable and fast one provided by Google).

When you want to add this “manualy” ad the line

nameserver 8.8.8.8

atr the end of /etc/resolv.conf. When you, after testing, want to keep that solution, read the comment in /etc/resolv.conf about removing a certain line. The removing of that line will prevent a future DHCP use from overwriting what you just entered “manualy”.

9

Thanks for the output. I’ll add to what hcvv has said.

If you have manually configured the IP addresses, then you have to manually build “/etc/resolv.conf” yourself. If you are using DHCP, that information is usually provided automatically. In your case, it isn’t happening.

There’s a possibility that your connections will be router through eth0, and your wlan0 will only see other computers on your LAN. You may have to make some routing changes if that is not what you want.

10

8.8.8.8 didn’t work so I got DNS nameservers from my isp and put them in manually in yast and after a reboot we seem to be all working. Thanks for the help guys, much appreciated.

Cheers
Yo