Is nmcli/network manager worth it (in terms of bloat) and/or how to achieve the same with wvdial for my mobile internet connection
by linuxuser371038 from LinuxQuestions.org on (#6M6K1)
I think the main gaps in my general understanding of networking are around routing and how IP addresses are issued in the system regardless of network interface - wired, wifi, mobile.
I had been banging my head against a wall all day trying to get wvdial to work with my 3g dongle following the archwiki: https://wiki.archlinux.org/title/Wvdial which is rather sparse.
I had edited the wvdial config file and was getting the error of No carrier. Somehow I managed to figure out I was using the wrong tty interface (0 instead of 2) which I think I garnered by looking at mmcli info and it showed main interface to be the latter.
Ok so then I change that in the wvdial conf file and then was able to get a connection and a bunch of output on the terminal which was gibberish to me.
I took that as a good sign however there was a problem in that there was no internet still and it seemed the problem was that an IP address had not been issued. Not sure what led me to this conclusion at the time but I do know dhcpcd was running as standard on my system so don't know what was missing to prevent it from being issued.
Due to the anorectic documentation generally for mobile internet connections I was at a loss how to complete that step to tie it together.
So I did some more searches on how to bring a mobile dongle online and found another article which used network manager/nmcli instead; namely this article: https://ubuntu.com/core/docs/network...ar-connections
I stopped any services related to the previous attempts and started again following that which uses network manager and lo and behold I was able to get it to work.
The missing pieces to bring it up seemed to be these two lines:
Code:$ nmcli c add type gsm ifname <interface> con-name <name> apn <operator_apn>
$ nmcli r wwan onI had not used network manager with any regularity before due to preferring the simplest solutions (some small profile for wired and wpa_supplicant more recently for wifi) and just making a small shell script to bring up relevant interfaces. I am wondering is network manager/nmcli worth having around despite being quite large compared to simple, individual, scripting options. If so why? Also I would like to know how to achieve the same with wvdial bearing in mind the problem I believe is that I was able to get a connection with wvdial but was not able to get ip routing to work with it.
The above nmcli commands somehow was able to set that all up for me so I am trying to better understand how it did it for general edification but also to be able to attempt with other programs should I choose to.
Unless people give good reasons to stick with network manager I think all other things being equal I would prefer individual solutions as I have done up to now. I am only using it right now as that is the only thing I got to work so far with the mobile connection. It also wiped my /etc/resolv.conf (historically I would make it immutable when programs would try to do that but not sure if that would mess up network manager's usual operation and still don't understand why certain programs do this so more understanding required here too) which I am not fond of, since the programs that change them would break the functionality of other ones that want to use it, often leaving a blank file behind (again would like to know what is up with this too if anyone can comment as an aside), and took me a little to figure out that was the issue as to why my wifi connection stopped working after having installed network manager.
I had been banging my head against a wall all day trying to get wvdial to work with my 3g dongle following the archwiki: https://wiki.archlinux.org/title/Wvdial which is rather sparse.
I had edited the wvdial config file and was getting the error of No carrier. Somehow I managed to figure out I was using the wrong tty interface (0 instead of 2) which I think I garnered by looking at mmcli info and it showed main interface to be the latter.
Ok so then I change that in the wvdial conf file and then was able to get a connection and a bunch of output on the terminal which was gibberish to me.
I took that as a good sign however there was a problem in that there was no internet still and it seemed the problem was that an IP address had not been issued. Not sure what led me to this conclusion at the time but I do know dhcpcd was running as standard on my system so don't know what was missing to prevent it from being issued.
Due to the anorectic documentation generally for mobile internet connections I was at a loss how to complete that step to tie it together.
So I did some more searches on how to bring a mobile dongle online and found another article which used network manager/nmcli instead; namely this article: https://ubuntu.com/core/docs/network...ar-connections
I stopped any services related to the previous attempts and started again following that which uses network manager and lo and behold I was able to get it to work.
The missing pieces to bring it up seemed to be these two lines:
Code:$ nmcli c add type gsm ifname <interface> con-name <name> apn <operator_apn>
$ nmcli r wwan onI had not used network manager with any regularity before due to preferring the simplest solutions (some small profile for wired and wpa_supplicant more recently for wifi) and just making a small shell script to bring up relevant interfaces. I am wondering is network manager/nmcli worth having around despite being quite large compared to simple, individual, scripting options. If so why? Also I would like to know how to achieve the same with wvdial bearing in mind the problem I believe is that I was able to get a connection with wvdial but was not able to get ip routing to work with it.
The above nmcli commands somehow was able to set that all up for me so I am trying to better understand how it did it for general edification but also to be able to attempt with other programs should I choose to.
Unless people give good reasons to stick with network manager I think all other things being equal I would prefer individual solutions as I have done up to now. I am only using it right now as that is the only thing I got to work so far with the mobile connection. It also wiped my /etc/resolv.conf (historically I would make it immutable when programs would try to do that but not sure if that would mess up network manager's usual operation and still don't understand why certain programs do this so more understanding required here too) which I am not fond of, since the programs that change them would break the functionality of other ones that want to use it, often leaving a blank file behind (again would like to know what is up with this too if anyone can comment as an aside), and took me a little to figure out that was the issue as to why my wifi connection stopped working after having installed network manager.