f38:: disabling NetworkManager makes xorg to core dump

Hi! Did anyone else observe the behavior from subject? I tried to move the NetworkManager starting from systemd to cron (because it takes to much to start and it is in critical-chain) and while it worked, the xorg no longer started up, and the journal show xorg core dumping... Anyone have any

solved - Re: F38 migrate NetworkManager/system-connections

On 5/1/23 09:01, francis.montag...@inria.fr wrote: Hi On Mon, 01 May 2023 08:52:49 -0400 Robert Moskowitz wrote: I have got the many *.nmconnection files moved to the F38 system into the /etc/NetworkManager/system-connections Owned by root:root with chmod 600 as the ones already there. When I

Re: F38 migrate NetworkManager/system-connections

Hi On Mon, 01 May 2023 08:52:49 -0400 Robert Moskowitz wrote: > I have got the many *.nmconnection files moved to the F38 system into > the /etc/NetworkManager/system-connections > Owned by root:root with chmod 600 as the ones already there. > When I look at the Edit Connec

Re: F38 migrate NetworkManager/system-connections

Progress I have got the many *.nmconnection files moved to the F38 system into the /etc/NetworkManager/system-connections Owned by root:root with chmod 600 as the ones already there. When I look at the Edit Connections dialog in the Xfce panel network app, they are not listed. What do I

Re: F38 migrate NetworkManager/system-connections

On Mon, 2023-05-01 at 05:22 -0400, Robert Moskowitz wrote: > In copying them to USB: > > # cp -a /etc/NetworkManager/system-connections/* > /run/media/rgm/3153-B4EA/system-connections/ > cp: failed to preserve ownership for > '/run/media/rgm/3153-B4EA/system-connections/e

Re: F38 migrate NetworkManager/system-connections

On 5/1/23 04:15, Peter Boy wrote: Am 01.05.2023 um 04:39 schrieb Robert Moskowitz : Is there a way to migrate the NetworkManager/system-connections files from F35 to F38 system? I am not finding an export option and haven't figured out how to get around file permissions to copy

Re: F38 migrate NetworkManager/system-connections

On 5/1/23 02:13, Jeffrey Walton wrote: On Sun, Apr 30, 2023 at 10:39 PM Robert Moskowitz wrote: Is there a way to migrate the NetworkManager/system-connections files from F35 to F38 system? I am not finding an export option and haven't figured out how to get around file permissions to copy

Re: F38 migrate NetworkManager/system-connections

On 5/1/23 00:33, Samuel Sieb wrote: On 4/30/23 19:39, Robert Moskowitz wrote: Is there a way to migrate the NetworkManager/system-connections files from F35 to F38 system? I am not finding an export option and haven't figured out how to get around file permissions to copy the files

Re: F38 migrate NetworkManager/system-connections

> Am 01.05.2023 um 04:39 schrieb Robert Moskowitz : > > Is there a way to migrate the NetworkManager/system-connections files from > F35 to F38 system? > > I am not finding an export option and haven't figured out how to get around > file permissions to copy the files to

Re: F38 migrate NetworkManager/system-connections

On Sun, Apr 30, 2023 at 10:39 PM Robert Moskowitz wrote: > > Is there a way to migrate the NetworkManager/system-connections files > from F35 to F38 system? > > I am not finding an export option and haven't figured out how to get > around file permissions to copy the files to

Re: F38 migrate NetworkManager/system-connections

On 4/30/23 19:39, Robert Moskowitz wrote: Is there a way to migrate the NetworkManager/system-connections files from F35 to F38 system? I am not finding an export option and haven't figured out how to get around file permissions to copy the files to a USB stick. What file permissions

F38 migrate NetworkManager/system-connections

Is there a way to migrate the NetworkManager/system-connections files from F35 to F38 system? I am not finding an export option and haven't figured out how to get around file permissions to copy the files to a USB stick. thanks ___ users mailing

Re: NetworkManager vs systemd-networkd

Mike Wright composed on 2023-04-25 18:43 (UTC-0700): > I've never been a fanboi when it came to NetworkManager so when I > installed f38 I used systemd-networkd. I found it straight forward and > was able to set up my networking very easily. > Does anybody know which way fo

NetworkManager vs systemd-networkd

Hi all, I've never been a fanboi when it came to NetworkManager so when I installed f38 I used systemd-networkd. I found it straight forward and was able to set up my networking very easily. Does anybody know which way forward Fedora is going? That is, NetworkManager with nmcli

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

On Mon, 2023-04-17 at 06:40 +0200, Franta Hanzlík via users wrote: > But in this case the connection specifies the target VPN server > somehow (I called it gw.mujsrv.org), but the NM OpenVPN client tries > to connect to 1a9107897c24.gw.mujsrv.org, 3abc1fd99dff.gw.mujsrv.org, >

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

On 4/16/23 21:40, Franta Hanzlík via users wrote: You are probably writing about the anonymization of the client - which is a case that still has some kind of substantiation. But in this case the connection specifies the target VPN server somehow (I called it gw.mujsrv.org), but the NM OpenVPN

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

On Mon, 17 Apr 2023 13:13:27 +0930 Tim via users wrote: > Franta Hanzlík: > >> But - somehow I don't understand - this wonderful feature (hostname > >> randomizing == disabling its resoulution/usage) that will cause > >> the connection to not work - does it have any real use? > >> Has anyone

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

Franta Hanzlík: >> But - somehow I don't understand - this wonderful feature (hostname >> randomizing == disabling its resoulution/usage) that will cause >> the connection to not work - does it have any real use? >> Has anyone gone crazy? Or am I crazy? Samuel Sieb: > It's an option that I can

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

e perhaps cached, and 'external' editing will not load > > the configuration ;) > > If you edit it manually, you need to use something (like nmcli) to tell > NetworkManager to reload the connection information. > > > But - somehow I don't understand - this wonderful feature

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

t manually, you need to use something (like nmcli) to tell NetworkManager to reload the connection information. But - somehow I don't understand - this wonderful feature (hostname randomizing == disabling its resoulution/usage) that will cause the connection to not work - does it have any rea

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

On Sun, 16 Apr 2023 13:02:03 -0700 Samuel Sieb wrote: > On 4/16/23 12:16, Franta Hanzlík via users wrote: > > I'm trying to configure OpenVPN connection in Fedora 37 NetworkManager. > > The configuration was created by importing the .ovpn file and subsequent > >

Re: connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

On 4/16/23 12:16, Franta Hanzlík via users wrote: I'm trying to configure OpenVPN connection in Fedora 37 NetworkManager. The configuration was created by importing the .ovpn file and subsequent its result correction. But connection is not working, and it seems it is because MetwokManage/nm

connecting to OpenVPN server: why NetworkManager nm-openvpn gererates curious, pointless random hostnames?

I'm trying to configure OpenVPN connection in Fedora 37 NetworkManager. The configuration was created by importing the .ovpn file and subsequent its result correction. But connection is not working, and it seems it is because MetwokManage/nm-openvpn prepend OpenVPN server name with random string

Re: NetworkManager switches between networks

On Sat, 28 Jan 2023 13:45:07 +1030 Tim via users wrote: > On Fri, 2023-01-27 at 13:57 -0800, Geoffrey Leach wrote: > > Home network has two wi-fi sources (Starlink and Netgear, fwiw). > > Occasionally NetworkManager switches betwee primary (Starlink) and > > secondary (Ne

Re: NetworkManager switches between networks

On Sat, 2023-01-28 at 13:45 +1030, Tim via users wrote: > What typically happens with people trying to get their device to > automatically shift to the nearest/best access point without doing > anything, while they roam around, is the device steadfastly tries to > stay connected to the one they

Re: NetworkManager switches between networks

On Fri, 2023-01-27 at 13:57 -0800, Geoffrey Leach wrote: > Home network has two wi-fi sources (Starlink and Netgear, fwiw). > Occasionally NetworkManager switches betwee primary (Starlink) and > secondary (Netgear) . I'm assuming that NetworkManager is trying to > connect to the stro

Re: NetworkManager switches between networks

would pick the other one. On Fri, Jan 27, 2023 at 3:58 PM Geoffrey Leach wrote: > Re-submitted with edit > > Home network has two wi-fi sources (Starlink and Netgear, fwiw). > Occasionally NetworkManager switches betwee primary (Starlink) and > secondary (Netgear) . I'm assuming that

Re: Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

On 12/19/22 14:25, Jon LaBadie wrote: Do the new names ("myname" in the above) become replacements or alternatives to the old device names.  I.e. must I modify any current scripts or config files that use the old names?  Or can either name be used. They are replacements. You can only use the

Re: Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

On 12/19/22 05:48, Dario Lesca wrote: I have two network device named ens192 and ens224 2: ens192: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0c:29:e6:6d:d7 brd ff:ff:ff:ff:ff:ff 3: ens224: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether

Re: Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

On Mon, Dec 19, 2022 at 05:49:10PM +0100, t_pol wrote: Hi, I had the same prob. Created 2 files in /etc/systemd/network/ 10-persistent-lan1.link 10-persistent-lan2.link with the following contents : [Match] MACAddress=xx:xx:xx:xx:xx:xx [Link] Name=myname it works. Hope

Re: Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

Il giorno lun, 19/12/2022 alle 17.49 +0100, t_pol ha scritto: > Created 2 files in /etc/systemd/network/ > > 10-persistent-lan1.link > 10-persistent-lan2.link > > with the following contents : > > [Match] > MACAddress=xx:xx:xx:xx:xx:xx > [Link] > Name=myname > > it works. > >

Re: Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

k/ether > 00:0c:29:e6:6d:e1 brd ff:ff:ff:ff:ff:ff > > It's possible to rename it with a logical name like LAN and WAN with > nmcli? > > I have found this howto: > https://www.thegeekdiary.com/how-to-set-a-custom-interface-name-with-networkmanager-in-centos-rhel-7/ > > B

Re: Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

> I have found this howto: > https://www.thegeekdiary.com/how-to-set-a-custom-interface-name-with-networkmanager-in-centos-rhel-7/ > > But seem not work into Fedora 37. > > If it's possible, what is the best way to set this name? Use a udev rule, like https://enterprise-support.nvidia.com/

Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

possible to rename it with a logical name like LAN and WAN with nmcli? I have found this howto: https://www.thegeekdiary.com/how-to-set-a-custom-interface-name-with-networkmanager-in-centos-rhel-7/ But seem not work into Fedora 37. If it's possible, what is the best way to set this name? Many

802.1x Reauth with linux bridge not working - NetworkManager does not reply to get identiy

We are trying to implement 802.1x on our Fedora-Workstations (36, latest updates) for both, the workstation itself and a Windows KVM Guest. Therefor we created a linux bridge with the physical and virtual device as members. The virtual kvm guest has been configured to use the br0 within kvm. To

NetworkManager not creating VLAN at boot

I am setting up Fedora 36 on a new laptop, and I'm trying (really, I'm trying!) to be a good boy and use NetworkManager for everything. After beating my head against the wall for a day, I've finally managed to get it to create a simple Open vSwitch bridge (ovs0), for use with virtual machines

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong (Resolved)

if it makes any difference. I put the specified command into iwlwifi.conf and it makes not difference, the wifi is not available on booting directly into linux. Just one further question , if connected to ethernet how do you try switching to wifi if networkmanager doesn't show any of the wifi

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

the specified command into iwlwifi.conf and it makes not difference, the wifi is not available on booting directly into linux. Just one further question , if connected to ethernet how do you try switching to wifi if networkmanager doesn't show any of the wifi ssid's so that you can try connecting

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

On 6/7/22 09:23, Roger Heflin wrote: Error -110 is timeout, meaning the device did not respond to the commands. It usually means the hardware in question is in a bad/locked up state so the kernel is unable to init it. If the issue is after a suspend/resume then try below: Other notes indicate

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

Error -110 is timeout, meaning the device did not respond to the commands. It usually means the hardware in question is in a bad/locked up state so the kernel is unable to init it. If the issue is after a suspend/resume then try below: Other notes indicate this: Please create the file

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

On 4/7/22 22:42, Tim via users wrote: On Mon, 2022-07-04 at 18:15 +1000, Stephen Morris wrote: The package must have been updated as when I looked yesterday it didn't supply any of those files, unless I looked at the file list from the wrong package dnf history See what got updated when.

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

On Mon, 2022-07-04 at 18:15 +1000, Stephen Morris wrote: > The package must have been updated as when I looked yesterday it > didn't supply any of those files, unless I looked at the file list > from the wrong package dnf history See what got updated when. -- uname -rsvp Linux

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

On 4/7/22 12:13, Samuel Sieb wrote: On 7/3/22 03:12, Stephen Morris wrote: On 3/7/22 19:05, Stephen Morris wrote: On 30/6/22 09:08, Stephen Morris wrote: Hi,     I booted into Fedora this morning and had no network available because wifi had not been started. Dmesg showed the following

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

On 7/3/22 03:12, Stephen Morris wrote: On 3/7/22 19:05, Stephen Morris wrote: On 30/6/22 09:08, Stephen Morris wrote: Hi,     I booted into Fedora this morning and had no network available because wifi had not been started. Dmesg showed the following message: iwlwifi: probe of :05:00.0

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

    There is not an issue with the wifi router as my wife was using the internet on her laptop at the time.     Also, when I looked at the wifi definition it said the wifi was last used 3 hours ago, but it has been over 9 hours since I shutdown my pc and that was from Windows, so where is networkmanager

Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

wife was using the internet on her laptop at the time.     Also, when I looked at the wifi definition it said the wifi was last used 3 hours ago, but it has been over 9 hours since I shutdown my pc and that was from Windows, so where is networkmanager (assuming Fedora is still using networkmanager

Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong

at the time.     Also, when I looked at the wifi definition it said the wifi was last used 3 hours ago, but it has been over 9 hours since I shutdown my pc and that was from Windows, so where is networkmanager (assuming Fedora is still using networkmanager) getting its information from? I am

Re: Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

Il giorno gio, 19/05/2022 alle 07.37 -0700, stan via users ha scritto: > File a bug for selinux.  If it isn't theirs, they will forward it to > NetworkManager.  You should include the above command you used to > work > around the issue. I have fill this bug: https://bugzill

Re: Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

On Thu, May 19, 2022 at 11:27 AM Dario Lesca wrote: > Il giorno mer, 18/05/2022 alle 09.00 +0200, Zdenek Pytela ha scritto: > > You can make just one domain a permissive one: > > > > sudo semanage permissive -a NetworkManager_dispatcher_t > > Ok, this resolve my problem. > Is this modify

Re: Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

ux. If it isn't theirs, they will forward it to NetworkManager. You should include the above command you used to work around the issue. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedora

Re: Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

Il giorno mer, 18/05/2022 alle 09.00 +0200, Zdenek Pytela ha scritto: > You can make just one domain a permissive one: > >  sudo semanage permissive -a NetworkManager_dispatcher_t Ok, this resolve my problem. Is this modify permanent at boot or I must repeat every restart? Another question: Is

Re: Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

On Wed, May 18, 2022 at 1:56 AM Dario Lesca wrote: > Il giorno mar, 17/05/2022 alle 19.42 +0200, Zdenek Pytela ha scritto: > > If the /etc/NetworkManager/dispatcher.d/15-vpn-disp file is not a > > part of any package, the following command should set the correct > > label: &

Re: Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

Il giorno mar, 17/05/2022 alle 19.42 +0200, Zdenek Pytela ha scritto: > If the /etc/NetworkManager/dispatcher.d/15-vpn-disp file is not a > part of any package, the following command should set the correct > label: > >   # restorecon -v /etc/NetworkManager/dispatche

Re: Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

On Tue, May 17, 2022 at 1:07 PM Dario Lesca wrote: > After update to Fedora 36 I have a selinux problem with my personal > NetworkManager dispatcher script > > Into logs I get this error: > > mag 17 12:56:30 dodo.home.solinos.it audit[160270]: AVC avc: denied { > getattr }

Fedora 36: NetworkManager dispatcher: SELinux avc denied after update

After update to Fedora 36 I have a selinux problem with my personal NetworkManager dispatcher script Into logs I get this error: mag 17 12:56:30 dodo.home.solinos.it audit[160270]: AVC avc: denied { getattr } for pid=160270 comm="nm-dispatcher" path="/etc/NetworkManager/disp

NetworkManager IPv6 Router Advertisement tracking

How and where does NetworkManager track prefixes from Router Announcements? I recently changed my router advertisement to remove a prefix which previously had a 24 hour expiration on it. I thought I would be able to manually remove the removed prefix before expiration from the appropriate

Re: system upgrade from F28 to F31: problem with installed package NetworkManager-libnm

> Only skipping a single version is "supported". You should upgrade to > either F29 or F30 before going to F31. I would recommend F29 if you want > to get to F31 or else go to F30, then F32. Thanks, F28 -> F30 apparently works. ___ users mailing list

Re: system upgrade from F28 to F31: problem with installed package NetworkManager-libnm

go to F30, then F32. Problem: problem with installed package NetworkManager-libnm-1:1.10.12-3.fc28.x86_64 - package NetworkManager-libnm-1:1.20.10-1.fc31.x86_64 conflicts with NetworkManager-glib < 1:1.20.10-1.fc31 provided by NetworkManager-glib-1:1.10.12-3.fc28.x86_64 - package N

system upgrade from F28 to F31: problem with installed package NetworkManager-libnm

Hi, I would like to upgrade a system from F28 to F31. But I get the following error: Problem: problem with installed package NetworkManager-libnm-1:1.10.12-3.fc28.x86_64 - package NetworkManager-libnm-1:1.20.10-1.fc31.x86_64 conflicts with NetworkManager-glib < 1:1.20.10-1.fc31 provi

Re: NetworkManager stymies me again

On Mon, May 4, 2020 at 2:20 AM Tom Horsley wrote: > On Sun, 3 May 2020 14:45:49 -0700 > Samuel Sieb wrote: > >> I highly recommend using "nm-connection-editor". It's the official >> connection editor for NetworkManager. It's quite nice and gives you >> acce

Re: NetworkManager stymies me again

On 2020-05-04 08:19, Tom Horsley wrote: > On Sun, 3 May 2020 14:45:49 -0700 > Samuel Sieb wrote: > >> I highly recommend using "nm-connection-editor". It's the official >> connection editor for NetworkManager. It's quite nice and gives you >> access to

Re: NetworkManager stymies me again

On Sun, 3 May 2020 14:45:49 -0700 Samuel Sieb wrote: > I highly recommend using "nm-connection-editor". It's the official > connection editor for NetworkManager. It's quite nice and gives you > access to all the settings and connection types. But it gives absolutely z

Re: NetworkManager stymies me again

I used to setup the bridge: I highly recommend using "nm-connection-editor". It's the official connection editor for NetworkManager. It's quite nice and gives you access to all the settings and connection types. ___ users mailing lis

Re: NetworkManager stymies me again

On Sun, 3 May 2020 13:27:02 -0400 Tom Horsley wrote: > But, I've defined a bridge with (seemingly) all the > same properties as the fedora 31 bridge I created > with network-scripts, yet my virtual machines using > bridge networking never get an IP address, as if the > router dhcp server never

NetworkManager stymies me again

I was finally going to try to setup my network using nm in fedora 32. I figured after 10 years or so all the bits I use might finally work :-). But, I've defined a bridge with (seemingly) all the same properties as the fedora 31 bridge I created with network-scripts, yet my virtual machines using

Re: NetworkManager and PEERDNS=no

On Mon, 17 Feb 2020 13:16:16 -0500 Tom Horsley wrote: > I guess I'll poke around some more and see if I can figure > out what the delay is all about. Ah-HA! Need to turn off STP on the bridge: nmcli con modify br0 bridge.stp no The original web page mentioned I could do that, but didn't say

Re: NetworkManager and PEERDNS=no

e master with eth0 attached to it. I pretty much followed the instructions here: https://www.cyberciti.biz/faq/how-to-add-network-bridge-with-nmcli-networkmanager-on-linux/ It sort of works, but when I boot the system, there is no network at all for several seconds. I have time to run "ip addr&quo

Re: NetworkManager and PEERDNS=no

On Sun, Feb 16, 2020 at 8:37 PM Tom Horsley wrote: > > I keep seeing signs that "network" will someday disappear > entirely and I'll be forced to use NetworkManager, so the > first question I haven't been able to find an answer > for: > > What is the "prope

Re: NetworkManager and PEERDNS=no

On Sun, 2020-02-16 at 19:55 -0600, Robert G (Doc) Savage via users wrote: > There is no technical reason for AT to lock this down. I might > understand this for the VOIP and IPTV segments of the gateway. Those > probably have very complex and proprietary DHCP configurations. But > for the Internet

Re: NetworkManager and PEERDNS=no

; > 192.168.1.254, which is the gateway itself. I want to change that > > to > > 192.168.1.1 which is the static IP address for my Pi-Hole > > appliance. If > > I could, the Pi-Hole would become a stealthy and very effective > > whole-home ad blocker. > > Net

Re: NetworkManager and PEERDNS=no

is the static IP address for my Pi-Hole appliance. If I could, the Pi-Hole would become a stealthy and very effective whole-home ad blocker. NetworkManager allows you to set it to get your IP address by DHCP, but set your DNS manually. Have you tried

Re: NetworkManager and PEERDNS=no

On Sun, 2020-02-16 at 14:43 -0700, Joe Zeff wrote: > On 02/16/2020 02:39 PM, Robert G (Doc) Savage via users wrote: > > AT U-verse customers are forced to use the DNS service in their > > residential gateway, which would be fine for IPTV and VOIP > > sessions. > > How? Does the router block

Re: NetworkManager and PEERDNS=no

On Mon, 17 Feb 2020 06:47:42 +0800 Ed Greshko wrote: > # nmcli con mod net-eth0 ipv4.ignore-auto-dns yes Sounds like what I want, I've just resurrected an old system and installed f31 so I can try experimenting with network manager. I'll see how it goes. Thanks.

Re: NetworkManager and PEERDNS=no

On 2020-02-17 03:36, Tom Horsley wrote: > I keep seeing signs that "network" will someday disappear > entirely and I'll be forced to use NetworkManager, so the > first question I haven't been able to find an answer > for: > > What is the "proper" way to se

Re: NetworkManager and PEERDNS=no

On 02/16/2020 02:39 PM, Robert G (Doc) Savage via users wrote: AT U-verse customers are forced to use the DNS service in their residential gateway, which would be fine for IPTV and VOIP sessions. How? Does the router block outgoing DNS requests? ___

Re: NetworkManager and PEERDNS=no

DNS service, I need to know how to sidestep the U-verse DHCP's primary DNS designation. --Doc Savage Fairview Heights, IL On Sun, 2020-02-16 at 14:36 -0500, Tom Horsley wrote: > I keep seeing signs that "network" will someday disappear > entirely and I'll be forced to use Ne

Re: NetworkManager and PEERDNS=no

On Sun, 16 Feb 2020 14:36:42 -0500 Tom Horsley wrote: > I keep seeing signs that "network" will someday disappear > entirely and I'll be forced to use NetworkManager, so the > first question I haven't been able to find an answer > for: > > What is the "proper&q

NetworkManager and PEERDNS=no

I keep seeing signs that "network" will someday disappear entirely and I'll be forced to use NetworkManager, so the first question I haven't been able to find an answer for: What is the "proper" way to setup a network connection using nmcli which will get an IP via DHCP, but

Re: F28, openvpn, NetworkManager

On Mon, May 27, 2019 at 6:42 AM Mike Wright wrote: > On 5/26/19 10:59 PM, Jack Craig wrote: > > > , then vpn comes and > > > default route is now pointed at the vpn. > > > > > > and this process in reverse on shutdown... > > What I've

Re: F28, openvpn, NetworkManager

On 5/26/19 10:59 PM, Jack Craig wrote: On Sun, May 26, 2019 at 10:52 PM Ed Greshko > wrote: On 5/27/19 1:38 PM, Jack Craig wrote: > > > On Sun, May 26, 2019 at 10:17 PM Ed Greshko mailto:ed.gres...@greshko.com> >

Re: F28, openvpn, NetworkManager

On Sun, May 26, 2019 at 10:52 PM Ed Greshko wrote: > On 5/27/19 1:38 PM, Jack Craig wrote: > > > > > > On Sun, May 26, 2019 at 10:17 PM Ed Greshko > > wrote: > > > > On 5/27/19 12:17 PM, Jack Craig wrote: > > > i thought what i read was after nm brings up

Re: F28, openvpn, NetworkManager

starting here in the am, see policy based routing,... https://docs.fedoraproject.org/en-US/Fedora/24/html/Networking_Guide/index.html i think i will find what i crave there... On Sun, May 26, 2019 at 10:38 PM Jack Craig wrote: > > > On Sun, May 26, 2019 at 10:17 PM Ed Greshko > wrote: > >>

Re: F28, openvpn, NetworkManager

On 5/27/19 1:38 PM, Jack Craig wrote: > > > On Sun, May 26, 2019 at 10:17 PM Ed Greshko > wrote: > > On 5/27/19 12:17 PM, Jack Craig wrote: > > i thought what i read was after nm brings up the vpn, only then is the > default > route to > > vpn

Re: F28, openvpn, NetworkManager

On Sun, May 26, 2019 at 10:17 PM Ed Greshko wrote: > On 5/27/19 12:17 PM, Jack Craig wrote: > > i thought what i read was after nm brings up the vpn, only then is the > default route to > > vpn created. more, its torn down first on shutdown. > > > > i'm thinking along this line, ... > > > > >

Re: F28, openvpn, NetworkManager

On 5/27/19 12:17 PM, Jack Craig wrote: > i thought what i read was after nm brings up the vpn, only then is the > default route to > vpn created. more, its torn down first on shutdown. > > i'm thinking along this line, ... > >

Re: F28, openvpn, NetworkManager

i thought what i read was after nm brings up the vpn, only then is the default route to vpn created. more, its torn down first on shutdown. i'm thinking along this line, ... https://www.debuntu.org/how-to-network-manager-openvpn-overwrites-default-route/ On Sun, May 26, 2019 at 8:19 PM Ed

Re: F28, openvpn, NetworkManager

On 5/27/19 10:23 AM, Jack Craig wrote: > so, i have enp420 & tun0. when tun0 comes up, route are not properly update > for tun0 > routing. i think... > > default via 10.0.0.1 dev enp4s0 proto dhcp metric 100 > 10.0.0.0/24 via 10.0.0.1 dev enp4s0 proto static metric 2 >

Re: F28, openvpn, NetworkManager

so, i have enp420 & tun0. when tun0 comes up, route are not properly update for tun0 routing. i think... default via 10.0.0.1 dev enp4s0 proto dhcp metric 100 10.0.0.0/24 via 10.0.0.1 dev enp4s0 proto static metric 2 10.0.0.0/24 dev enp4s0 proto kernel scope link src 10.0.0.101 metric 100

Re: F28, openvpn, NetworkManager

On 5/27/19 9:34 AM, Jack Craig wrote: > anyone got openvpn doing proper route management with vpn start/stop? > > my take appears to suggest NM to be the problem, but short on proof. I had no problems on F28.  Now on F30 with no issues. You'll need to describe what problem you having. --

F28, openvpn, NetworkManager

hi all, anyone got openvpn doing proper route management with vpn start/stop? my take appears to suggest NM to be the problem, but short on proof. anyone? tia, jackc... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an

Re: NetworkManager not there after upgrade to fedora 30 [resolved]

~]$ rpm -qa | grep -i ^network NetworkManager-wwan-1.16.0-1.fc30.x86_64 NetworkManager-1.16.0-1.fc30.x86_64 NetworkManager-l2tp-1.2.12-1.fc30.x86_64 NetworkManager-libnm-1.16.0-1.fc30.x86_64 NetworkManager-libreswan-1.2.10-1.fc30.1.x86_64 NetworkManager-openvpn-1.8.10-1.fc30.x86_64 NetworkManager

Re: NetworkManager not there after upgrade to fedora 30

On 5/12/19 4:58 PM, Ed Greshko wrote: On 5/12/19 11:29 PM, Emmett Culley via users wrote: So what to I install to get Network manager back. FWIW, I have the following installed after an upgrade to F29 to F30 and no issues. [egreshko@meimei ~]$ rpm -qa | grep -i ^network NetworkManager-wwan

Re: NetworkManager not there after upgrade to fedora 30

On 5/12/19 11:29 PM, Emmett Culley via users wrote: > So what to I install to get Network manager back. FWIW, I have the following installed after an upgrade to F29 to F30 and no issues. [egreshko@meimei ~]$ rpm -qa | grep -i ^network NetworkManager-wwan-1.16.0-1.fc30.x86_64 NetworkMana

NetworkManager not there after upgrade to fedora 30

NetworkManager seems to have disappeared when I updated to Fedora 30. Not only didn't my network start on reboot after upgrade, there is no NetworkManager.service to enable or start with systemctl. Running dnf list NetworkManager replies: Last metadata expiration check: 0:16:45 ago on Sun

Re: Link-Local Only option not available on NetworkManager

the VPN configuration GUI.   (I don't use L2TP) >> >> On Xfce there is no IPv6 Tab during creation.  But, once created there is, >> and Link-local >> Only isn't an option. >> >> On KDE there is no IPv6 Tab on creation or after creation. >> > For m

Re: Link-Local Only option not available on NetworkManager

there is no IPv6 Tab on creation or after creation. For me, in KDE, in the networkmanager app that sits in the system tray to show the network connection, when I enter into edit mode, irrespective of whether I am editing an existing definition or creating a new definition there is both an IPv4 and IPv6

Re: Link-Local Only option not available on NetworkManager

On 11/8/18 5:54 PM, Paul Smith wrote: > On Fri, Nov 9, 2018 at 1:46 AM Rick Stevens wrote: >> >> If disabling SELinux fixes the connection issue, I'd sure-as-tootin' >> file a bugzilla about it. > I need to remove this phrase from my "it goes without saying" list. :-) > > As

Re: Link-Local Only option not available on NetworkManager

On 11/9/18 7:15 PM, Paul Smith wrote: > On Fri, Nov 9, 2018 at 2:36 AM Ed Greshko wrote: > In my experience, no, permissive mode does not disable all of SELinux's > blocks, and _especially_ stuff having to to with networking (including > pipes). It's always bothered me.

Re: Link-Local Only option not available on NetworkManager

On Fri, Nov 9, 2018 at 2:36 AM Ed Greshko wrote: > > >>> In my experience, no, permissive mode does not disable all of SELinux's > >>> blocks, and _especially_ stuff having to to with networking (including > >>> pipes). It's always bothered me. > >> Interesting. I've not run into this problem >

Re: Link-Local Only option not available on NetworkManager

On Fri, Nov 9, 2018 at 3:00 AM Ed Greshko wrote: > > > I have meanwhile filed a bug at Bugzilla against selinux-policy. > > Oh, whatever it is, it may be a duplicate of > https://bugzilla.redhat.com/show_bug.cgi?id=1641383 I do not know whether it is a duplicate or not. The bug I filed is the

  1   2   3   4   5   6   7   8   9   >