Beiträge von manni_watzki

manni_watzki · 30. Juni 2016

Code

Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: You can find my version in /etc/resolv.conf.netconfig ...
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: You can find my version in /etc/resolv.conf.netconfig ...
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  keyfile: add connection in-memory (edd2cd03-18da-40fa-85a2-ab3c6ec5733c,"tun0")
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  (tun0): Activation: starting connection 'tun0' (edd2cd03-18da-40fa-85a2-ab3c6ec5733c)
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: You can find my version in /etc/resolv.conf.netconfig ...
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  (tun0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  NetworkManager state is now CONNECTED_LOCAL
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  Policy set 'tun0' (tun0) as default for IPv4 routing and DNS.
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: You can find my version in /etc/resolv.conf.netconfig ...
Jun 26 23:34:08 Asus-X52F NetworkManager[1014]: <info>  (tun0): Activation: successful, device activated.
Jun 26 23:34:17 Asus-X52F nm-openvpn[6920]: Bad LZO decompression header byte: 0
Jun 26 23:34:28 Asus-X52F nm-openvpn[6920]: Bad LZO decompression header byte: 0
Jun 26 23:34:38 Asus-X52F nm-openvpn[6920]: Bad LZO decompression header byte: 0
Jun 26 23:34:48 Asus-X52F nm-openvpn[6920]: Bad LZO decompression header byte: 0
Jun 26 23:34:58 Asus-X52F nm-openvpn[6920]: Bad LZO decompression header byte: 0
Jun 26 23:35:07 Asus-X52F nm-openvpn[6920]: [server] Inactivity timeout (--ping-restart), restarting
Jun 26 23:35:07 Asus-X52F nm-openvpn[6920]: SIGUSR1[soft,ping-restart] received, process restarting
Jun 26 23:35:09 Asus-X52F nm-openvpn[6920]: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 26 23:35:09 Asus-X52F nm-openvpn[6920]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Alles anzeigen

manni_watzki · 30. Juni 2016

Vielleicht ist das nützlicher, um den Fehler zu ermitteln und beseitigen.
Hat jemand Ahnung, wie das geht? Früher hatte ich einen anderen Anbieter, so etwas war mir nie passiert (nur spontane, zufällige Trennungen, die durch Portweiterleitung und angemessene Firewall-Einstellungen dann verschwunden sind).

Code

# journalctl --since=2016-06-26 -u NetworkManager
Jun 26 23:34:04 Asus-X52F NetworkManager[1014]: <info>  Starting VPN service 'openvpn'...
Jun 26 23:34:04 Asus-X52F NetworkManager[1014]: <info>  VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 6916
Jun 26 23:34:04 Asus-X52F NetworkManager[1014]: <info>  VPN service 'openvpn' appeared; activating connections
Jun 26 23:34:04 Asus-X52F NetworkManager[1014]: (nm-openvpn-service:6916): nm-openvpn-WARNING **: Directory '/var/lib/openvpn/chroot' not usable for chroot by 'nm-openvpn', openvpn will not be chrooted.
Jun 26 23:34:04 Asus-X52F NetworkManager[1014]: <info>  VPN plugin state changed: starting (3)
Jun 26 23:34:04 Asus-X52F NetworkManager[1014]: nm-openvpn-Message: openvpn started with pid 6920
Jun 26 23:34:04 Asus-X52F NetworkManager[1014]: <info>  VPN connection 'ibVPN_Germany_(Frankfurt_1)' (Connect) reply received.
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: OpenVPN 2.3.10 x86_64-suse-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Jan  4 2016
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: library versions: OpenSSL 1.0.1i-fips 6 Aug 2014, LZO 2.08
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: UDPv4 link local: [undef]
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: UDPv4 link remote: [AF_INET]178.162.221.62:1194
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: WARNING: 'dev-type' is used inconsistently, local='dev-type tun', remote='dev-type tap'
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1542', remote='link-mtu 1578'
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532'
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: WARNING: 'mtu-dynamic' is present in remote config but missing in local config, remote='mtu-dynamic'
Jun 26 23:34:04 Asus-X52F nm-openvpn[6920]: [server] Peer Connection Initiated with [AF_INET]178.162.221.62:1194
Jun 26 23:34:07 Asus-X52F nm-openvpn[6920]: Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:1: show-net-up (2.3.10)
Jun 26 23:34:07 Asus-X52F nm-openvpn[6920]: WARNING: Since you are using --dev tun with a point-to-point topology, the second argument to --ifconfig must be an IP address.  You are using something (255.255.255.0) that looks more like a n
Jun 26 23:34:07 Asus-X52F nm-openvpn[6920]: TUN/TAP device tun0 opened
Jun 26 23:34:07 Asus-X52F nm-openvpn[6920]: /usr/lib/nm-openvpn-service-openvpn-helper --tun -- tun0 1500 1542 10.10.10.2 255.255.255.0 init
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  (tun0): new Tun device (carrier: OFF, driver: 'tun', ifindex: 4)
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  VPN connection 'ibVPN_Germany_(Frankfurt_1)' (IP Config Get) reply received.
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  VPN connection 'ibVPN_Germany_(Frankfurt_1)' (IP4 Config Get) reply received.
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  VPN Gateway: 178.162.221.62
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  Tunnel Device: tun0
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  IPv4 configuration:
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    Internal Gateway: 10.10.10.1
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    Internal Address: 10.10.10.2
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    Internal Prefix: 24
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    Internal Point-to-Point Address: 0.0.0.0
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    Maximum Segment Size (MSS): 0
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    Forbid Default Route: no
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    Internal DNS: 1.2.3.4
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>    DNS Domain: '(none)'
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  No IPv6 configuration
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  VPN plugin state changed: started (4)
Jun 26 23:34:07 Asus-X52F nm-openvpn[6920]: GID set to nm-openvpn
Jun 26 23:34:07 Asus-X52F nm-openvpn[6920]: UID set to nm-openvpn
Jun 26 23:34:07 Asus-X52F nm-openvpn[6920]: Initialization Sequence Completed
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  VPN connection 'ibVPN_Germany_(Frankfurt_1)' (IP Config Get) complete.
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  (tun0): link connected
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  NetworkManager state is now CONNECTED_LOCAL
Jun 26 23:34:07 Asus-X52F NetworkManager[1014]: <info>  NetworkManager state is now CONNECTED_GLOBAL

Alles anzeigen

manni_watzki · 20. Juni 2016

Ich möchte mich dem Thema anschließen, weil ich ein komisches Verhalten von openvpn bekomme.

Wenn ich die Verbindung zum Server (mein Dienst ist ibVPN) per Kommandozeile herstelle, alles in Ordnung.

Code

# openvpn --config ibVPN_Germany_\(Frankfurt_1\).ovpn




Mon Jun 20 18:21:19 2016 OpenVPN 2.3.10 x86_64-suse-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Jan  4 2016
Mon Jun 20 18:21:19 2016 library versions: OpenSSL 1.0.1i-fips 6 Aug 2014, LZO 2.08
Mon Jun 20 18:21:19 2016 WARNING: file 'user_pass.txt' is group or others accessible
Mon Jun 20 18:21:19 2016 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Jun 20 18:21:19 2016 WARNING: normally if you use --mssfix and/or --fragment, you should also set --tun-mtu 1500 (currently it is 1502)
Mon Jun 20 18:21:19 2016 Socket Buffers: R=[87380->87380] S=[16384->16384]
Mon Jun 20 18:21:20 2016 Attempting to establish TCP connection with [AF_INET]178.162.197.145:1194 [nonblock]
Mon Jun 20 18:21:21 2016 TCP connection established with [AF_INET]178.162.197.145:1194
Mon Jun 20 18:21:21 2016 TCPv4_CLIENT link local: [undef]
Mon Jun 20 18:21:21 2016 TCPv4_CLIENT link remote: [AF_INET]178.162.197.145:1194
Mon Jun 20 18:21:21 2016 TLS: Initial packet from [AF_INET]178.162.197.145:1194, sid=a24ab55f 48685518
Mon Jun 20 18:21:21 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Jun 20 18:21:21 2016 VERIFY OK: depth=1, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, CN=Fort-Funston CA, emailAddress=me@myhost.mydomain
Mon Jun 20 18:21:21 2016 VERIFY OK: nsCertType=SERVER
Mon Jun 20 18:21:21 2016 VERIFY OK: depth=0, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, CN=server, emailAddress=me@myhost.mydomain
Mon Jun 20 18:21:21 2016 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1578', remote='link-mtu 1576'
Mon Jun 20 18:21:21 2016 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1534', remote='tun-mtu 1532'
Mon Jun 20 18:21:21 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jun 20 18:21:21 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jun 20 18:21:21 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jun 20 18:21:21 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jun 20 18:21:21 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Mon Jun 20 18:21:21 2016 [server] Peer Connection Initiated with [AF_INET]178.162.197.145:1194
Mon Jun 20 18:21:23 2016 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Mon Jun 20 18:21:23 2016 PUSH: Received control message: 'PUSH_REPLY,show-net-up,route-gateway 10.10.20.1,ping 10,ping-restart 60,redirect-gateway def1,dhcp-option DNS 1.2.3.4,ifconfig 10.10.20.5 255.255.255.0'
Mon Jun 20 18:21:23 2016 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:1: show-net-up (2.3.10)
Mon Jun 20 18:21:23 2016 OPTIONS IMPORT: timers and/or timeouts modified
Mon Jun 20 18:21:23 2016 OPTIONS IMPORT: --ifconfig/up options modified
Mon Jun 20 18:21:23 2016 OPTIONS IMPORT: route options modified
Mon Jun 20 18:21:23 2016 OPTIONS IMPORT: route-related options modified
Mon Jun 20 18:21:23 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon Jun 20 18:21:23 2016 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=eth0 HWADDR=f4:6d:04:7f:17:10
Mon Jun 20 18:21:23 2016 TUN/TAP device tap0 opened
Mon Jun 20 18:21:23 2016 TUN/TAP TX queue length set to 100
Mon Jun 20 18:21:23 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Mon Jun 20 18:21:23 2016 /bin/ip link set dev tap0 up mtu 1502
Mon Jun 20 18:21:23 2016 /bin/ip addr add dev tap0 10.10.20.5/24 broadcast 10.10.20.255
Mon Jun 20 18:21:23 2016 client.up tap0 1502 1578 10.10.20.5 255.255.255.0 init
Mon Jun 20 18:21:25 2016 /bin/ip route add 178.162.197.145/32 via 192.168.1.1
Mon Jun 20 18:21:25 2016 /bin/ip route add 0.0.0.0/1 via 10.10.20.1
Mon Jun 20 18:21:25 2016 /bin/ip route add 128.0.0.0/1 via 10.10.20.1
Mon Jun 20 18:21:25 2016 Initialization Sequence Completed

Alles anzeigen

Wenn ich hingegen versuche, das über GUI zu tun, kriege ich unstabile Verbindungen (nach 1-2 Minuten wieder weg) bis keine Erreichbarkeit jeder Ressource im Internet.

Ausgabe vom Bericht:

Code

#journalctl --since=2016-06-20 | grep vpn | tail




Jun 20 17:36:44 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:44 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:45 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:45 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:46 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:46 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:47 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:47 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:48 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0
Jun 20 17:36:48 Asus-X52F nm-openvpn[13487]: Bad LZO decompression header byte: 0

Alles anzeigen

Irgendwas mit LZO-Kompression stimmt also nicht.

Aber mal in die Konfig-Datei schauen:

Code

remote de1.ibvpn.com 1194 tcp
remote 178.162.221.62 1194 tcp
auth-user-pass user_pass.txt
up 'client.up'
down 'client.down'
link-mtu 1578
dev tap
server-poll-timeout 20
client
nobind
resolv-retry infinite
auth-retry nointeract
persist-key
persist-tun
mute-replay-warnings
comp-lzo
verb 3
mute 20
ns-cert-type server
route-method exe
route-delay 2
script-security 3 system
reneg-sec 0
<ca>
-----BEGIN CERTIFICATE-----
[…]
-----END CERTIFICATE-----
</ca>

Alles anzeigen

Von der oben genannten Datei habe ich die Verbindung im NM importiert. Man sollte also das gleiche Verhalten erwarten.

manni_watzki · 15. Mai 2016

Pardon, ich hatte die GUI gestartet.
Mittlerweile habe ich meine Netzwerkprobleme im Runlevel 3 gelöst.

Danach habe ich sämtliche installierten Pakete aus den jeweiligen Schemata-Listen (Plasma5 + KDE) deinstalliert und dann erneut installiert.
Resultat: System zusammengeschossen, kein grafischer Modus mehr möglich. Musste eine Sicherung einspielen.

Wie kann ich KDE so sauber wie möglich neu installieren, ohne dass irgendwas schiefgeht?

manni_watzki · 14. Mai 2016

Korrektur: IP-Adresse wird nicht bezogen.

manni_watzki · 14. Mai 2016

Das erklärt aber nicht, warum es in meinem Fall nicht klappt.
Sowohl eth0 als auch dhcp sind aktiv, wenn ich auf wicked umstelle. IP-Adresse wird bezogen, trotzdem erhalte ich keinen Zugang zum Internet.

manni_watzki · 12. Mai 2016

Hier mal das Ergebnis.

manni_watzki · 12. Mai 2016

Hatte mich vertippt, tut mir leid.

Zitat von SUSEDJAlex

du kannst nur eines benutzen ....

Ja, eben! Hast du richtig gelesen?

Code

~ hwinfo --network
40: None 00.0: 1070a WLAN                                       
  [Created at net.125]
  Unique ID: AYEt.QXn1l67RSa1
  Parent ID: y9sn.YOgHHBQ2is7
  SysFS ID: /class/net/wlan0
  SysFS Device Link: /devices/pci0000:00/0000:00:1c.1/0000:02:00.0
  Hardware Class: network interface
  Model: "WLAN network interface"
  Driver: "ath9k"
  Driver Modules: "ath9k"
  Device File: wlan0
  HW Address: 48:5d:60:9c:c2:fd
  Link detected: no
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #16 (Network controller)


41: None 00.0: 10700 Loopback
  [Created at net.125]
  Unique ID: ZsBS.GQNx7L4uPNA
  SysFS ID: /class/net/lo
  Hardware Class: network interface
  Model: "Loopback network interface"
  Device File: lo
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown


42: None 00.0: 10701 Ethernet
  [Created at net.125]
  Unique ID: usDW.ndpeucax6V1
  Parent ID: rBUF.W7HhcEuXdY2
  SysFS ID: /class/net/eth0
  SysFS Device Link: /devices/pci0000:00/0000:00:1c.5/0000:04:00.5
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "jme"
  Driver Modules: "jme"
  Device File: eth0
  HW Address: f4:6d:04:7f:17:10
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Ethernet controller)


43: None 00.0: 10780 Network Interface
  [Created at net.125]
  Unique ID: RRvF.GSopYcFr9cF
  SysFS ID: /class/net/ppp0
  Hardware Class: network interface
  Model: "Network Interface"
  Device File: ppp0
  Link detected: yes

Alles anzeigen

manni_watzki · 12. Mai 2016

Habe ich irgendwas vergessen?

Code

# sysctl stop network.service


# sysctl stop NetworkManager.service


# sysctl start wickedd.service


# sysctl start wicked.service


# sysctl start network.service


# netconfig update


# ping 8.8.8.8
connect: Network is unreachable

Alles anzeigen

manni_watzki · 11. Mai 2016

Mal abgesehen davon, ob PackageKit Schwierigkeiten macht, möchte ich KDE komplett neu installieren, weil die Umgebung zum Teil zusammengeschossen scheint.

Wie geht das? Per Console + Umstellung auf Runlevel 3 + YaST habe ich keinen LAN-Zugriff mehr.

Beiträge von manni_watzki

Keine Verbindung über openVPN möglich

Keine Verbindung über openVPN möglich

Keine Verbindung über openVPN möglich

Plasma5, häufig fehlerhaftes Verhalten

Plasma5, häufig fehlerhaftes Verhalten

Plasma5, häufig fehlerhaftes Verhalten

Plasma5, häufig fehlerhaftes Verhalten

Plasma5, häufig fehlerhaftes Verhalten

Plasma5, häufig fehlerhaftes Verhalten

Plasma5, häufig fehlerhaftes Verhalten

Tumbleweed-Update bricht ab

GNOME OS Preview: Ein Schritt in Richtung Alltagsbetrieb

Ubuntu 26.10 „Stonking Stingray“ ist erschienen

KDE Plasma 6.8 verabschiedet sich von X11

VBox - gemeinsame Zwischenablage

pit1958ffm

Wanderratte

k.113

aitexturegenerator

Giorgio68