Excluding a group of interfaces

2015-01-19 Thread Eugene Yakubovich
Hello NM List,

I need to exclude a group of interfaces from being managed by NM. I'm
running Ubuntu and wanted to use /etc/network/interfaces in
conjunction with manged=false in [ifupdown] section. However I need NM
to ignore a whole bunch of interfaces based on the wildcard in the
name.

For example ignore all interfaces whose name starts with abc. I tried
adding iface abc* to /etc/network/interfaces but it seems like globs
are not supported. All these interfaces are veth devices so ignoring
by device type would also work.

Any help would be greatly appreciated.

Thanks,
Eugene
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Not sure on confirmation

2015-01-19 Thread Garrison Ricketson
Hello ,
 I just joined the mailinglist and am not sure if it confirmed all right.
My reason for joining the list is I have some problem with network
manager,not working. I will explain the details, if and when I am actually
on the list.
 Thank you


From Garry
http://www.garryricketsonartworks.com

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


New to debian, and the mail list

2015-01-19 Thread Garrison Ricketson

Hello every one,
 I am new to this mail list, also just a few days ago installed debian ,
 all though the install went fine, the only thing is network manger is
not working to well, it does pick up my broad band mobile usb device,
but does not pick up on the offices wifi or wlan connection, which is
what I want to use, the broadband usb device is very expensive for me,
and the office, wifi or wlan is free,  I do not know much about this,
and normally let everything configure automaticly.
 When I installed xubuntu on a different partition, the network
connections or manager worked fine, all I needed to do is put in the
password for the office modem, in the security part and it works fine.
 I would need to know what information anyone will need, if they have some
ideas, please let me know what is needed.
thanks
From Garry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Problems with routing

2015-01-19 Thread Thomas Haller
On Sat, 2015-01-17 at 17:44 +0300, Mustafa Muhammad wrote:
 Hi,
 I am trying to use NetworkManager with per interface routing and split
 routing tables, when I use network I can put the route in a file
 route-ifname with:
 default via 192.168.222.1 table rt2
 
 and it works, when I switched to using NM, this no longer work, I
 tried several times and found that I can use:
 192.168.222.0/0 via 192.168.222.1 table rt2
 
 but not default, is this a bug or am I missing something?

initscripts pass the lines from route-ifname directly to ip-route.
NetworkManager does not support all this flexibility, especially it
does not support specifying routing tables...


But... recently the following got merged, so if you use NetworkManager
from master, it might work for you:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6d5e62a3877491299654de99809e156fd348c549


The related bug on RHEL-7 is:
https://bugzilla.redhat.com/show_bug.cgi?id=1160013



If you use an older NetworkManger, you might get around it by using a
dispatcher script. Something like
https://bugzilla.redhat.com/show_bug.cgi?id=1160013#c3



Thomas


signature.asc
Description: This is a digitally signed message part
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Unavailable, managed device.

2015-01-19 Thread Léo Peltier
Hi,

I currently trying to get NM to handle a virtual wlan device and can't
get it to work. Its the second connection of an Intel 7260, the first
one being used as an access point managed outside of NM.

The OS is an Ubuntu Server 12.04 running NM 0.9.4.0-0ubuntu4.4.1
uname: 3.13.0-43-generic #72~precise1-Ubuntu SMP i686 i386

When I do everything manually through ip/iw/iwlist everything works fine
but I now need to integrate it with the rest of our software that
handles the network configuration using NM via DBus.

I create the iface using the following command:
 iw dev wlan0 interface add wlan1 type station

Here's what NM gives me:
 $ nmcli dev list iface wlan1
 GENERAL.DEVICE: wlan1
 GENERAL.TYPE:   802-11-wireless
 GENERAL.VENDOR: Intel Corporation
 GENERAL.PRODUCT:Wireless 7260
 GENERAL.DRIVER: iwlwifi
 GENERAL.HWADDR: F8:16:54:55:A5:9C
 GENERAL.STATE:  20 (unavailable)
 GENERAL.REASON: 2 (Device is now managed)
 GENERAL.UDI:
 /sys/devices/pci:00/:00:1c.5/:02:00.0/net/wlan1
 GENERAL.IP-IFACE:   
 GENERAL.NM-MANAGED: yes
 GENERAL.FIRMWARE-MISSING:   no
 GENERAL.CONNECTION: not connected
 CAPABILITIES.CARRIER-DETECT:no
 CAPABILITIES.SPEED: unknown
 WIFI-PROPERTIES.WEP:yes
 WIFI-PROPERTIES.WPA:yes
 WIFI-PROPERTIES.WPA2:   yes
 WIFI-PROPERTIES.TKIP:   yes
 WIFI-PROPERTIES.CCMP:   yes

Syslog:
 info (wlan1): using nl80211 for WiFi device control
 warn (wlan1): driver supports Access Point (AP) mode
 info (wlan1): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 28)
 info (wlan1): exported as /org/freedesktop/NetworkManager/Devices/4
 info (wlan1): now managed
 info (wlan1): device state change: unmanaged - unavailable (reason 
 'managed') [10 20 2]
 info (wlan1): bringing up device.
 info (wlan1): preparing device.
 info (wlan1): deactivating device (reason 'managed') [2]

I have [ifupdown] managed=false in my NetworkManager.conf and wlan1
does not appear in `/etc/network/interfaces`. Nothing is disabled in
`/var/lib/NetworkManager/NetworkManager.state`.

Can someone point me the right direction to get out of this
unavailable state?

Thanks.

-- 
Léo Peltier

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


New Austrian telecommunication service provider HoT

2015-01-19 Thread a b
Hi.

I've tested on a Linux Mint 17.1 system a new telecommunication service
provider with network-manager. I write to you since in my used
network-manager package (which has the version 0.9.8.8-0ubuntu7) this
service provider is not integrated until now.

*The system on which I've tested is the following:*
System: Kernel: 3.13.0-37-generic x86_64 (64 bit, gcc: 4.8.2)
Desktop: Gnome Distro: Linux Mint 17.1 Rebecca
Machine: System: Hewlett-Packard (portable) product: HP Pavilion 17
Notebook PC
Mobo: Hewlett-Packard model: 226A version: 73.25
HP Pavilion 17-f151ng (K0W64EA)
Bios: American Megatrends version: F.29 date: 08/14/2014
CPU: Quad core AMD A8-6410 APU with AMD Radeon R5 Graphics


*Information about this new service provider:*
Name: Hofer Telekom, HoT
Web: https://www.hot.at/
Country: Austria
Information regarding the APN:
https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf, page 1
I've attached the file /etc/NetworkManager/system-connections/

HoT Internet connection

Since I had problems with the stabillity (i.e. from ten connection tries
through network-manager only one connection could be established) I also
tried the connection directly through pppd. And this is much more stable
(i.e. 100% connection tries could be established). Cause of this I've
created these files:
 * chat-script file (location /etc/chatscripts): chatscript_hot_internet

 * peers file (location /etc/ppp/peers): peers_hot_internet
Also these files were attached.

I hope with this you have all the information to add this new service
provider to you package (in case it was not already done).

Regards
Oliver.


HoT
Description: Binary data


chatscript_hot_internet
Description: Binary data


peers_hot_internet
Description: Binary data
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Problems with routing

2015-01-19 Thread Mustafa Muhammad
Hi,
I am trying to use NetworkManager with per interface routing and split
routing tables, when I use network I can put the route in a file
route-ifname with:
default via 192.168.222.1 table rt2

and it works, when I switched to using NM, this no longer work, I
tried several times and found that I can use:
192.168.222.0/0 via 192.168.222.1 table rt2

but not default, is this a bug or am I missing something?

Regards
Mustafa Muhammad
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Unavailable, managed device.

2015-01-19 Thread Dan Williams
On Mon, 2015-01-19 at 16:40 +0100, Léo Peltier wrote:
 Hi,
 
 I currently trying to get NM to handle a virtual wlan device and can't
 get it to work. Its the second connection of an Intel 7260, the first
 one being used as an access point managed outside of NM.
 
 The OS is an Ubuntu Server 12.04 running NM 0.9.4.0-0ubuntu4.4.1
 uname: 3.13.0-43-generic #72~precise1-Ubuntu SMP i686 i386
 
 When I do everything manually through ip/iw/iwlist everything works fine
 but I now need to integrate it with the rest of our software that
 handles the network configuration using NM via DBus.

Some quick things that I can think of:

1) rfkill - what does 'rfkill list' say?
2) wpa_supplicant - is the supplicant running, and was it spawned with
the -u option?

Dan

 I create the iface using the following command:
  iw dev wlan0 interface add wlan1 type station
 
 Here's what NM gives me:
  $ nmcli dev list iface wlan1
  GENERAL.DEVICE: wlan1
  GENERAL.TYPE:   802-11-wireless
  GENERAL.VENDOR: Intel Corporation
  GENERAL.PRODUCT:Wireless 7260
  GENERAL.DRIVER: iwlwifi
  GENERAL.HWADDR: F8:16:54:55:A5:9C
  GENERAL.STATE:  20 (unavailable)
  GENERAL.REASON: 2 (Device is now managed)
  GENERAL.UDI:
  /sys/devices/pci:00/:00:1c.5/:02:00.0/net/wlan1
  GENERAL.IP-IFACE:   
  GENERAL.NM-MANAGED: yes
  GENERAL.FIRMWARE-MISSING:   no
  GENERAL.CONNECTION: not connected
  CAPABILITIES.CARRIER-DETECT:no
  CAPABILITIES.SPEED: unknown
  WIFI-PROPERTIES.WEP:yes
  WIFI-PROPERTIES.WPA:yes
  WIFI-PROPERTIES.WPA2:   yes
  WIFI-PROPERTIES.TKIP:   yes
  WIFI-PROPERTIES.CCMP:   yes
 
 Syslog:
  info (wlan1): using nl80211 for WiFi device control
  warn (wlan1): driver supports Access Point (AP) mode
  info (wlan1): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 28)
  info (wlan1): exported as /org/freedesktop/NetworkManager/Devices/4
  info (wlan1): now managed
  info (wlan1): device state change: unmanaged - unavailable (reason 
  'managed') [10 20 2]
  info (wlan1): bringing up device.
  info (wlan1): preparing device.
  info (wlan1): deactivating device (reason 'managed') [2]
 
 I have [ifupdown] managed=false in my NetworkManager.conf and wlan1
 does not appear in `/etc/network/interfaces`. Nothing is disabled in
 `/var/lib/NetworkManager/NetworkManager.state`.
 
 Can someone point me the right direction to get out of this
 unavailable state?
 
 Thanks.
 


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list