Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
One more thing... On Wed, September 30, 2015 3:28 pm, Derek Atkins wrote: > Dan, > > On Wed, September 30, 2015 12:44 pm, Dan Williams wrote: >> On Wed, 2015-09-30 at 12:25 -0400, Derek Atkins wrote: >>> Dan, >>> >>> Dan Williams writes: >>> >>> I.e., just to make sure I understand correctly, in order to get what I >>> want I should just create /etc/sysconfig/network-scripts/ifcfg-eth0:0 >>> and let NM manage my alias that way? Do I need to do anything special >>> to get NM to notice it, or it will do so automagically on the next >>> restart/reboot? >> >> There are some alias examples here, FWIW: >> >> http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/plugins/ifcfg-rh/tests/network-scripts >> >> And all that's really required is "nmcli con reload", you shouldn't ever >> need to restart NetworkManager to get config changes taken into account. > > I added this config file but it's not bringing up eth0:0. > > # cat /etc/sysconfig/network-scripts/ifcfg-eth0:0 > DEVICE=eth0:0 > IPADDR=192.168.x.y (yes, x.y are numbers) > BOOTPROTO=none > ONBOOT=yes > IPV6INIT=no > # > > What am I missing? Do I need the base ifcfg-eth0 file, too? (That file > was not created by anaconda). Or do I need some additional fields because > there is no ifcfg-eth0? Or do I need to tell NM to bring it up? Even after I add this file, I can't even manually "ifup" the interface! # nmcli con NAMEUUID TYPE DEVICE Wired connection 1 3a02edd8-e82d-4dca-a336-933e9177f4cd 802-3-ethernet eth0 # ifup eth0:0 Error: no device found for connection 'System eth0:0'. # nmcli con NAMEUUID TYPE DEVICE System eth0:0 81ad1dc6-9516-a6cf-73d9-600036a810a1 802-3-ethernet -- Wired connection 1 3a02edd8-e82d-4dca-a336-933e9177f4cd 802-3-ethernet eth0 # nmcli con reload # nmcli con NAMEUUID TYPE DEVICE Wired connection 1 3a02edd8-e82d-4dca-a336-933e9177f4cd 802-3-ethernet eth0 Even if I add a line NAME="System eth0:0" to the ifcfg-eth0:0 file, it still doesn't work... -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Dan, On Wed, September 30, 2015 12:44 pm, Dan Williams wrote: > On Wed, 2015-09-30 at 12:25 -0400, Derek Atkins wrote: >> Dan, >> >> Dan Williams writes: >> >> I.e., just to make sure I understand correctly, in order to get what I >> want I should just create /etc/sysconfig/network-scripts/ifcfg-eth0:0 >> and let NM manage my alias that way? Do I need to do anything special >> to get NM to notice it, or it will do so automagically on the next >> restart/reboot? > > There are some alias examples here, FWIW: > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/plugins/ifcfg-rh/tests/network-scripts > > And all that's really required is "nmcli con reload", you shouldn't ever > need to restart NetworkManager to get config changes taken into account. I added this config file but it's not bringing up eth0:0. # cat /etc/sysconfig/network-scripts/ifcfg-eth0:0 DEVICE=eth0:0 IPADDR=192.168.x.y (yes, x.y are numbers) BOOTPROTO=none ONBOOT=yes IPV6INIT=no # What am I missing? Do I need the base ifcfg-eth0 file, too? (That file was not created by anaconda). Or do I need some additional fields because there is no ifcfg-eth0? Or do I need to tell NM to bring it up? > Dan -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: AP with Radius and VLAN?
OK, thanks! -Frank On Wed, 30 Sep 2015 12:14:09 -0700, Dan Williams wrote: On Tue, 2015-09-29 at 21:37 -0700, Frank Rizzo wrote: Hey guys! I'm using Ubuntu 14.04 LTS, and using the applet I am able to do basic configuration of an AP. I can then start it, connect to it, and use it. But this base config is very simplistic. I need something more. I need Radius server authentication, and VLANs. (Things that are supported through hostapd). Does anyone have an example config that I can base mine upon? NetworkManager only supports wpa_supplicant's lightweight AP mode and is not intended as a full-fledged WiFi access point. For that, you'd want to configure & run hostapd itself, and make NM ignore the wifi interface through the config file and the "unmanaged-devices" key. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: AP with Radius and VLAN?
On Tue, 2015-09-29 at 21:37 -0700, Frank Rizzo wrote: > Hey guys! > > I'm using Ubuntu 14.04 LTS, and using the applet I am able to do basic > configuration of an AP. I can then start it, connect to it, and use it. > But this base config is very simplistic. I need something more. I need > Radius server authentication, and VLANs. (Things that are supported > through hostapd). > > Does anyone have an example config that I can base mine upon? NetworkManager only supports wpa_supplicant's lightweight AP mode and is not intended as a full-fledged WiFi access point. For that, you'd want to configure & run hostapd itself, and make NM ignore the wifi interface through the config file and the "unmanaged-devices" key. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
On Wed, 2015-09-30 at 12:25 -0400, Derek Atkins wrote: > Dan, > > Dan Williams writes: > > >> Could you explain more detail on how to add "label xxx" to the nmcli > >> command (which you inconveniently cut out of your reply, so I've > >> included it below)? I cannot find any reference to "label" in the nmcli > >> documentation. > >> > >> nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" > > > > If you really do need address labels (eg, interface aliases) then > > NetworkManager has limited support for them. If you don't truly need > > address labels, then I wouldn't use them. Anyway, NM supports address > > labels, but only when they are set via ifcfg "alias" files. They > > currently cannot be added via nmcli or set via the 'keyfile' plugin, > > though that's just a case of "didn't implement yet" rather than anything > > else. > > I.e., just to make sure I understand correctly, in order to get what I > want I should just create /etc/sysconfig/network-scripts/ifcfg-eth0:0 > and let NM manage my alias that way? Do I need to do anything special > to get NM to notice it, or it will do so automagically on the next > restart/reboot? There are some alias examples here, FWIW: http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/plugins/ifcfg-rh/tests/network-scripts And all that's really required is "nmcli con reload", you shouldn't ever need to restart NetworkManager to get config changes taken into account. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Dan, Dan Williams writes: >> Could you explain more detail on how to add "label xxx" to the nmcli >> command (which you inconveniently cut out of your reply, so I've >> included it below)? I cannot find any reference to "label" in the nmcli >> documentation. >> >> nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" > > If you really do need address labels (eg, interface aliases) then > NetworkManager has limited support for them. If you don't truly need > address labels, then I wouldn't use them. Anyway, NM supports address > labels, but only when they are set via ifcfg "alias" files. They > currently cannot be added via nmcli or set via the 'keyfile' plugin, > though that's just a case of "didn't implement yet" rather than anything > else. I.e., just to make sure I understand correctly, in order to get what I want I should just create /etc/sysconfig/network-scripts/ifcfg-eth0:0 and let NM manage my alias that way? Do I need to do anything special to get NM to notice it, or it will do so automagically on the next restart/reboot? > Dan -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: failure with bridge devices
On Wed, Sep 30, Dan Williams wrote: > Backwards compatibility, an intention to replicate the behavior of > various legacy network initscripts that had the same behavior (where eg > 'ifup br0' after boot didn't bring up slaves), and because it's not > always the case that you want every single slave configuration that > references 'br0' to be started when br0 starts. In general, NM tries to > be less destructive by default, and allow you to opt into destruction :) Just to emulate a buggy ifup? Not sure if our ifup even had a mode to leave slaves alone. I suggest to patch the buggy behaviour into the distro packages where needed, instead of having people patch the correct behaviour into the packages.. Olaf ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: failure with bridge devices
On Wed, 2015-09-30 at 09:59 +0200, Olaf Hering wrote: > Am 29.09.2015 um 13:21 schrieb Jirka Klimes: > > On Mon, 28 Sep 2015 09:05:02 +0200 > > Olaf Hering wrote: > >> So my questions: > >> Are there known bugs in the cooperation between NM and GNOME? > > I don't think there is a known serious issue. > > At least GNOME 3.16 is unable to do anything with bridges, except that > they can be configured. > > >> Are bridge devices fully supported? If so, why did NM not bringup > >> onboard before configuring bridge? > > Yes, bridge configurations are supported. You might got confused by > > the fact bringing up a bridge profile does not automatically bring up > > its slaves. Basically, you need to connect all slaves (bridge master > > will be connected as a dependency). > > > > But, as you have found there is a new property to influence the > > behaviour (connection.autoconnect-slaves). When you set it to '1' you > > can activate bridge and its slaves will be activated too. > > Why is it off by default? What is the point of that behaviour? Backwards compatibility, an intention to replicate the behavior of various legacy network initscripts that had the same behavior (where eg 'ifup br0' after boot didn't bring up slaves), and because it's not always the case that you want every single slave configuration that references 'br0' to be started when br0 starts. In general, NM tries to be less destructive by default, and allow you to opt into destruction :) (which might be new to some people, but that's the goal for the last 4 years or so) Dan > >> Below is the output of what I configured with 'nm-connection-editor'. > >> Why is that output even localized?! > > What is the issue with localization/no-localization? > > Its translated at the wrong layer. But after all, they also gave us > ~/Schreibtisch, ~/ビデオ, ~/Público and other odd directory names. So it > just makes sense to translate property names as well. I think in the > future we will get /proc/версия too... > > Olaf > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
On Wed, 2015-09-30 at 10:15 -0400, Derek Atkins wrote: > Andrei, > > Andrei Borzenkov writes: > > > 29.09.2015 20:54, Dan Williams пишет: > >> > >>> Basically I want to automate NM doing, effectively: > >>> > >>>ifconfig eth0:0 192.168.x.y > >> > >> Don't do this with interface aliases; the kernel is perfectly capable of > >> using more than one address on the same interface. Simply do: > >> > >> ip addr add 192.168.x.y/24 dev eth0 > >> > >> and magically you'll have two. > >> > > > > > > This makes addresses invisible in ifconfig output and that may confuse > > legacy software (I know about at least one such case). Adding "label > > xxx" will emulate legacy aliases enough to make them appear as > > "normal" interface. > > Could you explain more detail on how to add "label xxx" to the nmcli > command (which you inconveniently cut out of your reply, so I've > included it below)? I cannot find any reference to "label" in the nmcli > documentation. > > nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" If you really do need address labels (eg, interface aliases) then NetworkManager has limited support for them. If you don't truly need address labels, then I wouldn't use them. Anyway, NM supports address labels, but only when they are set via ifcfg "alias" files. They currently cannot be added via nmcli or set via the 'keyfile' plugin, though that's just a case of "didn't implement yet" rather than anything else. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
On Wed, 2015-09-30 at 06:26 +0300, Andrei Borzenkov wrote: > 29.09.2015 20:54, Dan Williams пишет: > > > >> Basically I want to automate NM doing, effectively: > >> > >>ifconfig eth0:0 192.168.x.y > > > > Don't do this with interface aliases; the kernel is perfectly capable of > > using more than one address on the same interface. Simply do: > > > > ip addr add 192.168.x.y/24 dev eth0 > > > > and magically you'll have two. > > > > > This makes addresses invisible in ifconfig output and that may confuse > legacy software (I know about at least one such case). Adding "label > xxx" will emulate legacy aliases enough to make them appear as "normal" > interface. Yes, that is a downside. However, the kernel functionality underlying this, address labels, is only for tricking ifconfig. The alias interfaces are not normal interfaces and changes made to them affect all other alias interfaces. No other tools present this view of the world, and the upstream kernel is only keeping this functionality for backwards compatibility. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Andrei, Andrei Borzenkov writes: > 29.09.2015 20:54, Dan Williams пишет: >> >>> Basically I want to automate NM doing, effectively: >>> >>>ifconfig eth0:0 192.168.x.y >> >> Don't do this with interface aliases; the kernel is perfectly capable of >> using more than one address on the same interface. Simply do: >> >> ip addr add 192.168.x.y/24 dev eth0 >> >> and magically you'll have two. >> > > > This makes addresses invisible in ifconfig output and that may confuse > legacy software (I know about at least one such case). Adding "label > xxx" will emulate legacy aliases enough to make them appear as > "normal" interface. Could you explain more detail on how to add "label xxx" to the nmcli command (which you inconveniently cut out of your reply, so I've included it below)? I cannot find any reference to "label" in the nmcli documentation. nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" Thanks, -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: failure with bridge devices
Am 29.09.2015 um 13:21 schrieb Jirka Klimes: > On Mon, 28 Sep 2015 09:05:02 +0200 > Olaf Hering wrote: >> So my questions: >> Are there known bugs in the cooperation between NM and GNOME? > I don't think there is a known serious issue. At least GNOME 3.16 is unable to do anything with bridges, except that they can be configured. >> Are bridge devices fully supported? If so, why did NM not bringup >> onboard before configuring bridge? > Yes, bridge configurations are supported. You might got confused by > the fact bringing up a bridge profile does not automatically bring up > its slaves. Basically, you need to connect all slaves (bridge master > will be connected as a dependency). > > But, as you have found there is a new property to influence the > behaviour (connection.autoconnect-slaves). When you set it to '1' you > can activate bridge and its slaves will be activated too. Why is it off by default? What is the point of that behaviour? >> Below is the output of what I configured with 'nm-connection-editor'. >> Why is that output even localized?! > What is the issue with localization/no-localization? Its translated at the wrong layer. But after all, they also gave us ~/Schreibtisch, ~/ビデオ, ~/Público and other odd directory names. So it just makes sense to translate property names as well. I think in the future we will get /proc/версия too... Olaf ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: failure with bridge devices
Am 29.09.2015 um 13:25 schrieb Jirka Klimes: > On Mon, 28 Sep 2015 19:18:12 +0200 > Olaf Hering wrote: > >> Am 28.09.2015 um 09:05 schrieb Olaf Hering: >>> connection.autoconnect-slaves: -1 (default) >> >> Did I miss that knob in the GUI? Setting it to 1 with >> "nmcli connection edit bridge" seems to fix the "up" command. > > You have to use nmcli to configure that. > I think, there is no knob in the GUI. It seems that it should be added. What is the purpose of the current state? I mean, how does one start a configured bridge? Olaf ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
