I’ve been away for a while since the 9.1 suse release. After all this time, I was expecting to see a finalized, polished release with most issues fixed. But I see the same old problems and a lot of new ones.
Anyway. I recently did a fresh install of opensuse 12.2. I configured my network with yast, including the default gateway and DNS servers, but the routing table comes after each boot like this:
->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.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
This is not going to work! I have since disabled 169.254.0.0 from /etc/sysconfig/network/scripts/ifup-route. Additionaly /etc/resolv.conf is empty despite having defined static nameservers in /etc/sysconfig/network/config. The default gateway is specified in:
Running netconfig as root, doesn’t do anything. What should I do to keep my network intact across boots? I should also mention that NetworkManager fails to start:
-> systemctl status dbus-org.freedesktop.NetworkManager.service
dbus-org.freedesktop.NetworkManager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
On 2013-03-09 03:06, nbal wrote:
>
> I’ve been away for a while since the 9.1 suse release. After all this
> time, I was expecting to see a finalized, polished release with most
> issues fixed. But I see the same old problems and a lot of new ones.
There is a network subforum where you should have posted this. Please
ask a moderator to move this thread.
Further to this, please use code tags to post such things as command
outputs. Advanced editor, ‘#’ button.
[ View this
thread for instructio
You mention using YaST, then Network manager. One or the other, choose.
On 03/08/2013 08:06 PM, nbal wrote:
>
> I’ve been away for a while since the 9.1 suse release. After all this
> time, I was expecting to see a finalized, polished release with most
> issues fixed. But I see the same old problems and a lot of new ones.
>
> Anyway. I recently did a fresh install of opensuse 12.2. I configured
> my network with yast, including the default gateway and DNS servers, but
> the routing table comes after each boot like this:
>
> ->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.1.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
>
> This is not going to work! I have since disabled 169.254.0.0 from
> /etc/sysconfig/network/scripts/ifup-route. Additionaly /etc/resolv.conf
> is empty despite having defined static nameservers in
> /etc/sysconfig/network/config. The default gateway is specified in:
>
> -> cat /etc/sysconfig/network/routes
> default 192.168.1.254 - -eth0
>
> Running netconfig as root, doesn’t do anything. What should I do to
> keep my network intact across boots? I should also mention that
> NetworkManager fails to start:
>
> -> systemctl | grep NetworkManager
> NetworkManager.service loaded failed failed Network Manager
>
> -> systemctl status dbus-org.freedesktop.NetworkManager.service
> dbus-org.freedesktop.NetworkManager.service
> Loaded: error (Reason: No such file or directory)
> Active: inactive (dead)
Did you upgrade after doing the installation? The 12.2 installation media have
bugs in the routing code that were fixed.
On 3/8/2013 8:35 PM, Larry Finger wrote:
> On 03/08/2013 08:06 PM, nbal wrote:
>>
>> I’ve been away for a while since the 9.1 suse release. After all this
>> time, I was expecting to see a finalized, polished release with most
>> issues fixed. But I see the same old problems and a lot of new ones.
>>
>> Anyway. I recently did a fresh install of opensuse 12.2. I configured
>> my network with yast, including the default gateway and DNS servers, but
>> the routing table comes after each boot like this:
>>
>> ->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.1.0 0.0.0.0 255.255.255.0 U 0 0
>> 0 eth0
>>
>> This is not going to work! I have since disabled 169.254.0.0 from
>> /etc/sysconfig/network/scripts/ifup-route. Additionaly /etc/resolv.conf
>> is empty despite having defined static nameservers in
>> /etc/sysconfig/network/config. The default gateway is specified in:
>>
>> -> cat /etc/sysconfig/network/routes
>> default 192.168.1.254 - -eth0
<snip>
>
> Did you upgrade after doing the installation? The 12.2 installation media have
> bugs in the routing code that were fixed.
>
>
Nikos;
Yes, I am aware of that. It is used for DHCP, which i don’t use. The rule is worthless in my case, since I am on a different subnet and all traffic outside it is handled by the default router. Sorry, but i don’t like software configuring my installation against my wishes. That’s Microsoft territory
I am sure I did some upgrades. Each time i would start my default gateway, it would prompt me for new available upgrades. I didn’t try to yast since, since all desired changes are already in network/config. However, when I boot the same problems exist.
[QUOTE=robin_listas;2533153]On 2013-03-09 03:06, nbal wrote:
>
>> I’ve been away for a while since the 9.1 suse release. After all this
>> time, I was expecting to see a finalized, polished release with most
>> issues fixed. But I see the same old problems and a lot of new ones.
>There is a network subforum where you should have posted this. Please
> ask a moderator to move this thread.
Sure. How can i get in touch with a moderator?
> Further to this, please use code tags to post such things as command
> outputs. Advanced editor, ‘#’ button.
> [
On 2013-03-09 07:06, nbal wrote:
>>> > > You mention using YaST, then Network manager. One or the other,
>> > choose.
>> >
> Well, if the one doesn’t work, you try the other.
It doesn’t work that way. You have to disable one to use the other.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
On 2013-03-09 06:46, nbal wrote:
> Yes, I am aware of that. It is used for DHCP, which i don’t use. The
> rule is worthless in my case, since I am on a different subnet and all
> traffic outside it is handled by the default router. Sorry, but i don’t
> like software configuring my installation against my wishes. That’s
> Microsoft territory
Please no comparisons with Microsoft here.
A Link-Local address is automatically used when you configured for DHCP
and no DHCP server is found.
Please show us displays of how you configured YaST - assuming you are
still using YaST, ie, ifup. It can be done in text mode for pasting here.
And please, ask a moderator to move this thread. Use the report button.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
If your box is not going to be moving from one network to another the
choice of using Yast to configure networking was the right one. If,
though, this is a laptop or something that will be roaming from one
network to another then using Network Manager is the right option. You
choose which one is used within Yast, but if you choose the Network
Manager option then Yast basically lets you set that and then you’re
done… no more settings; Yast defers everything else t Network Manager.
In your case, let’s assume the static settings are correct. As others
have mentioned, let us know everything you filled in. Your initial
description posts some output from the old ‘route’ command, so let’s use
newer commands and get everything we can about your system:
Code:
ip -s link
ip addr
ip route
grep -v ‘^#’ /etc/resolv.conf
Post the output from those commands and let’s go from there. Again, if
unsure about any changes you’ve made when trying this, go into Yast and
reset everything for the static (not Network Manager) mode. For the
record, you can use Network Manager even on a static machine, but it loads
(I am pretty sure) during a user login, so networking won’t be fully setup
until that time, where the static ifup/Yast method will set everything
during boot regardless of whether or not somebody logs into the GUI and
loads Network Manager. I doubt that is your problem, but it may be
unexpected for newer users.
@robin_listas:
>A Link-Local address is automatically used when you configured for DHCP
>and no DHCP server is found.
I never configured for DHCP. Installation did this automatically and I changed that to static when I got it up.
No matter, when I configured yast with static addresses, it should have removed the route.
>Please show us displays of how you configured YaST - assuming you are
>still using YaST, ie, ifup. It can be done in text mode for pasting here.
@ab:
> If your box is not going to be moving from one network to another the
> choice of using Yast to configure networking was the right one. If,
> though, this is a laptop or something that will be roaming from one
> network to another then using Network Manager is the right option. You
> choose which one is used within Yast, but if you choose the Network
> Manager option then Yast basically lets you set that and then you’re
> done… no more settings; Yast defers everything else t Network Manager.
Yeap. I am using a desktop with everything fixed. Besides, it’s not like I have a choice, NetwrokManager won’t start, and i have seen some Bug reports, saying that this is a bug in 12.2.
> In your case, let’s assume the static settings are correct. As others
> have mentioned, let us know everything you filled in. Your initial
> description posts some output from the old ‘route’ command, so let’s use
> newer commands and get everything we can about your system:
I am not sure what you expect to get from these. Clearly I had to fix DNS and routing tables by hand to have access to this forum.
I can also put the default route in root’s .bashrc, but this is not the right way to do it. I also sent in my Yast output in my previous mail.
DrWho:~# ip -s link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
10375 71 0 0 0 0
TX: bytes packets errors dropped carrier collsns
10375 71 0 0 0 0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 00:25:22:18:91:81 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
5514821 35907 0 0 0 0
TX: bytes packets errors dropped carrier collsns
1333828 4713 0 0 0 0
DrWho:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:25:22:18:91:81 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0
inet6 fe80::225:22ff:fe18:9181/64 scope link
valid_lft forever preferred_lft forever
DrWho:~# ip route
default via 192.168.1.254 dev eth0
127.0.0.0/8 dev lo scope link
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1
DrWho:~# grep -v '^#' /etc/resolv.conf
nameserver 194.219.227.2
nameserver 193.92.159.3
>> Please show us displays of how you configured YaST - assuming you are
>> still using YaST, ie, ifup. It can be done in text mode for pasting
> here.
>
> Here you go:
>
>
Ok, with the above you will not have network manager.
At the overview tab, you have to enter “edit” on your card. You will see
something like this, which I do not see on your post:
> Network Card Setup
> ┌General──Address──Hardware──────────────────────────────────────────────────────┐
> │ Device Type Configuration Name │
> │ Wireless▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒↓ wlan0▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │
> │( ) No IP Address (for Bonding Devices) │
> │( ) Dynamic Address DHCP▒▒▒▒▒▒▒▒▒▒↓ DHCP both version 4 and 6▒↓ │
> │(x) Statically assigned IP Address │
> │IP Address Subnet Mask Hostname │
> │192.168.1.3▒▒▒▒▒▒▒▒▒▒▒ /24▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ <nas-tirith.valinor▒ │
> │┌Additional Addresses──────────────────────────────────────────────────────────┐│
> ││ ┌──────────────────────────────────────────────────────────────────────┐ ││
Notice the “Statically assigned IP Address” part.
A word of warning: if you try to edit some of the network configuration
files directly, it may be that YaST aborts the network configuration.
This is intentional and not new.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Tha’s fine. I don’t need that line. This is just my desktop PC with a DSL router. I don’t have any other hosts in my domain, which is BTW non-resolvable. Besides, resolv.conf was edited by hand and works fine. My question is why it was not fixed by Yast (see my Yast configuration) and I had to do it by hand. AFAIK resolv.conf doesn’t show in ifconfig.
On 2013-03-10 04:06, nbal wrote:
> Besides, resolv.conf was edited by hand and works fine.
> My question is why it was not fixed by Yast (see my Yast configuration)
Because once you edit resolv.conf by hand YaST refuses to touch it.
Documented.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
As mentioned in my previous mail, I did whatever I had to do to get Internet and find some help.:shame:
I did edit resolv.conf but only after repeated failures by Yast and netconfig to write anything
into resolv.conf. But now that you mention it, since I’ve gotten a few upgrades since,
I will stop my network remove/edit my resolv.conf and let Yast at it again.
Right now, my main concern is to get the default gateway going at boot time. I can edit the init scripts
by hand, but I’d rather know if I have a configuration problem beforehand. Like before, I did update my
routing tables by hand, so Yast might object to touching them. But just a minute! Routing tables live in kernel
space, and Yast is in user space, so it doesn’t know!
