I have a peculiar problem with Wicked (?). In India service provider MTNL is still on IPv4. While using 12.2, 12.3 and 13.1 etc I found the system took for ever to connect to any site and that turning the IPv6 option off allowed me to access the internet. Once IPv6 option was turned off there were no further problems.
With 13.2 “Wicked” I find that “each” time I reboot I have to go to Network Devices in Yast and “switch” this setting to access the internet!! I mean if the setting is changed from “on to off” the first time, after the next reboot/restart it has to be changed from “off to on”.
The other grouse is that I cannot view the progress of downloads on the small graphical inset of Network Manager.
Am I doing something wrong.?
I had earlier posted this problem under “Internet” group but got no reply.
I haven’t examined Wicked much yet since I mainly run on 13.1 but you could disable IPv6 completely from the system using either one of these methods;
add net.ipv6.conf.all.disable_ipv6 = 1 to /etc/sysctl.conf and reboot
or
add ipv6.disable=1 to your Grub parameters ( YAST -> Bootloader -> System -> Boot Loader -> Kernel Parameters and add it in the Optional Kernel Command Line Parameter at the end of the line ) and restart the system.
Note that this will completely disable IPv6. You can use conf.nameofyournetworkdevice.disable_ipv6 to choose a particular interface to disable it for, for example ens33.
Dear Miuku,
Thanks for your reply. I will try itt out and post the outcome. However, I have a niggling doubt. There is something wrong in Wicked which needs looking into by its team! The behaviour I have run into is peculiar, that is the actual status of IP6 enabling is not indicated in the YAST device set up. And that the IP6 enabled is the state in which wicked always starts.
A part of the problem appears to be at the service provider end in that they do not have IPv6. It is MTNL New Delhi wired DSL connection. The connectivity problem existed even in 12.3 and 13.1. If the set up had IPv6 enabled it would take for ever to connect to the server, with IPv6 disabled the connection worked fine.
With ‘wicked’ the problem has a new twist. I boot on and find connection is not working. Yast->Network Devices disable IPv6 get message that to put into effect need to reboot. I do not reboot and try connecting and get a fine connection! Next time I boot up the connection is not working. Yast->Network Devices enable IPv6 and get same message. Again do not reboot and find connection is fine!! Next time it is again IPv6 enabled to disabled and so on.
No, I have not tampered or fiddled with any setting. And I borrowed a USB mobile wifi card connection (Tata Indicom). No problem!
Again - I tested on 13.2 with wicked and IPv6 disabled persist across reboots. So it is not general problem. This seems something specific to your system. For a start - yast writes line “net.ipv6.conf.all.disable_ipv6 = 1” to /etc/sysctl.conf. Is this line present before and after reboot? What shows “find /proc/sys -name disable_ipv6 | xargs grep -H .” before and after reboot?
Suddenly the problem disappeared! No, I did not change any settings. I recall one of the updates had something to do with ‘wicked’, but I doubt that was directed towards this issue. Probably some file in my set up was corrupt and was replaced during udate.
Thanks for your help. I checked the files and it shows IPv6 switched off.
