Re: NM removes default route installed by zebra

ave alluded to the requirement rather than suggesting a mechanism. My apologies for intruding upon your mailing list. Regards, glen -- Glen Turner Web: <http://www.gdt.id.au/~gdt/>___ networkmanager-list mailing list networkmanager-list@

Re: NM removes default route installed by zebra

erent forwarding table is the simplest way (using the ifcfg-..., rule-... and route-... files). -glen -- Glen Turner Web: <http://www.gdt.id.au/~gdt/> ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: is anyone actually still using WiMAX

On Friday, Stuart Longland wrote: > Probably worth pointing out, here in Australia there's been a move to > get better Internet coverage in rural areas using fixed-wireless broadband. > > There's talk of that being based on "WiMAX 2", so there could be more > demand for WiMAX support in Linux in

Re: Ensuring predictable MAC address for bond interface

> > Yes, I like this approach much better: let the user specify the MAC address > for the bond, use that address when creating the bond, and be done with it. > Then the carrier state, the order of enslaving devices, etc. are all > irrelevant. Perhaps also a button to easily generate a locally-

Re: Link MTU option ignored in IPv6 router advertisements

On 04/10/2014, at 2:31 AM, Dan Williams wrote: > On Fri, 2014-10-03 at 11:36 -0400, Chuck Anderson wrote: >> I'm not sure if this is a kernel thing or a NetworkManager thing. Did >> something change in how IPv6 router advertisements are handled by >> NetworkManager in Fedora 20? > > I think it'

Re: Software to test MAC address privacy

the system and then that Interface ID is retained for the lifetime of the machine or until sysadmin action). See http://www.rfc-editor.org/rfc/rfc7217.txt Best wishes with your project, glen PS: probably best to move any further discussion off-list. -- Glen Turner <http://

Re: Software to test MAC address privacy

On 19/07/2014 Robert Moskowitz wrote: > Actually the standard uses the first 2 bits for this. It is called local > scope MAC addresses. This leaves 46 bits for the random content. Thus if you > have a network of 1 devices the probablity of a collision is 7x10^-7 Hello Robert, Not all local

Re: RFC: standardized network provisioning

n It is XML, so should be importable. Please be careful in the help text to say what you are importing, as a .mobileconfig can set up many different things (such as your authentication, file shares to mount, and so on). Cheers, glen -- Glen Turner <http://www

Re: random MAC addresses for scanning

point for another. If you present a differing MAC address to each AP then we can't maintain your connectivity. -glen -- Glen Turner <http://www.gdt.id.au/~gdt/> ___ networkmanager-list mailing list networkmanager-list@gnome.org https:

Re: ping_test

network administration to actually fix the issue. I hope this mail suggests that NetworkManager is part of a network ecosystem and for this particular feature fitting into the ecosystem well is vital and needs close consideration. -glen --

Re: MM 0.6.0 conflicts with USB GPS device?

> > ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port As a workaround, set up a udev rule to: - set the group and mode on the device - create a non-changing symlink name to the changing device name - tell ModemManager not to touch the device Create a file, say /etc/udev/rules.d/99-loc

Request: log NMEI and E.164 number of mobile broadband devices

could - log the serial number and NMEI of broadband modem+SIM after it is detected - log the E.164 calling number once a connection is established. Thank you, Glen -- Glen Turner www.gdt.id.au/~gdt ___ networkmanager-list mailing list netw