[SOLVED] Internet connection fails after UnionTech OS wakes from suspension.
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Internet connection fails after UnionTech OS wakes from suspension.
I am running UnionTech OS (often abbreviated to "UOS"), which is based on Deepin.
I have set up a PPPoE connection, which works fine after UOS has started. However, it does not work after UOS has woken from suspension. It will not work again even after I have run "pon dsl-provider". It will work again only after a reboot. How can I get it to work without a reboot?
A screenshot: https://www.linuxquestions.org/quest...p;d=1654869298
Last edited by Matthew Wai; 06-10-2022 at 09:15 AM.
Can you stop the network as part of the suspension procedure? With dhcp, it's easier as the server assigns an ip and the dhcp program can ask "Am I still good with that IP?"
Stop the network manually first then restart it after. You can get to automating it later.
Can you stop the network as part of the suspension procedure?
I just did the following test:
I stopped networking and then suspended UOS. I woke it up and started networking. It was still unable to connect "Wired Connection".
Code:
Matthew_Wai@MatthewWai:~$ sudo /etc/init.d/networking stop
[sudo] password for Matthew_Wai:
Verification successful
[ ok ] Stopping networking (via systemctl): networking.service.
Matthew_Wai@MatthewWai:~$ /etc/init.d/networking status
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2022-06-10 21:32:29 CST; 1min 42s ago
Docs: man:interfaces(5)
Process: 770 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
Process: 18457 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo (code=exited, status=0/SUCCESS)
Main PID: 770 (code=exited, status=0/SUCCESS)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Matthew_Wai@MatthewWai:~$ sudo /etc/init.d/networking start
[ ok ] Starting networking (via systemctl): networking.service.
Matthew_Wai@MatthewWai:~$ /etc/init.d/networking status
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2022-06-10 21:35:43 CST; 18s ago
Docs: man:interfaces(5)
Process: 19806 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
Main PID: 19806 (code=exited, status=0/SUCCESS)
Matthew_Wai@MatthewWai:~$ ifconfig -a
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::ebb8:dcde:c545:31fc prefixlen 64 scopeid 0x20<link>
ether e0:d5:5e:cc:65:a3 txqueuelen 1000 (Ethernet)
RX packets 20155 bytes 5894685 (5.6 MiB)
RX errors 0 dropped 6 overruns 0 frame 0
TX packets 46543 bytes 17961096 (17.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 28 base 0xd000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 33344 bytes 2464508 (2.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 33344 bytes 2464508 (2.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Matthew_Wai@MatthewWai:~$
Last edited by Matthew Wai; 06-10-2022 at 08:58 AM.
My PPPoE connection just failed again after suspension.
I opened Terminal and ran the following commands to re-enable the network adapter:
Code:
sudo ip link set enp2s0 down && sudo ip link set enp2s0 up
However, the connection still failed.
Then, I opened Device Manager, manually disabled the network adapter and re-enabled it. Then, the connection worked again.
Quote:
Originally Posted by business_kid
You can get to automating it later.
How can I automate it via commands? What commands can be used instead of "ip link set"?
I don't have Union Tech OS. There's a problem with less well known distros. Developers are few, experience is limited, an when it come to something like suspend & restart working on ALL laptops, they can't compete.
Your best bet is to develop the suspend script yourself. In this case shut down the network before suspend, & resume afterwards. Then, when it's working, submit the changes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.