AP with Radius and VLAN?
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? Thanks! -Frank ___ 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)?
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. ___ 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 Tue, 2015-09-29 at 12:16 -0400, Derek Atkins wrote: > Hi, > > I've got an esoteric NM question. I've got two distinct networks that > share an ethernet fabric (poor man's vlans). I have a F22 server that I > want to put on both networks. It's currently configured to use DHCP for > the primary network (and my DHCP server provides a static address). > > AFAICT there's really no way to get DHCP to provide two addresses, so > I'd like to set up a secondary IP statically using nmcli (I did say this > was a server, right?) Correct. DHCPv4 cannot provide more than one IP address. (DHCPv6 can, however). > 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. > I know I can add a second IP to eth0 via: > > nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" This is exactly what you do. Keep the ipv4.method = "auto" however, that's how DHCP gets signaled. > But I have no idea how this would interact with the primary address > being obtained by DHCP. What should happen is that DHCP will provide everything it currently does, including the primary IP address, gateway, DNS, etc, and the only change will be that a second IP address is added to the interface. You won't see this address with ifconfig though, because it's stupid. Use /sbin/ip to see it. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Hi, I've got an esoteric NM question. I've got two distinct networks that share an ethernet fabric (poor man's vlans). I have a F22 server that I want to put on both networks. It's currently configured to use DHCP for the primary network (and my DHCP server provides a static address). AFAICT there's really no way to get DHCP to provide two addresses, so I'd like to set up a secondary IP statically using nmcli (I did say this was a server, right?) Basically I want to automate NM doing, effectively: ifconfig eth0:0 192.168.x.y I know how I would do this using the old /etc/sysconfig/networking config files, but I have NO CLUE how to do with with nmcli. I've spent the last hour googling and reading about it and still haven't figured it out, yet. I suppose I could just add something to rc.local, but I'd rather do it the "right way" (and maybe learn something along the way). I know I can add a second IP to eth0 via: nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" But I have no idea how this would interact with the primary address being obtained by DHCP. So, what nmcli magic command(s) do I need to run to do what I want? 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
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. Jirka ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: failure with bridge devices
On Mon, 28 Sep 2015 09:05:02 +0200 Olaf Hering wrote: > I'm running openSUSE Tumbleweed, with GNOME 3.16.2 and NM 1.0.6, and > have odd issues with networking. > > Initially GNOME automatically configured the onboard ethernet and > named it "Wired Connection 1". I added a few VPN connections and all > was fine. > > A few weeks later I finally got around to reenable my winxp-tax VM. > For this I needed a bridge. The GNOME UI is appearently unable to > handle bridge. I was unable to get online, under the hood only the > onboard connection was enabled. > > Later I found nm-connection-editor. This showed the bridge devices > etc. But in the end, since both seem to disagree about what is > configured, I removed the related config files from > /etc/NetworkManager/system-connections, used nm-connection-editor to > configure a bridge with the onboard ethernet. After a reboot it > finally worked. The GNOME UI is still unable to recognize the bridge > connection. But in the end I was able to run the VM and all was fine > again. > > > With todays TW snapshot the IPv4 part of the connection did not get > up. I found the nmcli command. It showed the bridge is online, but no > IPv4 route was set. Dowing down and up showed that only the bridge > came up, but not the onboard device. Trying the GNOME UI did not get > a connection either. > > To my surprise, once I ran 'nmcli connection up bridge' the > established onboard connection from GNOME changed something, now the > bridge came up fine including IPv4. Up to now only IPv6 was usable to > get outside. > > > So my questions: > Are there known bugs in the cooperation between NM and GNOME? I don't think there is a known serious issue. > 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. > Does NM rely on the iproute2 package in any way? > NetworkManager does not use iproute2 package, but NETLINK interface to the kernel. > 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? Jirka ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
