[sles-beta] wicked problem
Marius Tomaschewski
mt at suse.de
Mon Mar 3 01:18:58 MST 2014
Am 28.02.2014 21:27, schrieb Günther J.Niederwimmer:
> Hello,
>
> is this a yast2 or a wicked problem?
I'd say in both. Please open 2 bug reports.
YaST2 does not allow to configure it per-interface [bug or missed
feature], wicked does not consider settings in ifsysctl files [bug].
> with wicked show all
>
> I have very bad information ?
>
> wicked show all
> lo up
> link: #1, state up
> type: loopback
> cstate: network-up
> config: compat:/etc/sysconfig/network/ifcfg-lo
> leases: ipv4 static granted
> leases: ipv6 static granted
> addr: ipv4 127.0.0.1/8
> addr: ipv6 ::1/128
>
> enp2s0f0 up
> link: #2, state up, mtu 1500, master br0
> type: ethernet, hwaddr 00:15:17:29:12:10
> cstate: link-authenticated
> config: compat:/etc/sysconfig/network/ifcfg-enp2s0f0
>
> enp2s0f1 up
> link: #3, state up, mtu 1500, master br1
> type: ethernet, hwaddr 00:15:17:29:12:11
> cstate: link-authenticated
> config: compat:/etc/sysconfig/network/ifcfg-enp2s0f1
>
> enp6s0 device-not-started
> link: #4, state down, mtu 1500
> type: ethernet, hwaddr 54:04:a6:8a:64:f5
> cstate: device-exists
>
> enp7s0 device-not-started
> link: #5, state down, mtu 1500
> type: ethernet, hwaddr 54:04:a6:8a:6b:ec
> cstate: device-exists
>
> br0 up
> link: #6, state up, mtu 1500
> type: bridge
> cstate: link-up
> config: compat:/etc/sysconfig/network/ifcfg-br0
> leases: ipv4 static granted
> addr: ipv4 192.168.200.220/16
> addr: ipv6 2001:15c0:65ff:868c:215:17ff:fe29:1210/64
> route: ipv4 default via 192.168.100.220
> route: ipv6 default via fe80::215:17ff:fe13:b8a7
>
> br1 up
> link: #7, state up, mtu 1500
> type: bridge
> cstate: network-up
> config: compat:/etc/sysconfig/network/ifcfg-br1
> leases: ipv6 static granted
> addr: ipv6 2001:15c0:65ff:868c:215:17ff:fe29:1211/64
> addr: ipv6 2001:15c0:65ff:868c::dc/64
> route: ipv6 default via fe80::215:17ff:fe13:b8a7
>
> ovs-system device-not-started
> link: #8, state down, mtu 1500
> type: ethernet, hwaddr b6:d1:01:b7:46:4d
> cstate: device-exists
>
>
> the IPv6 routing is wrong ?
No, it isn't. It is just autoconfigured.
> Witch command Is for deactivate iPv6 for a NIC
See https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt
echo "net.ipv6.conf.foo0.disable_ipv6 = 1" >
/etc/sysconfig/network/ifsysctl-foo0
or
echo "net.ipv6.conf.foo0.disable_ipv6 = 1" > /etc/sysconfig/network/ifsysctl
You can also disable the address-:
net.ipv6.conf.foo0.autoconf = 0
and/or route autoconfiguration:
net.ipv6.conf.foo0.accept_ra = 0.
When you want to disable it globally, you may add an "all" policy to:
/etc/sysctl.d/99-sysctl.conf
net.ipv6.conf.all.disable_ipv6 = 1
> Witch command is for correct route for IPv6
The routes are AFAIS correct. IPv6 routes usually do not go via a router
from same prefix, but via link-local (fe80:...) addresses of the router.
> I found nothing in the Manuals for wicked :-(,
Yes, going to fix it. "man ifsysctl" on SLE-11.
> This is a Strong change for network ?
IMO no changes at all. Most things are same as on SLES-11 at this place.
> What is correct way to config for the Network it is nor possible to
> change NS Server and so on ?
=> yast2 lan
Gruesse / Regards,
Marius Tomaschewski <mt at suse.de>, <mt at suse.com>
--
SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg),
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer,
Maxfeldstraße 5, 90409 Nürnberg, Germany
More information about the sles-beta
mailing list