Re: ethernet connection
I don't see any use of such feature. As long as both connections are DHCP-based, you don't need to bother where you are. And, as far as I remember, your mac-address is not assigned --- it's hardcoded to your network device. There's very little advantage on changing it, IMHO. Maybe if you explain a little more what do you want to do? Em qua., 12 de fev. de 2020 às 18:37, escreveu: > Is there a way to configure two wired connections. One for my home > network (assigned-mac-address=permanent) and one for all other wired > connections (assigned-mac-address=random) in a manner at which > networkmanager autodetects if the wired connection is at my home > network? > > -- > > Jaap van Wingerde > e-mail: r...@shrl.nl > > ___ > 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: NM changes DHCP address too easily
2016-04-25 2:24 GMT-03:00 matti kaasinen : > dhcpd3 > > Sorry. I didn't make myself clear. Which device is your DHCP server? A router (maybe wifi)? A dedicated/generic router? A server? How many free leases the DHCP server have, now? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM changes DHCP address too easily
2016-04-22 11:59 GMT-03:00 matti kaasinen : > > 2016-04-22 17:07 GMT+03:00 José Queiroz : > >> Shouldn't the DHCP address be managed by the DHCP server? Even if the >> client releases the previous lease, the server should send the same address >> on the next DISCOVER, as long as it is free, that's the recommended server >> behaviour. > > I would like that bhaviour, indeed. However, reality is that DHCP server > works like that with board supervised with Connman but not with NM. I have > tried to make NM and Connman client settings to look exactly the same to > DHCP server like for instance dhcp-client-identifier - based on MAC > address. Everyting seems identical from DHCP server lease log and I can't > see difference with Wireshark. Unfortunately I have not got traced that > event that changes IP address. > > Who is your network's DHCP server? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bonding wifi and wired
2016-03-08 14:30 GMT-03:00 Dan Williams : > > I know it's been done before, but one caveat is that the wifi driver > and the supplicant have to correctly support setting the WiFi device's > MAC address since bonding requires they have the same one. That's been > a problem in the past and required fixes to the supplicant and drivers. > But yeah, I'm sure we'd take patches fixing anything on the NM side. > > Hi Dan, And what about if NM assume this to be done based on the WiFi's MAC? This way we could use this feature despite the drive in use... ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Don't connect to specific *wired* networks?
2015-12-10 16:37 GMT-02:00 Dan Williams : > On Thu, 2015-12-10 at 15:37 -0200, José Queiroz wrote: > > 2015-12-10 14:55 GMT-02:00 Dan Williams : > > > > > On Thu, 2015-12-10 at 08:06 -0800, Nikolaus Rath wrote: > > > > Hello, > > > > > > > > Is there a way to prevent NetworkManager from automatically > > > > connecting > > > > to specific *wired* networks? > > > > > > > > I think the network could be identified by the presence (or > > > > absence) > > > > of > > > > specific MACs, but I'd be open to other suggestions as well. > > > > > > That's the best option for now, but of course there are security > > > issues > > > with that since any MAC address can be spoofed. There are vague > > > plans > > > to attempt to automatically identify wired networks by listening to > > > the > > > wire for a few seconds and detecting 802.1x EAP-Request Identity > > > packet > > > s or ARPing a specific IP address and matching the returned MAC. > > > This > > > feature would have to be opt-in because obviously it would delay > > > network connections. > > > > > > If that's something you'd be willing to work on, that would be > > > great... > > > what do you say? :) > > > > > > Dan > > > > > > > > > What about using IPv6 RA messages to do that? > > This could be another check among many, yes. Though to prevent DoS > most routers have a configured minimum advertisement interval which > could be much longer than a few seconds. > > Dan > What if the workstation send a RS before? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Don't connect to specific *wired* networks?
2015-12-10 14:55 GMT-02:00 Dan Williams : > On Thu, 2015-12-10 at 08:06 -0800, Nikolaus Rath wrote: > > Hello, > > > > Is there a way to prevent NetworkManager from automatically > > connecting > > to specific *wired* networks? > > > > I think the network could be identified by the presence (or absence) > > of > > specific MACs, but I'd be open to other suggestions as well. > > That's the best option for now, but of course there are security issues > with that since any MAC address can be spoofed. There are vague plans > to attempt to automatically identify wired networks by listening to the > wire for a few seconds and detecting 802.1x EAP-Request Identity packet > s or ARPing a specific IP address and matching the returned MAC. This > feature would have to be opt-in because obviously it would delay > network connections. > > If that's something you'd be willing to work on, that would be great... > what do you say? :) > > Dan > What about using IPv6 RA messages to do that? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Priorize one AP or other
Hi, I'm almost sure that someone, in the past, asked this. Imagine that you're working on a ESS, where one of the APs is pretty stable, and the other is older, slower, and falty. But, for some reason, NM seems to prefer to connect to the last one, even when it's signal is weaker than the other. Is there any way to tell NM to connect to the first one, and only roam to the other if the first is unavailable? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: AP Mode Support?
2012/6/5 Sérgio Basto > On Ter, 2012-06-05 at 12:00 -0300, José Queiroz wrote: > > Yeah, thats the point. Hope this will get available to other systems > > soon. > > but this depends on drives , for example mine iwlwifi (Intel wireless > something) doesn't have AP mode (with kernel 3.3.7) , so I can't enable > it. > > Neither mine... iwlagn. Probably I'll buy an usb wifi adapter with a suitable chipset (seems that atheros and broadcom will do the trick). you may try hostapd > rpm -q hostapd > hostapd-0.7.3-5.fc17.x86_64 > http://w1.fi/hostapd > http://wireless.kernel.org/en/users/Documentation/hostapd > > I'm using Kubuntu [10.04] right now; it seems to have hostapd on the repositories. But all the tutorials to install/configure it seem to instruct disabling NM, I don't want to do it. I want to keep NM working, so it's easier to share a 3G connection to wifi enabled devices. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: AP Mode Support?
Yeah, thats the point. Hope this will get available to other systems soon. 2012/6/5 Sérgio Basto > On Ter, 2012-06-05 at 01:18 -0300, José Queiroz wrote: > > Sorry if this is a repeated question. > > > > Is there any support for AP mode on NM, provided the NIC driver > > supports it? > > > > If not, is there any plan on adding this on some near future? > > > > Thanks for the attention. > > > https://fedoraproject.org/wiki/Features/RealHotspot > > I think that is what you are asking, F18 will be available (as stable) > at November , but you can test it soon . > > > -- > Sérgio M. B. > > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
AP Mode Support?
Sorry if this is a repeated question. Is there any support for AP mode on NM, provided the NIC driver supports it? If not, is there any plan on adding this on some near future? Thanks for the attention. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN
2012/5/29 Daniel Ackwonu > Hello! > > My name is Daniel and I am using Ubuntu on a new HP notebook. I have got > the problem that my Realtek Wlan card(RTL8111) is not recognized by my > operating system. I have tried a few things but it is still not working. If > one of you could help that would be great. > Thank you. > >> iwconfig >> lono wireless extensions. >> >> eth0 no wireless extensions. >> >> vboxnet0 no wireless extensions. >> > > Hello Daniel, Have you posted this on the Ubuntu Forum? http://ubuntuforum.org You may also try to use the command below to find out which hardware you have, and whether their drivers are correctly loaded. sudo lshw -C network ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless disabled by hardware
Hi Felipe, 2012/5/12 Felipe Alcubillas > I'm using ubuntu 10.10. I can't connect to wifi. I've tried everything > (trust me, I REALLY read everything I could at forums and tried a thousand > times) but I just can't solve this problem. How can I enable my wifi again? > > Are you using a Dell or Acer notebook? If this is the case, there are some modules that cause this behaviour on Ubuntu, and need to be blocked. > Thanks, > > Felipe > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: iptables rules
In fact, you should plan your firewall policy a little better. You have two systems doing exactly the same thing. Is this really necessary? Em 9 de março de 2012 18:41, rob stone escreveu: > Please ignore previous e-mail. > I have found the "problem". The firestarter firewall alters iptables > when it is launched. All I have to do is alter the init.d sequences so > my script starts last. > > Cheers, > Rob > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: how to get 3g modem back in managed state
Try to SIGTERM modem-manager. *sudo killall -TERM modem-manager* 2011/12/29 Eduard Hasenleithner > I'm using network-manager on ubuntu oneiric. Every time the modem gets > disconnected (either by the network, or due to bad reception) it > disappears from the network device list. > > Dec 29 18:17:28 eeepc pppd[2070]: LCP terminated by peer > Dec 29 18:17:28 eeepc pppd[2070]: Connect time 1.4 minutes. > Dec 29 18:17:28 eeepc pppd[2070]: Sent 47182 bytes, received 339954 bytes. > Dec 29 18:17:28 eeepc charon: 08[KNL] interface ppp0 deactivated > Dec 29 18:17:28 eeepc charon: 08[KNL] 10.61.6.235 disappeared from ppp0 > Dec 29 18:17:28 eeepc pppd[2070]: Modem hangup > Dec 29 18:17:28 eeepc pppd[2070]: Connection terminated. > Dec 29 18:17:28 eeepc NetworkManager[666]: (ttyUSB0): device > state change: activated -> failed (reason 'ppp-disconnect') [100 120 > 13] > Dec 29 18:17:28 eeepc NetworkManager[666]: Activation (ttyUSB0) > failed. > Dec 29 18:17:28 eeepc avahi-daemon[526]: Withdrawing workstation > service for ppp0. > Dec 29 18:17:28 eeepc modem-manager[519]: (ttyUSB0) closing > serial port... > Dec 29 18:17:28 eeepc modem-manager[519]: (ttyUSB0) serial port > closed > Dec 29 18:17:28 eeepc modem-manager[519]: Modem > /org/freedesktop/ModemManager/Modems/0: state changed (connected -> > disconnecting) > Dec 29 18:17:28 eeepc modem-manager[519]: Modem > /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting > -> connected) > Dec 29 18:17:28 eeepc NetworkManager[666]:SCPlugin-Ifupdown: > devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0) > Dec 29 18:17:28 eeepc NetworkManager[666]: (ttyUSB0): now unmanaged > Dec 29 18:17:28 eeepc NetworkManager[666]: (ttyUSB0): device > state change: failed -> unmanaged (reason 'removed') [120 10 36] > Dec 29 18:17:28 eeepc NetworkManager[666]: (ttyUSB0): > deactivating device (reason 'removed') [36] > Dec 29 18:17:28 eeepc dbus[488]: [system] Activating service > name='org.freedesktop.nm_dispatcher' (using servicehelper) > Dec 29 18:17:28 eeepc NetworkManager[666]: could not read ppp > stats: No such device > > Is there a way to get it back without a reboot? > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: how to use NetworkManager in ubuntu 10.04
2011/11/21 金 晓烨 > I want to develop an application run in ubuntu 10.04 and this application > may have some IPC with the NetworkManager. > When i installed the NetworkManager 0.9.20 after "./configure" "make > check" "make install" "make installcheck" it is all clear ,but then i can > not get my eth device information with"ifconfig" and get into the Internet. > I use "ps -aux"can find that the nm-applet is running, but there must have > some mistakes for me, when i use the tool provided in "use/local/bin/"like > nmcli the terminal`s output is that "./nmcli: error while loading shared > libraries: libnm-util.so.2: cannot open shared object file :No such file or > directory" > Is that device`s driver problem? how can i fix it. > > Ubuntu 10.04 LTS comes with NM 0.8 (afaik 0.8.1). Did you remembered uninstalling it before installing NM 0.9? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-connection-editor working only as root
Ramon, did you ever tried to set up a new user, and see if the same problem happens with it? If it happens, then the problem surely is in NM; but if not, then the problem is in your profile... 2011/11/6 Ramon Diaz-Uriarte > > > > On Fri, 04 Nov 2011 11:12:09 -0500,Dan Williams wrote: > > On Fri, 2011-11-04 at 11:48 +0100, Ramon Diaz-Uriarte wrote: > > > > > > > > > On Wed, 02 Nov 2011 20:31:41 -0500,Dan Williams > wrote: > > > > On Mon, 2011-10-24 at 11:48 +0200, Ramon Diaz-Uriarte wrote: > > > > > Actually, three problems remain ;-). > > > > > > > > > > > > > > > 1. I've rebooted and reloged in several times, but I cannot save a > > > > > connection because it complaints about insufficient privileges. (I > get a > > > > > pop-up message that says "Connection add failed", "Insufficient > > > > > privileges"). > > > > > > > > > > > > > > > I have logged with kdm (or gdm) and have a local session: > > > > > > > > > > ramon@Bufo:~$ ck-list-sessions > > > > > Session1: > > > > > unix-user = '1000' > > > > > realname = 'ramon diaz-uriarte' > > > > > seat = 'Seat1' > > > > > session-type = '' > > > > > active = TRUE > > > > > x11-display = ':0' > > > > > x11-display-device = '/dev/tty7' > > > > > display-device = '' > > > > > remote-host-name = '' > > > > > is-local = TRUE > > > > > on-since = '2011-10-23T16:29:00.632372Z' > > > > > login-session-id = '4294967295' > > > > > > > Is this an update or a new connection? This error is coming from > > > > PolicyKit, so does this work if you edit the file: > > > > > > > > /usr/share/polkit-1/actions/org.freedesktop.network-manager-settings.system.policy > > > > > > > and change the following hunk to: > > > > > > >id="org.freedesktop.network-manager-settings.system.modify"> > > > > <_description>Modify system connections > > > > <_message>System policy prevents modification of system > settings > > > > > > > > yes > > > > auth_admin_keep > > > > > > > > > > > > > > > then try. If that doesn't work, change it to: > > > > > > >id="org.freedesktop.network-manager-settings.system.modify"> > > > > <_description>Modify system connections > > > > <_message>System policy prevents modification of system > settings > > > > > > > > yes > > > > yes > > > > > > > > > > > > > > > no reboot or anything is necessary, the changes take effect > immediately. > > > > > > > > > I tried both (note: there were minor differences in syntax, like mine > is > > > called NetworkManager, not network-manager, etc). > > > > > > The first one did not work, but the second did. Thanks a lot. > > > Ok, this is good to know. We now know that your user was marked as > > 'active' via ConsoleKit (which PolicyKit talks to) but for some reason > > PolicyKit wasn't able to show the authentication dialog. If you're > > using a GNOME desktop, do you have the > > "polkit-gnome-authentication-agent-1" program anywhere in /usr/libexec > > or /usr/lib or /usr/lib64 or /usr/bin ? If you're not on a GNOME > > desktop, do you ever see PolicyKit authentication dialogs? > > > I do not use GNOME, but I tested it here. This is what happens: > > - If I use GNOME, then the first version > > yes > auth_admin_keep > > > works. When I try to add a connection with security, or to modify > an existing one, I am prompted for the root password, and then I can > modify, etc. > > Yes, I do have polkit-gnome-authentication-agent-1 in > /usr/lib/policykit-1-gnome/ > > > > - If I do not use GNOME (I use xmonad), then I need the second version > > yes > yes > > to be able to modify, add, etc. Otherwise, I get a message saying that I do > not have sufficient privileges. > > No, I never see a PolicyKit authentication dialog. However, in case it > matters, I do have the daemon running: > > > ramon@Bufo:~$ ps -A -f | grep polkit > root 1487 1 0 12:00 ?00:00:01 > /usr/lib/policykit-1/polkitd > > > and a bunch of dbus-related stuff: > > ramon@Bufo:~$ ps -A -f | grep dbus > 101 1468 1 0 12:00 ?00:00:02 /usr/bin/dbus-daemon > --system > ramon10239 10197 0 12:59 ?00:00:00 /usr/bin/ssh-agent > /usr/bin/dbus-launch --exit-with-session /bin/bash /home/ramon/.xsession > ramon10242 1 0 12:59 ?00:00:00 /usr/bin/dbus-launch > --exit-with-session /bin/bash /home/ramon/.xsession > ramon10243 1 0 12:59 ?00:00:00 /usr/bin/dbus-daemon > --fork --print-pid 5 --print-address 7 --session > > > > > Best, > > > R. > > > > > Best, > > > > > > > > > R. > > > > > > > > > > > > > Dan > > > > > > > > > > > > > 2. There is the problem of not being able to access my previously > defined > > > > > connections (versions 0.8.1). They must be somewhere, but the new > versions > > > > > do not seem to be able to find them. > > > > > > > > > > > > > > > > > > > > 3. Finally, connections saved using, say, gksudo >
Re: nm-connection-editor working only as root
Em 24/10/2011 07:48, "Ramon Diaz-Uriarte" escreveu: > > > Actually, three problems remain ;-). > > > 1. I've rebooted and reloged in several times, but I cannot save a > connection because it complaints about insufficient privileges. (I get a > pop-up message that says "Connection add failed", "Insufficient > privileges"). Seems that you've left files owned by root in your profile. Try to chmod all your home directory back to your user. > > > I have logged with kdm (or gdm) and have a local session: > > ramon@Bufo:~$ ck-list-sessions > Session1: >unix-user = '1000' >realname = 'ramon diaz-uriarte' >seat = 'Seat1' >session-type = '' >active = TRUE >x11-display = ':0' >x11-display-device = '/dev/tty7' >display-device = '' >remote-host-name = '' >is-local = TRUE >on-since = '2011-10-23T16:29:00.632372Z' >login-session-id = '4294967295' > > > 2. There is the problem of not being able to access my previously defined > connections (versions 0.8.1). They must be somewhere, but the new versions > do not seem to be able to find them. > > > > 3. Finally, connections saved using, say, gksudo nm-connection-editor are > stored under > /etc/NetworkManager/system-connections > > with passwords, etc, as plain text. Sure, they are only readable to root, > but ssn't this a potential problem? If I remember correctly, with previous > versions, you could only access connections (and their passwords) after > entering your password via keyring. > > > Best, > > R. > > > > On Fri, 21 Oct 2011 22:17:01 +0200,Ramon Diaz-Uriarte wrote: > > > > > On Fri, 21 Oct 2011 21:16:25 +0200,Michael Biebl wrote: > > > [1 ] > > > Am 21.10.2011 21:14, schrieb Ramon Diaz-Uriarte: > > > > > > > > > > > > On Fri, 21 Oct 2011 16:42:52 +0200,Michael Biebl wrote: > > > >> Am 21.10.2011 13:44, schrieb Ramon Diaz-Uriarte: > > > > > > > >> What's the output of ck-list-sessions? > > > > > > > > > > > > Session5: > > > > active = FALSE > > > > is-local = FALSE > > > > That's your problem. Use a login manager, like gdm or kdm, which > > > properly registers a ConsoleKit session. > > > Otherwise the PolicyKit rules used by NM won't work. > > > Login with gdm does work, but only partially. I can now add and edit > > connections as non-root (ck-list-sessions now lists two local > > sessions). But the long list of wireless connections I had defined (prior > > to 0.9) is not there. Is there anyway to get those back? > > > > As well, can I get the PolicyKit rules to work with other login managers? > > I use wdm, but the trick of adding > > > exec ck-launch-session xmonad > > > at the end of my .xinitrc does not seem to work. > > > > Thanks, > > > > R. > > > > > > > Michael > > > > -- > > > Why is it that all of the instruments seeking intelligent life in the > > > universe are pointed away from Earth? > > > > [2 OpenPGP digital signature ] > > > -- > > Ramon Diaz-Uriarte > > Department of Biochemistry > > Universidad Autónoma de Madrid > > Spain > > > http://ligarto.org/rdiaz > > > Temporarily at: > > Structural Biology and Biocomputing Programme > > Spanish National Cancer Centre (CNIO) > > > Phone: +34-91-732-8000 ext. 3019 > > Fax: +-34-91-224-6972 > -- > Ramon Diaz-Uriarte > Department of Biochemistry > Universidad Autónoma de Madrid > Spain > > http://ligarto.org/rdiaz > > Temporarily at: > Structural Biology and Biocomputing Programme > Spanish National Cancer Centre (CNIO) > > Phone: +34-91-732-8000 ext. 3019 > Fax: +-34-91-224-6972 > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DHCP timeout on ethernet device.
2011/10/5 Dan Williams > On Tue, 2011-10-04 at 11:44 +0200, Jiri Popelka wrote: > > You can add > > > > timeout ; > > > > to /etc/dhcp/dhclient-.conf > > > > > > See also > > > http://mail.gnome.org/archives/networkmanager-list/2011-September/msg00127.html > > That doesn't work because NM bounds the DHCP transaction and kills it if > it runs over 45 seconds. > > The better question is: why is DHCP on that network taking so long? > I've talked about bumping the timeout to 60 seconds before, but the > point here is that if your network is taking more than 60 seconds to > respond to DHCP requests, something is *really*, *really* wrong, and > should be corrected on the network side instead of working around this > in the client. How long is the DHCP transaction taking? > > Dan > > Could it be some Spanning-Tree issue? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Automatic proxy configuration in dispatcher.d
I don't think so. Consider if super-user rights is really needed inside the script, if so, use SUID-root. It's lame, but works. 2011/9/21 José Moyano > Hi José Queiroz (tocayo ;) > > Do you think that su $user -c will work instead of sudo? > > 2011/9/21 José Queiroz : > > Hello Jose Moyano, > > > > "sudo" only works if run from a valid terminal. This may be the problem > with > > your script. > > > > 2011/9/21 José Moyano > >> > >> Hi everybody, > >> > >> I write the following script to make network manager dispatcher to > >> change the proxy automagically based on site IP. > >> > >> #!/bin/sh > >> > >> IF=$1 > >> STATUS=$2 > >> > >> echo "-" > >> >> \ > >>/var/log/autoproxy.log > >> > >> date >> /var/log/autoproxy.log > >> > >> echo "Configuring proxy..." >> /var/log/autoproxy.log > >> NETMASK= > >> > >> if [ -n "`/sbin/ip addr show to $NETMASK`" ]; then > >>echo "Address with proxy detected..." >> /var/log/autoproxy.log > >> > >>PROXY_HOST="proxy.something.ar" > >>PROXY_PORT="8080" > >> > >>for user in "jose" > >>do > >>echo "Setting proxy for user $user" >> /var/log/autoproxy.log > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf --type string \ > >>--set /system/http_proxy/host $PROXY_HOST >> \ > >>/var/log/autoproxy.log > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf --type int \ > >>--set /system/http_proxy/port $PROXY_PORT >> \ > >>/var/log/autoproxy.log > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf --type bool \ > >>--set /system/http_proxy/use_same_proxy true >> \ > >>/var/log/autoproxy.log > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf --type bool \ > >>--set /system/http_proxy/use_http_proxy true >> \ > >>/var/log/autoproxy.log > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf --type string \ > >>--set /system/proxy/mode manual >> /var/log/autoproxy.log > >>done > >> else > >>echo "The address has no proxy known" >> /var/log/autoproxy.log > >> > >># Clear proxy configuration for all users > >>for user in "jose" > >>do > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf \ > >>--unset /system/http_proxy/host > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf \ > >>--unset /system/http_proxy/port > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf \ > >>--unset /system/http_proxy/use_same_proxy > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf \ > >>--unset /system/http_proxy/use_http_proxy > >> > >>/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ > >>--config-source=xml::/home/$user/.gconf \ > >>--unset /system/proxy/mode > >>done > >> fi > >> > >> echo "Proxy configuration done" >> /var/log/autoproxy.log > >> > >> Funny thing, the script works if executed manually as root. When the > >> script is executed by network manager dispatcher, the calls to > >> gconftool-2 do nothing. The script is executed because all the log > >> printing can be seen in the /var/log/autoproxy.log file. I tried > >> adding other commands to the script, printing whoami (replies "root") > >> and everything seems to be fine. However, gconftool-2 has no effect in > >> the gnome configuration. > >> Does anyone know what can be the problem? > >> Thanks in advance! > >> > >> José. > >> ___ > >> networkmanager-list mailing list > >> networkmanager-list@gnome.org > >> http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > ___ > > networkmanager-list mailing list > > networkmanager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Automatic proxy configuration in dispatcher.d
Hello Jose Moyano, "sudo" only works if run from a valid terminal. This may be the problem with your script. 2011/9/21 José Moyano > Hi everybody, > > I write the following script to make network manager dispatcher to > change the proxy automagically based on site IP. > > #!/bin/sh > > IF=$1 > STATUS=$2 > > echo "-" >> > \ >/var/log/autoproxy.log > > date >> /var/log/autoproxy.log > > echo "Configuring proxy..." >> /var/log/autoproxy.log > NETMASK= > > if [ -n "`/sbin/ip addr show to $NETMASK`" ]; then >echo "Address with proxy detected..." >> /var/log/autoproxy.log > >PROXY_HOST="proxy.something.ar" >PROXY_PORT="8080" > >for user in "jose" >do >echo "Setting proxy for user $user" >> /var/log/autoproxy.log > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf --type string \ >--set /system/http_proxy/host $PROXY_HOST >> \ >/var/log/autoproxy.log > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf --type int \ >--set /system/http_proxy/port $PROXY_PORT >> \ >/var/log/autoproxy.log > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf --type bool \ >--set /system/http_proxy/use_same_proxy true >> \ >/var/log/autoproxy.log > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf --type bool \ >--set /system/http_proxy/use_http_proxy true >> \ >/var/log/autoproxy.log > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf --type string \ >--set /system/proxy/mode manual >> /var/log/autoproxy.log >done > else >echo "The address has no proxy known" >> /var/log/autoproxy.log > ># Clear proxy configuration for all users >for user in "jose" >do >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf \ >--unset /system/http_proxy/host > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf \ >--unset /system/http_proxy/port > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf \ >--unset /system/http_proxy/use_same_proxy > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf \ >--unset /system/http_proxy/use_http_proxy > >/usr/bin/sudo -u $user /usr/bin/gconftool-2 \ >--config-source=xml::/home/$user/.gconf \ >--unset /system/proxy/mode >done > fi > > echo "Proxy configuration done" >> /var/log/autoproxy.log > > Funny thing, the script works if executed manually as root. When the > script is executed by network manager dispatcher, the calls to > gconftool-2 do nothing. The script is executed because all the log > printing can be seen in the /var/log/autoproxy.log file. I tried > adding other commands to the script, printing whoami (replies "root") > and everything seems to be fine. However, gconftool-2 has no effect in > the gnome configuration. > Does anyone know what can be the problem? > Thanks in advance! > > José. > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Password Security
Even though you should not have allowed his friend from accessing your account, I think it's possible to add a control so the hidden passwords are only displayed if a master password is provided. This is the behavior of Mozilla Firefox, for example. This master password can live on the User Wallet, or wherever NM uses to store the connections' passwords. 2011/6/8 Timo Babst > Hello, I am using NetworkManager Applet 0.8. It works great except for one > very annoying thing : there is a checkbox that says "show password" and > someone (luckily a friend) was able to copy my password just by using this > little funny feature. Could'nt you make sure that the user has to be root in > order to view the password? It IS very annoying, since this feature makes > every password absolutely useless. Sorry to be so direct, but this really is > a BIG issue for me (and I think it should not be too hard to change it for > the guy who developped it). > > Best regards, > > Timo Babst > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DHCP fall back to link-local? (IPv4)
Sorry the last reply gone personal. Em 24 de maio de 2011 14:15, W. Martin Borgert escreveu: > Quoting "José Queiroz" : > >> It seems to me that this behaviour is handled by AVAHI. >> > > Yes, many thanks! The manual page of avahi-autoipd says: > > "avahi-autoipd can be used [...] as plugin for a DHCP client > such as ISC's dhclient, where it can be used as fallback > solution if no DHCP server is found." > > (http://linux.die.net/man/8/avahi-autoipd) > > Or did you mean that avahi-daemon does handle DHCP? > > Cheers > > No, AFAIK AVAHI will only handle the assignment of a link-local address. DHCP should be handled by dhclient, dhcpcd or pump. In fact, I think that if the idea is to reproduce the IPv6 behaviour of having a link-local address, AVAHI should assing ll-address even if the dhcp client do find a valid server. But this is another discussion... ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Can't create new wireless network in NetworkManager Applet 0.8
Are you using NM from official Ubuntu repositories? These are still 0.8.0. Maybe you should give a try on NM 0.8.4 from NetworkManager PPA: https://launchpad.net/~network-manager/+archive/ppa 2011/5/23 William Moon > Ubuntu 10.04 LTS > > When I left click the applet and select "Create New Wireless Network" the > "Create" button is grayed out. > If I right click the applet, select "Edit Connections", then the "Wireless" > tab, then the "Add" button, the "Apply" button is grayed out. > > If I open a terminal and enter "nm-tool" I get > > [QUOTE > NetworkManager Tool > > State: connected > > - Device: wlan0 > > Type: 802.11 WiFi > Driver: iwl3945 > State: disconnected > Default: no > HW Address: 00:18:DE:2D:74:88 > > Capabilities: > > Wireless Properties > WEP Encryption: yes > WPA Encryption: yes > WPA2 Encryption: yes > > Wireless Access Points > Janet -O_Wireless_C990BB: Infra, 00:22:75:C9:90:BB, Freq 2437 MHz, Rate 54 > Mb/s, Strength 34 > > > - Device: eth0 [Wired connection 1] > --- > Type: Wired > Driver: tulip > State: connected > Default: yes > HW Address: 00:04:5A:A8:76:D5 > > Capabilities: > Carrier Detect: yes > > Wired Properties > Carrier: on > > IPv4 Settings: > Address: 64.77.253.186 > Prefix: 23 (255.255.254.0) > Gateway: 64.77.252.1 > > DNS: 198.6.1.122 > DNS: 198.6.1.3 > /QUOTE] > > Any ideas would be greatly appreciated. > > Bill > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Gateway and link-local (IPv4) possible?
Em 21 de maio de 2011 10:51, W. Martin Borgert escreveu: > On 2011-05-20 14:41, José Queiroz wrote: > > Why are you using link-local addresses? > > I'm connecting an embedded device to a PC, so that the PC can > access the GUI (web interface) of the device. Th link local > address has the advantage, that there is very little > configuration necessary for the end user and no address conflict > will happen with the LAN of the user. For this no routing is > necessary. However, in some situations it would be a nice extra > if the PC could act as a router to e.g. a software repository. > > I can set the gateway manually on the device and it works fine > (even if not intended by the IP standards), but at least the > network-manager applet lacks, it seems, any settings for this. > (NM applet is not used on the embedded device, but I used it as > a tool to create NM configuration files.) > Can't this device work with DHCP? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Gateway and link-local (IPv4) possible?
2011/5/20 Marc Luethi > > So it boils down to: 169.254.0.0/16 should not be routed - hence the name > "link local". While possibly technically feasible, you might find rather > strange side effects. > One of these could be that the destination address could itself have a link local address. So it could think that your ll-addressed packet was from the local link, avoiding proper communication... ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Gateway and link-local (IPv4) possible?
Why are you using link-local addresses? 2011/5/19 W. Martin Borgert > Hi, > > I am connecting two machines via a link-local IP address > (169.254/16) and one machine should work as the gateway for the > other. However, the NM applet does not allow setting any routes > or gateways in the case of link-local. Is this a limitation of > the Internet Protocol, Linux, network manager, or NM applet? (Or > a limitation on my understanding of things?) > > Thanks in advance! > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH 0/3] [RFC] Support for ADSL modems
2011/5/6 Pantelis Koukousoulas > Hi, before I leave for FOSSCOMM.gr, this patch series implements the > initial > version of the support for ADSL modems in network manager. > > Notes: > * PPPoA-only for now. I hope that PPPoE can be added with not too much > trouble > as well, if it is possible to just create a new ethernet device for the > "nas0" > interface that br2684ctl creates and reuse the already existing "wired" > device > PPPoE support. > > This way the adsl part can manage the ATM part of the equation just > like it > does now for PPPoA. > > * This is the "duct tape and gum" implementation, according to the "first > make > it work, then make it work right" motto. There are lots of > bugs/limitations > duplicate code etc but at least it works for me (TM) now :P > > * My initial patch that added everything at once got bounced for > moderation > due to its size, so (for size and easier reviewing reasons) I split it > to > 3 patches, in a bisect-friendly way (after each patch, NM builds and > does > something useful) > > * I 'm now happily waiting for your comments / advice / testing etc :) :) > > Hi, Maybe this can be a little off-topic, but is there any intent to add support to PPPoE over wifi? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re:
Try killing modem-manager: sudo killall -TERM modem-manager 2011/4/11 Feipeng Liu > Hi, > > I noticed that sometimes USB 3G modem doesn't connect, but if I plug > out the modem and plug in again, it works. Is there anyway to simulate > this behavior in DBUS interface? So that I don't have to plug out the > modem physically every time. > > Thank you and Best regards, > Feipeng > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Handling of empty secrets
Em 2011/4/5 Dan Williams > What situations do you need these in? (empty secrets) >> > > Said you have a certificate-based VPN connection. As each VPN user have its own certificate, and certificate's key is password protected, one can assume that no further authentication is needed. > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Kubuntu 10.04: Stuck in 0.8.1?
Hi, I'm using NetworkManager PPA Daily trunk builds from Launchpad ( https://launchpad.net/~network-manager/+archive/trunk), and noticed that, besides the site says that the latest version is 0.8.4~git.20110321t190247.e3a02aa-0ubuntu2~nmt2~luci, I'm still using 0.8.1: $ apt-cache policy network-manager network-manager: Installed: 0.8.1+git.20101009t040337.01fa170-0ubuntu1~nmt1~lucid1 Candidate: 0.8.1+git.20101009t040337.01fa170-0ubuntu1~nmt1~lucid1 Version table: *** 0.8.1+git.20101009t040337.01fa170-0ubuntu1~nmt1~lucid1 0 500 http://ppa.launchpad.net/network-manager/trunk/ubuntu/lucid/main Packages 100 /var/lib/dpkg/status 0.8-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages Why do this happens? What should I do to get NM upgraded to 0.8.4? The same happens on 2 other Kubuntu machines. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: upgrade nm-applet 0.8 to 0.8.1 on ubuntu 10.04
Install/activate NetworkManager PPA: https://launchpad.net/~network-manager/+archive/ppa 2011/3/25 susitha senarath > Hi, > > I'm using Ubuntu Lucid and I want to upgrade my network manager applet to > 0.8.1 or 0.8.2 . This is because they says that some new features in Mobile > broad band come with new release. So I want to install new version in my > machine. I downloaded the source of 0.8.1 I'm not sure whether it is ok to > install in without stopping current one. The install guide does not talk > about that. So I need little bit help their. > > Thank you > Ravinda > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How do I create a new wifi connection with nmcli?
2011/3/20 Leonardo Ferreira Fontenelle > Em Dom, 2011-03-20 às 10:05 +0100, Ma Begaj escreveu: > > 2011/3/20 Leonardo Ferreira Fontenelle > > Hello, list! > > I wasn't able to use nmcli to create a new wifi connection. The access > point is listed by "nmcli dev wifi", but if I try to connect to it with > "nmcli con up myssid" it says the connection is unknown. Indeed, it is not > listed in /etc/NetworkManager/system-connections/ . The only connection I > was able to use was "Auto eth0", which was automatically created for me. > > Is nmcli able to create a new wifi connection? How do I make it create it? > > Thanks in advance. > > > you forgot "id" in your command ... > > nmcli con up id myssid > > but you have to use connection name from network manager and not essid of > your ap. > > > Thank you. When I forgot to type on the mail, but I did use "id" on my > system, no luck. > > How to I get the connection name (or UUID) from NM if the wireless networks > don't show up in "nmcli con list"? > > Thanks for your attention, > > AFAIK, there's no way to ***create*** a connection in nmcli, only to ***activate*** or ***deactivate*** it. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Implementing IPv6 in modem manager
Hi Dan and Guillaume, If adding support to IPv6, it would be good to add NAT-PT and v4v6 tunnels to the "TODO" list. 2011/3/19 Dan Williams > On Sat, 2011-03-19 at 12:56 +0100, Guillaume Leclanche wrote: > > Hello, > > > > I browsed the source code, and I've seen that modem manager supports > > only "IP" type of PDP (that is, IPv4). Knowing the network > > requirements for IPv6 and AT commands, I started checking what would > > have to be changed in the code to have support of IPv6 working > > properly. But honestly I've not coded in C in the last 10 years, and > > although the code is very clean (congratulations !), the architecture > > is not documented and I ended up wondering the role of each function. > > > > I have the knowledge of network and AT commands, plus I own the > > hardware and 3GPP network to test, so is anybody with good knowledge > > of modemmanager architecture & code willing to team with me to > > implement v6 over 3GPP ? It's probably not a lot of code, but you need > > to know where to do all changes. > > Yes, we do need IPv6 support in MM... great to hear you're interested. > There's a few issues here that we need to handle. > > 1) detecting the available PDP context types: many many modems only > support the IP type, but others will support the IPV4/V6 types as well, > especially newer ones. So we'll need to add some code to the enable > sequence (mm-generic-gsm.c) to request AT+CGDCONT=? and pick out the > available PDP context types. There's code that already does some of > this, but only for AT+CGDCONT? to get the currently defined PDP > contexts, while we need to get the *possible* ones. > > 2) based on that, we need some way of figuring out whether we can do a > single V4/V6 PDP context, or whether we might have to do separate PDP > contexts if the modem can't do both in the same PDP at the same time; I > seem to recall that sometimes you have to use a secondary PDP context > for IPv6. But for the start, I'd suggest only handling the V4V6 context > type if your modem supports it, or doing one-or-the-other. > > 3) we need to define some "simple connect" key/value pairs that indicate > what the user wants the IP addressing to be; this could be as simple as > a key name of "ip-config" with values of "v4", "v6", and "v4v6" or > something like that. Keep in mind that we'll probably want to use this > for CDMA too if we can, which doesn't have PDP contexts, so we should > keep it generic. > > 4) we'll need to somehow indicate to clients (like NetworkManager) what > sort of PDP context actually got negotiated; do we allow failure of some > method and fallback to another? ie if the user wants IPv6 but doesn't > care if they only get IPv4, do we need to bother handling that? > > Just some thought's it's really not to hard I think to implement the > basics here. But having answers or at least a direction on some of > these questions might help us figure out how to best implement it. > > What do you think? We'd be glad to have your help and input on this :) > > Cheers, > Dan > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Question about
Hi Larry, Are you using a Dell laptop? A recent kernel change broke the WMI support to some dell hardware. If it's your case, try blacklisting dell-laptop modules and reseting your machine. 2011/3/13 Larry Finger > I am running openSUSE 11.4 with NetworkManager 0.8.2 and knetworkmanager > 0.9. Usually everything works fine, but under some circumstances that are > not understood, wireless is disabled. It is not blocked by a radio-kill > switch, as 'rfkill list' shows > > 0: phy0: Wireless LAN >Soft blocked: no >Hard blocked: no > > Similarly, I see no reason for the block in /var/log/NetworkManager. For > completeness, 'nmcli nm' shows > > RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN > running disconnectedenabled disabled enabled enabled > > Are there any other commands that might tell me where the problem is > occurring? Switching from knetworkmanager to the plasmoid networkmanager > package clears the problem, but I would like to understand the problem. > > Thanks, > > Larry > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: autoconnect VPN?
Sorry the off-topic: how did you managed to make your connection to work? Are using certificates or username/passwords? 2011/2/27 Matej Kovacic > Hi, > > what is the function of "autoconnect" option in VPN settings section? > > I have an OpenVPN connection and I marked it to be autoconencted. > However, nothing happens and I have to connect to VPN manually. > > And also - when VPN connection is lost, it is not re-established > automatically again... > > > Regards, > > Matej > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mysteries of NM
Are you using KDE 4.5? The network-manager plasmoid was redesigned, and now its much more stable than before, it's worth a try. 2011/2/26 Timothy Murphy > Andrey Borzenkov wrote: > > >> I'm running NetworkManager on my Thinkpad T60 > >> (Intel PRO/Wireless 3945ABG controller, iwl3945 driver) > >> and it works fine under Fedora/KDE, > >> but I find the user interface almost completely unintelligible. > > ... > >> > >> Are others puzzled by the NM interface, > >> or am I being obtuse? > >> > > > > It is not NM but rather knetworkmanager (a.k.a. networkmanagement) > > which is independent project. > > > > I do not think many people on this list are using or working on it. > > You better use kde-networkmana...@kde.org. > > OK, thanks. > I suspected that might be it. > The interface is quite nice, but bizarre. > > -- > Timothy Murphy > e-mail: gayleard /at/ eircom.net > tel: +353-86-2336090, +353-1-2842366 > s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Vpn connection disabled in network manager
Which of the packages below are installed on your system? > > network-manager-openconnect > network-manager-openconnect-gnome > network-manager-strongswan > network-manager-strongswan-kde > network-manager-openvpn > network-manager-openvpn-gnome > network-manager-openvpn-kde > network-manager-pptp > network-manager-pptp-gnome > network-manager-pptp-kde > network-manager-vpnc > network-manager-vpnc-gnome > network-manager-vpnc-kde > 2011/2/23 Anton Boronnikov > > I've just installed ubuntu 10.10. Previously I tried 11.04. But there is >> the same problem I can not solve. >> What ever I configure in my vpn-connection it still disabled in network >> manager. I can not force network manager to use my vpn connection. My >> connection exposed in connections tab but absolutely inactive! >> >> Please help! What is my problem? Any ideas? Is there a magic button >> "enable vpn connections" I forgot to click/enable? >> ___ >> networkmanager-list mailing list >> networkmanager-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/networkmanager-list >> > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Help with OpenVPN Connection
Hi, I'm trying to setup an OpenVPN connection, but I think I'm missing some point, because I'm stuck. The server side is setup (afaik) and ready, and I already managed to get a manual connection working. Now, I want to setup NM-OpenVPN also, but all I'm getting are "Failed to update VPN secrets: 3 Secret no-secret was empty" errors. I'm using Kubuntu 10.04, package versions: network-manager: 0.8.1+git.20101009t040337.01fa170-0ubuntu1~nmt1~lucid1 network-manager-openvpn: 0.8-0ubuntu3 network-manager-openvpn-kde: 0.9~svn1137272-0ubuntu2~lucid1~ppa1 The connection uses only PEM Certificates (by the way, may I use a PKCS12 certificate on it?), no connection passwords, except the key file password. I'm using the same certificate files used in the manual connection, so they're OK. I need some directions to get this working. Thanks. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Monitor
2011/2/18 Matej Kovacic > (...)Hi, > So the best practical solution is to have network trafic monitor inside > NM. Not only for 3G, also for other types of connections. In could be > very useful to know how much traffic did you have on mobile conection 1, > 2, etc., wired connection at home, in the office, how much went it > through VPN, etc. > > That would be really great. A 3G quality monitor could also be handy. > Also some other data could be useful to have. For instance how much time > I have been using one connection and the other. And maybe also time and > traffic "profile" (when I was online / transferring data) - please see > attached mockup picture. > > It could also be done that would be able to select/deselect connections > with clicking to the legend, and the data on the graph would then cnahge > respectively... > > Sorry, I don't want to burden you too much, I am just givin some ideas. > > I understand this requires a database, and that is not so simple to do. > But I think features like that give NM and Linux in general exactly that > "marketing advantage" it needs. > > Maybe RRD? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Monitor
2011/2/18 Marc Herbert > Le 17/02/2011 18:16, Stuart D Gathman a écrit : > > Le 15/02/2011 18:53, Matej Kovacic a écrit : > >>> I am using 3G mobile connection, and have limited traffic. Traffic over > >>> some treshold (for instance 1 Gb a month) is very very expensive. > > > That 3G provider is missing the boat, business wise. [...] > > Agreed, but most of the other providers (which catch the boat) still > charge volume one way or the other. Even when they keep saying > "unlimited". So monitoring usage is useful in any case. > > Sorry the offtopic (and sorry the personal message, Mark) In my country, almost all the 3G operators are doing the same, in some different ways. The one I use (Tim Brasil) have this plan called "Infinity Web" that gives me 4GiB of traffic per mount. After the user pass this limit, the connection drops to 100Kbps. And the swear that the connection is "unlimited", just because it doesn't charges for the additional traffic. ::) And even with this nonsense, it's one of the best plans --- the other operators have even worse conditions. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
2011/2/7 Ozan Çağlayan > On 03.02.2011 13:00, Ozan Çağlayan wrote: > >> Hi, >> > > And there's also another bug that I can reproduce: > > 1. Connect using WiFi > 2. Soft block WiFi (result: sw_enabled=0, hw_enabled=1) > 3. state file is updated to WirelessEnabled=false > 4. Unblock wifi (result: sw_enabled=1, hw_enabled=1) > 5. state file is not updated and stays the same > 6. WiFi doesn't come up automatically unless the "Enable wireless > networking" is clicked in the UI. > I confirm that this happens here, too. NM 0.8.1+git.20101009t040337.01fa170-0ubuntu1~nmt1~lucid1 Kubuntu 10.04, NM from ppa/Launchpad. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wlan0: device not ready
2011/2/4 Julien Danjou > Hi there, > > I've already spent some hours trying to found what's the problem, but > now I really need some hints. > > I've a WLAN on this laptop (iwlagn) which used to work fine with a > 2.6.32 Linux kernel (Debian). I've now upgraded to a 2.6.37 kernel, and > NM does not want to let me connect my wlan0 device. > Does this kernel have full support to your iwlagn device? Including possible firmware files? > > The device works fine with wireless-tools (iwlist/iwconfig/ifconfig) and > I do see networks with these. However, nmcli says: > > % nmcli dev > DEVICE TYPE STATE > eth0 802-3-ethernetconnected > wlan0 802-11-wireless unavailable > > It does not seems like a rfkill problem since: > 5: phy0: Wireless LAN >Soft blocked: no >Hard blocked: no > 10: hci0: Bluetooth >Soft blocked: no >Hard blocked: no > > I've set logging to debug with all domains, and what I got with latest > NM from git is: > > WiFi enabled by radio killswitch; enabled by state file > WWAN enabled by radio killswitch; enabled by state file > WiMAX enabled by radio killswitch; enabled by state file > (wlan0): driver supports SSID scans (scan_capa 0x01). > (wlan0): new 802.11 WiFi device (driver: 'iwlagn' ifindex: 3) > (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 > (wlan0): now managed > (wlan0): device state change: 1 -> 2 (reason 2) > (wlan0): bringing up device. > (wlan0): preparing device. > (wlan0): deactivating device (reason: 2). > (wlan0): supplicant interface state: starting -> init > > (then it connects with eth0, but that's not the issue, eth0 with NM > works fine) > > Then it never talks about wlan0 anymore, so it seems to stay stucked at > that supplicant init state. > > I looked quickly at the code, but the last line is printed by a callback > and I'm not sure where the original signal is emitted. So any hint > welcome, I know how to use gdb if that might help. :) > > -- > Julien Danjou > ❱ http://julien.danjou.info > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager-0.8.2 keyfile syslog spam
Try to turn off debugging in "/etc/NetworkManager/NetworkManager.conf".
By the way, which NM version are you using?
2011/1/13 Leho Kraav
> Hello all
>
>
> Can anyone point out to me why NetworkManager is spamming my syslog with
> a really useless "updating: " message every 5 minutes?
>
> Right now I just commented it out, but should this output be moved
> somewhere more sensible?
>
> 1 diff --git a/system-settings/plugins/keyfile/plugin.c
> b/system-settings/plugins/keyfile/plugin.c
> 2 index 27ae0a0..1e0f7af 100644
> 3 --- a/system-settings/plugins/keyfile/plugin.c
> 4 +++ b/system-settings/plugins/keyfile/plugin.c
> 5 @@ -203,7 +203,7 @@ dir_changed (GFileMonitor *monitor,
> 6 break;
> 7 case G_FILE_MONITOR_EVENT_CREATED:
> 8 case G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT:
> 9 - PLUGIN_PRINT (KEYFILE_PLUGIN_NAME, "updating %s", name);
> 10 + /* PLUGIN_PRINT (KEYFILE_PLUGIN_NAME, "updating %s", name); */
> 11
> 12 if (connection) {
> 13 /* Update */
>
> --
> Leho Kraav, M.Sc.
> ___
> networkmanager-list mailing list
> networkmanager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Fwd: NetworkManager connection priority - same ssid ?
2011/1/10 mike cloaked > On Mon, Jan 10, 2011 at 4:19 PM, Franco Miceli > wrote: > > Mike, > > > > I have been dealing with the AP algorithm selection a few months ago. The > > one that selects the best connection is NM. If you get the src you can > see > > it in the file nm-device-wifi.c (for the wireless connections). > > > > The way it is implemented in nm 0.7 (which is the one I have been working > > on) is that NM will go through each favourite connection you have, and > > comparing them with the ones available from scan results. It does not > > prioritize on signal strength rather than timestamp. Which means if the > one > > you last connected to is available it will connect to that one. > > > > I have been playing with the code in order to make that selection signal > > sensitive. In order to do that you need to get signal strength info. The > > method nm_ap_get_strength(ap) can help get such data. The thing is that > not > > all wireless adapters report well signal strength, but if you trust > yours, > > then you can make this mod. > > > > Hope I could help. If you need I can share the code I used. > > Thanks Franco - I need to understand a few things - The version that > is current in F14 that I am running is > NetworkManager-0.8.1-10.git20100831.fc14.i686 and, as José Queiroz > mentions in his subsequent reply, there have been many important > changes since v7, although he does not reference a link to what those > changes have been in v0.8. > > However, what I do not know is whether the selection of AP was made > signal sensitive in the implemented changes in 0.8 or not? Certainly > the last signal used appears to be the one selected when booting up > the machine after switching off previously, which would be a > reasonable "first option" for the starting choice, but then a > secondary criterion where a stronger signal that already has been > used, and is listed in the connections in NM, would be selected and > switched in instead. Having such a two-stage selection would be what > would suit me (and many others) better than just going to the last one > used. > > I wonder if José Queiroz would tell us if this is in fact what has > been implemented in 0.8 (or 0.81 or 0.82) or not? That would be very > helpful. If this has been put into the code but has residual bugs > then presumably getting some data and putting in a bug report so that > developers could look at fixing it would be the way forward? > > A nice level headed and fact based approach to this would be ideal. > I could swear that this was already discussed here, but the only reference I found was another message of mine. In the lack of good references, I ran to my kubuntu box. I also have an ESS in my home. My syslog shows several messages from wpa_supplicant about group rekeyings to one of the APs (the one that haves the strongest signal in the place I usually use my notebook). In one moment, I see messages from the kernel about deauthenticating the first AP, and authenticating the second one. Around these messages, I see only messages from wpa_supplicant, even though NM debugging is enabled. So I concluded that this reassociation was ordered by wpa_supplicant, not by NM. But, I admit, this is only an empirical verification; I didn't checked any code to confirm this. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM disconnect after one hour with a wired network
2011/1/9 Charles Cultien > Hi, > I have a very strange problem : > I'm connected with the wired network of my university and each time, after > one hour, Network Manager disconnect himself and didn't reconnect > automatically. So I have to reconnect by myself evry hour and this is boring > ! > > I don't know why and how change this. A dmesg didn't show anything (on the > moment it disconnect). > > I'm using LInux Mint DEbian (so debian testing) with : > Linux kernel 2.6.32-5-686 > GNOME 2.30.2 > Network Manager 0.8.1 > I'am am behind a proxy (automatically given by the script htpp://proxyconf) > and so the gnome proxy is configured. > > Thank you for helping and didn't hesitate asking for trying something or > given more information. > > Are you using DHCP for the IP address? The problem may be related to it. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Fwd: NetworkManager connection priority - same ssid ?
2011/1/10 Franco Miceli > Mike, > > (...) The way it is implemented in nm 0.7 (...) > The current version is 0.8 (0.8.2, in fact), there was a lot of important changes since 0.7. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager connection priority - same ssid ?
Em 9 de janeiro de 2011 14:12, mike cloaked escreveu: > By the way in this case both signals are virtually noise free,. and > indeed there are no neighbours using the same channels - (I checked > over a period doing a wireless site survey both before the test and > during the test) > > In fact, if you're using the second AP as a wireless repeater, you don't have a noise free channel. Consider use a UTP cable to link the APs. Assure yourself that the APs are configure to work on different channels with >=5 channels of isolation. This restraint makes the only usable channels be *1*, *6*, and *11*. Don't use any other channel in the presence of other wireless sources. Check also that both APs are using the same cripto configs. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager connection priority - same ssid ?
2011/1/8 mike cloaked > I have a home LAN where there are two wireless access points. I run > Fedora F14 and use NetworkManager to connect. The access points both > use the *same* ssid and encryption to try to make a seamless wifi > network around the house. > > How does NetworkManager decide on which of the two APs to connect to? > AFAIK, the selection of which AP to connect, in a ESSID, is done by "wpa_supplicant", not by NM. > What I would like is that in this instance the connection is made to > that AP that is giving the strongest signal at the laptop but it does > not always do this. > > That's exactly the criterium used by wpa_supplicant to choose which AP to connect: strongest signal. But if there's some problem with the strongest signal (e.g. authentication timeout), it will try the other APs available. This may happen also if the strongest signal is the most noisy. > I can't see a way of telling NM how to prioritise the strongest signal > at any time, but I don't know if this is already the logic that is > built in to NM or not - it does not appear that the connection > decision is based on signal strength but on perhaps other or > additional criteria? > > Thanks > > You can configure a preferred AP on NM, to always connect to the same AP. But I think that this isn't what you want to do. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Español (Was: Re: networkmanager-list Digest, Vol 7 6, Issue 2,)
2011/1/7 pilar te quiere > porfavor necesito que me escrivas en español,gracias > > Hola, esta es una lista en Inglés. Si usted no entiende Inglés, a continuación, no se inscribe en la lista, o utilizar un servicio de traducción, tales como Google Translate (http://translate.google.com). PD: aun no hablan ni escriben el español, he usado el servicio por encima de la traducción de mi lengua materna (portugués). ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: last connection
Instead of using auto connection, create a conection (e.g. "@Home") and select the preferred SSID. This way you can mark your home's network SSID as "preferential". Create one of these connections to each of the wireless networks that you use to connect, so you can roam from one to another without further reconfiguring or manual proceeding. 2010/12/31 Simone Romano > Dear all, > > I was wondering if there is a way to connect to the last connected SSID > automatically. I'm at home and I get a lot of wireless networks, I always > have to choose mine because it tries to connect to other networks (maybe > alphabetically ordered). I would like it connects to my network, that is the > last connected network from last boot. > > It could be a good fix. > > Bye, > Simone > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM automatically reconnects to WIFI AP automatically after commanded to disconnect from it.
Is your connection marked "Auto-connect"? 2010/12/22 Greg Suarez > Hi, > > What I'm seeing in my application is when I command NM to disconnect from > an AP (via DBUS) NM disconnects but then reconnects right away. > AM I missing a step that needs to be done first? > > I'm using the method org.freedesktop.NetworkManager.DeactivateConnection > > Thanks, > > Greg > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wifi module can't scan any more
2010/11/23 rain blue > Dear, >I meet some issue. Could someone help me? > version; NetworkManager 0.8 > NetworkManager-Applet 0.8 ( I modify to no GUI ) > wpa_supplicant 0.6.9 > Issue step: > 1.connect AP ( Success!!! ). > 2.ping network over 2~~3 hours. > 3.wifi will auto disconnected. > 4.And it will be not connect AP or scan any AP. > > I try to use other system > Other system, OK. But, what is your original system? > 1.ubuntu 10.04 -- pass ( if i always scan AP or Get strength from > NetworkManager. over 6~7 hours fail) > 2.RTOS-- fail > > when wifi module crash. > I use applet, iwlist or dbus-send wpa_supplicant that get AP ssid. > there do not work... > it must be re-power-supply to module. > that will recover. > > So, I don't no how i can guess that is driver, HW or system issue. > And how can i let module crash acceleration in other system. > > blue > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modem pppd authentication error: peer refused to authenticate: terminating link
Hi Hong Sheng,
2010/11/15 hong sheng
> Hi
>
> I got the following pppd call error for chap authentication in vz system.
> It seems the peer refused to authenticate. How can I fix the problem? Does
> it mean I have to tell Verizon my username and password for setting up the
> data connection so that the peer can accept it?
>
Is this a 3G connection? If so, the authentication happens inside the 3g
dongle, using a "common" username/password, in the majority of the cases.
In example, my connection uses the ISP name as username ("tim", for
"Tim/Brazil"). The same for the password.
> thanks
>
> Here is the pppd debug message:
>
>
>
> Dialing...
> Script /usr/sbin/chat -v -f /etc/chatscripts/verizon-connect finished (pid
> 14614), status = 0x0
> Serial connection established.
> using channel 11
> Using interface ppp0
> Connect: ppp0 <--> /dev/ttyUSB2
> sent [LCP ConfReq id=0x1
> ]
> sent [LCP ConfReq id=0x1
> ]
> rcvd [LCP ConfReq id=0x1 0xebbf684b> ]
> sent [LCP ConfAck id=0x1 0xebbf684b> ]
> rcvd [LCP ConfRej id=0x1 ]
> sent [LCP ConfReq id=0x2
> ]
> rcvd [LCP ConfAck id=0x2
> ]
> sent [LCP EchoReq id=0x0 magic=0x49a7edba]
> peer refused to authenticate: terminating link
> sent [LCP TermReq id=0x3 "peer refused to authenticate"]
> rcvd [CHAP Challenge id=0x1 <7239534d5bd64be4573a7c768252d3f5>, name = ""]
> Discarded non-LCP packet when LCP not open
> rcvd [LCP EchoRep id=0x0 magic=0xebbf684b]
> rcvd [LCP TermAck id=0x3]
> Connection terminated.
>
>
>
> ___
> networkmanager-list mailing list
> networkmanager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Specifying an IPv6 suffix
Em 5 de novembro de 2010 15:33, Robert Moskowitz escreveu: > On 11/05/2010 11:00 AM, José Queiroz wrote: > > 2010/11/5 Marc Herbert > > > PS: this does not look specific to IPv6 > > This does not look specific to NetworkManager, as long as NM is working > strictly in the limits created by the RFCs... > > > The last 64 bits are recommended to be based on the MAC address, but not > only is this not required, it is not recommended for a server. > > For example: > > $ host www.ietf.org > www.ietf.org has address 64.170.98.32 > www.ietf.org has IPv6 address 2001:1890:1112:1::20 > > > How can you tell that this address was dinamically assigned, or a full static address was designed to it? What I am saying is to add flexiblity so that other suffixes can be use. > Have you ever seen this feature in any other system? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Specifying an IPv6 suffix
2010/11/5 Marc Herbert > > PS: this does not look specific to IPv6 > > This does not look specific to NetworkManager, as long as NM is working strictly in the limits created by the RFCs... ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: OT: 3G Modem - Any voice applications?
There is something like this on kmobiletools. 2010/10/12 Ma Begaj > hi, > > off topic question: > do you know linux applications which could be used to make voice calls > through 3G modem > and a headset. I am not talking about VOIP but about standard voice > call like on your phone. > > gnome-phone-manager is probably able to send text messages through 3G > modem but I was > not able to find any voice call (dialer) for linux. windows had > "dialer.exe" which was/is a > program which allows a user to dial an outgoing voice call via his > computer, if the modem > supports both voice and data. > > there are a lot of ppp dialer for linux but only with data support > > any ideas? > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: OT: 3G Modem - Any voice applications?
There is something like this on kmobiletools. 2010/10/12 Ma Begaj > hi, > > off topic question: > do you know linux applications which could be used to make voice calls > through 3G modem > and a headset. I am not talking about VOIP but about standard voice > call like on your phone. > > gnome-phone-manager is probably able to send text messages through 3G > modem but I was > not able to find any voice call (dialer) for linux. windows had > "dialer.exe" which was/is a > program which allows a user to dial an outgoing voice call via his > computer, if the modem > supports both voice and data. > > there are a lot of ppp dialer for linux but only with data support > > any ideas? > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet or alternative for small resolutions?
Did you tried "nm-cli"? It's a command line interface to NM. 2010/9/27 John Connolly > Hi All, > > I'm not sure if this is also the place for networkmanager-gnome related > inquiries, but here goes. The device I'm working with supports a tiny > 320x240 touchscreen display running matchbox-wm/desktop. > > Is anyone aware of a still-maintained frontend for > networkmanager/modem-manager that is more suitable for such a small > resolution? I'm willing to patch nm-applet and/or collaborate on projects > for this purpose. I'm even willing to abandon matchbox in favor of a > window-manager with a decent small-resolution UI for networkmanager. > > I've abandoned connman/ofono recently in favor of NM due to the poor UI > support for the connman/ofono frontend in the community/distro we use > (openembedded). > > Thanks a lot! > > -John > > __ > John Connolly > Software Developer > Bug Labs > 598 Broadway, 4th Floor > New York, NY 10012-3206 > 646.723.9258 > jconnolly @ irc.freenode.net/#buglabs > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: stopping modem manager
2010/9/25 Dan Williams > On Mon, 2010-08-23 at 17:31 +0100, Rune Gellein wrote: > > Hi, > > I tried to just kill the modem manager, but Network manager started it > > again, so if you remove it, network manager will continue to try to > > start it in the background. > > And because of these dependencies, when you update the system again, > > the modem manager will be pulled back in (at least in gentoo). > > > > So what I am looking for is a setting in the Network manager > > configuration to stop it from loading the modem manager at all. > > > > Anything like that available? > > At this time, you either remove the modem-manager package, or you remove > the dbus auto-activation file referenced earlier in this thread. > > I have various ideas how to only run ModemManager on-demand, which > basically revolve around using udev to spawn ModemManager if it's not > already running when a new serial port appears, and have MM quit if it's > not managing any modems. NM would then stop poking MM automatically, > and just rely on its presence. > > The one thing that doesn't solve is if MM crashes, it wouldn't > necessarily get restarted automatically, which is quite useful to > recover from bugs for users that don't know how to manually restart it. > > Dan > And what about creating a "[modem-manager]" section on NetworkManager.conf? This way we could have a "disabled=true" directive to avoid loading MM, and a "debug=" to easy debugging it. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
modem-manager fails to reconnect
Hi, I've noticed a strange behavior with my 3g dongle (Onda MSA405 HS / 19d2:0037). When I plug it, it connects with ease. After some time, if I disconnect it and try to reconnect, it fails, and I have to unplug/plug again the device or restart modem-manager process to get the connection back. I've turned on loggin on modem-manager, and I saw that when it states that the connection transitioned from "connected -> disconnecting" and from "disconnecting -> registered", I can reconnect it. But sometimes, it transitions from "connected -> disconnecting" and then "disconnecting -> connect". When this happens, I cannot reconnect unless unplug or restart modem-manager. This sometimes happens in the first reconnection, sometimes it takes some reconnections to happen, but sooner or later will happen. I'm using: Kubuntu Lucid 10.04, NetworkManager 0.8.1+git.20100810t184654.ab580f4-0ubuntu3~nmt3~lucid modem-manager 0.4+git.20100922t210758.618dc06-0ubuntu1~nmt1~lucid I also saw that in a normal disconnect, ttyUSB2 (data port) and ttyUSB1 send a "NO CARRIER" message; when the disconnection fails, only ttyUSB1 says "NO CARRIER". This is a piece of modem-manager debug. I can consistently reproduce the symptom, if needed. ** (modem-manager:11224): DEBUG: <1285364689.581337> (ttyUSB2): network_mode => 8 ** (modem-manager:11224): DEBUG: <1285364689.581337> (ttyUSB2): username => "tim" ** (modem-manager:11224): DEBUG: <1285364689.581337> (ttyUSB2): number => "*99#" ** (modem-manager:11224): DEBUG: <1285364689.581337> (ttyUSB2): apn => " www.tim.com.br" ** (modem-manager:11224): DEBUG: <1285364689.581337> (ttyUSB2): allowed_mode => 4 ** (modem-manager:11224): DEBUG: <1285364689.581337> (ttyUSB2): password => "tim" ** (modem-manager:11224): DEBUG: <1285364689.581451> (ttyUSB2): simple connect state 0 ** (modem-manager:11224): DEBUG: <1285364689.581492> (ttyUSB2): simple connect state 2 ** (modem-manager:11224): DEBUG: <1285364689.581541> (ttyUSB2): --> 'AT+CREG?' ** (modem-manager:11224): DEBUG: <1285364689.591677> (ttyUSB2): <-- '+CREG: 1,1OK' ** (modem-manager:11224): DEBUG: <1285364689.591776> (ttyUSB2): simple connect state 4 ** (modem-manager:11224): DEBUG: <1285364689.591821> (ttyUSB2): --> 'AT+CGDCONT?' ** (modem-manager:11224): DEBUG: <1285364689.613745> (ttyUSB2): <-- '+CGDCONT: 1,"IP","www.tim.com.br","0.0.0.0",0,0+CGDCONT: 2,"IP","www.tim.com.br","0.0.0.0",0,0+CGDCONT: 3,"IP"," bandalarga.claro.com.br","0.0.0.0",0,0+CGDCONT: 4,"IP","tim.br ","0.0.0.0",0,0OK' ** (modem-manager:11224): DEBUG: <1285364689.613907> (ttyUSB2): simple connect state 5 ** (modem-manager:11224): DEBUG: <1285364689.613961> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting) ** (modem-manager:11224): DEBUG: <1285364689.614001> (ttyUSB2): --> 'ATD*99***1#' ** (modem-manager:11224): DEBUG: <1285364689.634906> (ttyUSB2): <-- 'CONNECT 115200' ** (modem-manager:11224): DEBUG: <1285364689.635012> (ttyUSB2): port now connected ** (modem-manager:11224): DEBUG: <1285364689.635055> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected) ** (modem-manager:11224): DEBUG: <1285364689.635098> (ttyUSB2): simple connect state 6 ** (modem-manager:11224): DEBUG: (net/ppp0): could not get port's parent device ** (modem-manager:11224): DEBUG: <1285364691.463726> (ttyUSB1): <-- '+ZPASR: "HSDPA"' ** (modem-manager:11224): DEBUG: <1285364701.3719> (ttyUSB1): --> 'AT+CSQ' ** (modem-manager:11224): DEBUG: <1285364701.13901> (ttyUSB1): <-- '+CSQ: 16,99OK' ** (modem-manager:11224): DEBUG: <1285364701.14020> (ttyUSB1): --> 'AT+ZPAS?' ** (modem-manager:11224): DEBUG: <1285364701.34469> (ttyUSB1): <-- '+ZPAS: "HSDPA","CS_PS"OK' ** (modem-manager:11224): DEBUG: <1285364708.9169> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected -> disconnecting) ** (modem-manager:11224): DEBUG: <1285364708.9302> (ttyUSB1): --> 'AT+CGACT=0,1' ** (modem-manager:11224): DEBUG: <1285364708.42966> (ttyUSB2): network_mode => 8 ** (modem-manager:11224): DEBUG: <1285364708.42966> (ttyUSB2): username => "tim" ** (modem-manager:11224): DEBUG: <1285364708.42966> (ttyUSB2): number => "*99#" ** (modem-manager:11224): DEBUG: <1285364708.42966> (ttyUSB2): apn => " www.tim.com.br" ** (modem-manager:11224): DEBUG: <1285364708.42966> (ttyUSB2): allowed_mode => 4 ** (modem-manager:11224): DEBUG: <1285364708.42966> (ttyUSB2): password => "tim" ** (modem-manager:11224): DEBUG: <1285364708.43083> (ttyUSB2): simple connect state 0 ** (modem-manager:11224): DEBUG: <1285364708.43126> (ttyUSB2): simple connect state 2 ** (modem-manager:11224): DEBUG: <1285364710.903746> (ttyUSB2): <-- '+ZPASR: "UMTS"' ** (modem-manager:11224): DEBUG: <1285364710.903941> (ttyUSB1): <-- '+ZPASR: "UMTS"' ** (modem-manager:11224): DEBUG: <1285364710.925500> (ttyUSB1): <-- 'OK' ** (modem-manager:11224): DEBUG: <1285364710.927614> (ttyUSB2): <-- 'NO CARRIER' ** (modem-manager:11224): DEBUG: Got failure code 3: No carrier ** (modem-manager:11224): D
Re: how to let http brings up networkmanager modem connectivity?
And how do you intend to differentiate one from the other? 2010/9/16 hong sheng > I mean "bring up the 3G connectivity automatically when we start web brower > application", not just http. > > hong > > > 2010/9/15 Raphaël Jacquot > > >> On 15 sept. 2010, at 23:49, hong sheng wrote: >> >> > Hi >> > >> > I would skip the networkmanager applet in our platform. In stead, I want >> to let the http brower automatically bring up the 3G connectivity for >> NetworkManager. So, what d-bus message I should send to bring up the 3G >> connectivity ? >> > >> > Thanks >> > >> > Hong >> >> sounds pretty shortsighted, considering that the internet contains many >> more things than http... > > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA2 password problem
Sometimes, a problem with the wireless adapter may cause NM to fail connection. When the connection fails repeatedly, NM opens a window asking you to retype the password, even though it is correct. Confirm that you are using the best driver for your device. 2010/9/15 Stuart Gathman > A wrt54g2 wireless lan has a WPA2 Personal password that works with > Windows machines, but does not work with Ubuntu, Fedora 12, or Mac. EAPOL > packets are received (shown by tcpdump) while attempting to connect from > Fedora. So far, the only advice I've managed to get is "use the right > password". It is the right password for Windows, but I'm not sure how to > find the right password for other operating systems. > > Does Windows still have a proprietary password hash for WPA2? What other > things could be causing this? The user ran the included setup CD, which I > believe implements WPS, from Windows. Could this be related? I'm guessing > that resetting to factory defaults and setting up via the web interface will > fix things. > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: vpnc: can't open pidfile /var/run/vpnc/pid for writing
Is there free space in the FS that holds "/var/run/vpnc"? 2010/9/7 Tom Sutherland > From my syslog: > > > Sep 7 13:31:07 angry-butler09 vpnc[7137]: can't open pidfile > /var/run/vpnc/pid for writing > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: VPN connection > 'WolverineECC' (IP Config Get) complete. > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: Policy set > 'LabConn' (eth0) as default for IPv4 routing and DNS. > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: VPN plugin > state changed: 4 > Sep 7 13:31:08 angry-butler09 nm-dispatcher.action: Script > '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. > Sep 7 13:37:37 angry-butler09 vpnc[7137]: select: Interrupted system call > Sep 7 13:37:37 angry-butler09 vpnc[7137]: terminated by signal: 15 > > The tunnel interface comes up, routes are populated, but no traffic seems > to flow across tunnel. > > If I manually create /var/run/vpnc directory prior to starting the > connection, all seems to work properly. > > > version: > network-manager/maverick uptodate > 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 > > > uname -a: > Linux angry-butler09 2.6.35-20-generic #29-Ubuntu SMP Fri Sep 3 14:55:28 > UTC 2010 x86_64 GNU/Linux > > > Any ideas? Is this a distro-specific thing? > > Regards, > Tom Sutherland > > > > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: stopping modem manager
2010/8/20 Alexander Sack > For ubuntu my answer would be to remove the modemmanager package > ... that would do the trick. > > - Alexander > > Won't it cause any dependency problem? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
Em 6 de agosto de 2010 15:43, Ville-Pekka Vainio escreveu: > On Fri, 6 Aug 2010 15:32:27 -0300, "José Queiroz" wrote: > > In Ubuntu, the native b43 module is broken, as the device is always > > disabled. > > > > We have to block it and use the bcmwl-kernel-source, which installs a > "wl" > > driver > > that works. > > > > Maybe this works for you, too? > > > Thanks for the suggestion, but I'd rather not use closed source drivers as > long > as the open source ones work, at least to some degree. > > -- > Ville-Pekka Vainio > Won't you even give it a try? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
2010/8/6 Ville-Pekka Vainio > Hi, > > I'm running Fedora 13 with NetworkManager-0.8.1-1 and a 2.6.34 kernel from > koji. My system has a BCM4312 wifi chip which I'm using with the b43 module > and the proprietary firmware from Broadcom. > > In Ubuntu, the native b43 module is broken, as the device is always disabled. We have to block it and use the bcmwl-kernel-source, which installs a "wl" driver that works. Maybe this works for you, too? NetworkManager is acting a bit weird with wifi. Every time I reboot the > laptop, the wireless connection is disabled, meaning I have to right click > on the nm-applet icon and choose "Enable wireless". Based on > /var/log/messages the firmware is loaded to the device at this point like > this: > > NetworkManager[968]: (wlan0): bringing up device. > kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) > kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready > dbus-daemon: [system] Rejected send message, 1 matched rules; > type="method_return", sender=":1.1" (uid=0 pid=968 comm="NetworkManager) > interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 > destination=":1.56" (uid=500 pid=1563 comm="nm-applet)) > NetworkManager[968]: (wlan0): supplicant interface state: starting > -> ready > NetworkManager[968]: (wlan0): device state change: 2 -> 3 (reason > 42) > NetworkManager[968]: Activation (wlan0) starting connection 'Auto > ' > > etc. etc. > > With my previous laptop, which had an Intel wifi chip, the wireless network > was always automatically enabled when I booted up the computer. I know the > b43 drivers are still under development, but does anyone have an idea what > could be going wrong? The dbus error does look a bit scary to me. > > -- > Ville-Pekka Vainio > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WAN = 3G, share=WIFI, does not turn on WIFI TX
Please, respond my question. Are you using an Access Point, or are you using AdHoc mode? To use "infrastructure", you need an access point, or a wireless router. Does you have one? Which one? Em 2 de agosto de 2010 16:38, Eric Lee Elliott escreveu: > > Using internal Atheros 802.11 NIC to share connection from laptop with ATT > 3G USB modem. Internet is connected to first laptop via 3G modem. First > laptop WIFI is access point for second laptop. > > I have tried infrastructure & ad-hoc. > > -- > God Bless You, > > Eric Lee Elliott > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WAN = 3G, share=WIFI, does not turn on WIFI TX
Are you using an AP to link these laptops, or are you using AdHoc mode? 2010/8/2 Eric Lee Elliott > Can Networkmanager do sharing of WIFI with USB modem as WAN connection? > I've tried configuration repeatedly in various ways, without other > computers detecting WIFI on air. > 3G WAN to shared Ethernet works on both laptops. Both laptops are > Thinkpads with Atheros AR5212 802.11abg NICs. > > If this does work in Kubuntu 10.04, where must I look for why WIFI does not > transmit? > > Eric > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Different permissions for different network interfaces
2010/7/7 > Hi all, > > I have a problem with ubuntu 10.04 LTS and the Network Manager. > As per default Network Manager is working fine and doesn't make any > trouble. > > My customer has the requirement that the default network interface > (connected to public LAN) must be protected and it should not be able to > change anything on it (even taking it on- or offline should be possible) > But all of the users also have a second LAN Interface, which they use for > testing, in a dedicated network. This Network Interface should be > manageable by every user, without being prompt for a password when changing > settings. > > If tried several ways and went through the official Network Manager > documentation without success. > It always seems to have somewhere a problem. > > So I would be really thankful if somebody could point me to the right > direction or does have a working example for this scenario. > > If you have questions or if you require additional information, feel free > to ask me. > > Thanks and all the best, > Simon > Hi Simon, Configure the first connection on the "/etc/network/interfaces". This way, NM will not manage it, so the users will have no access to change it without system access (root or sudo). You could also define this connection in a system-wide connection. But I just don't know how to enable it (shame on me); all I know is that you need to use policy-manager to allow it. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager not listing all networks
2010/7/3 Jacob Certain > I have two wifi routers. If I stand next to the main one with my > laptop I can connect and access the internet no problem. The other > router is in my office, and the bridging is messed up, so while I see > the essid and bssid using 'iwlist scanning' and nm-tool, I can't > connect to it. I should mention that the essid's are the same. > > If the two SSID's are the same, then ANY system will understand that they're part of the same network (that's the difference from a BSS to an ESS). > Now, my main router's signal still reaches to my office, just not as > strong as the borked router in my office. I need to be able to connect > to my main router while in the office. I added entries for both in > network-manager, but it doesn't show them in the list when I left > click the tray icon! How the do I connect to the network I want? > > I suggest you to pass a cable between the two routers (LAN ports), and disable the DHCP server from one of them. This way, you will have one of the routers working as an access point, and you can move freely from one place to other. wpa_supplicant will detect the strongest signal and roam you to it. As they're linked by the cable, you will see no difference on using one or another. If you can't deploy the cable, you have two options. The easiest is just change one of the SSIDs. The other is create two connections on NM, and bind each of them with the MAC address of the desired bridge. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Can't make NM work with local caching DNS resolver
2010/6/29 Robert Nichols > > I cannot simply hard code the upstream servers in /etc/dnsmasq.conf > because that would ignore what DHCP returns. > > And what's the problem in it? Are the server list returned so unstable, that you can get different upstream DNS servers in different connections? And what's the problem on using, for instance, OpenDNS as your upstream servers? They're fast and somewhat reliable. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Programmatically set the MTU for ALL Ethernet Adapters
Why don't you set the new MTU value in DHCP??? 2010/6/2 Jeffersen Sylvia > I am running into an issue with programmatically changing the MTU settings > for an Ethernet adapter within SUSE Enterprise 11. > > > > Issue: We have configured an OS to run within VMware Player that will be > transferred between multiple PCs on removable media. By nature (as well as > design) VMware will assign a new MAC Address (and therefore a new virtual > adapter) at each new PC, or location on the same PC. Because we are using > Lotus Notes 8.5.1, and Cisco AnnyConnect VPN Tunneling, we need to set the > MTU for the adapter **WITHOUT** user intervention. > > > > When Using **ifup** we can change global settings in the > “/etc/sysconfig/network/config” and adapter based settings in > “/etc/sysconfig/network/ifcfg.template” files, however once the adapter is > created, it must be manually activated and set to DHCP which requires “root” > permissions. > > > > When using NetworkManager, the process is automated for the creation and > default activation of the eth adapter, however the MTU must be set > manually, per adapter by the user. > > > > I am trying to find a way (similar to adjusting the configurations of > config/ifcfg.template) that will programmatically set the MTU for ALL new > eth adapters to 1492. > > > > Any ideas will be GREATLY appreciated… J > > Thanks Much > > Jeff Sylvia > > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > <>___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [RFC] Fast-user-switching plans
2010/5/27 Ludwig Nussel : >> >> I don't agree. Historically, network connections was a system-wide >> resource. But if you start thinking that a 3G connection is a personal >> resource, as personal as a cellphone, you will see that we need a >> better model that the one we use nowadays. This is because any user, >> and any process, may use this resource, without any control. > > Sure, you have to trust the computer you plug your device into. > And that's the point. If the system offers us the separation of resources like files, why can't a network connection be personal? >> You can imagine that one user start a P2P download, with some kind of >> client, said, amule, then leaves the machine's console. Then another >> user comes to the console, and opens a new session, without logging >> out the previous one. A classical case of "user switching". >> >> The he/she plugs in a 3g modem, and start a new connection. As the >> network settings, now, are system wide, the connection stablished by >> the user will be used by the amule process left by the previous user, >> also. > > A computer system shared by multiple users at the same time where > every user has to bring his own modem to get the system online? That > sounds rather unrealistic to me. > This is because you're thinking only on the system side. "I do have a network connection, why do this user needs another one?" But, try to look from the user point of view: "The network connection that this computer offers me doesn't fits my needs. I have this other connection that's better to me, but I don't want that other users on the same machine use it, as it is charged by traffic". ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [RFC] Fast-user-switching plans
2010/5/21 Ludwig Nussel : > Daniel Gnoutcheff wrote: >> I've been spending some time thinking about how to get N-M to work with >> fast-user-switching. Here are some possible solutions that I have heard of or >> thought of, presented for review. >> [...] >> Well, once again, thanks for reading all that! Comments, corrections, better >> ideas? > > 5. (or rather 2b?) Get rid of the user settings concept > > I always found that concept weird and the wrong way around. Those > network connections are not private to some user anyways. So always > have all network connection settings system global (ie in /etc). You > don't need to store an owner of a connection at all, owner is always > root. Use polkit to determine whether a user trying to edit, > start/stop network connections etc is allowed to do so. Credentials > such as passwords or client certificates could still be requested > from the frontend (ie the user that tries to start a connection) if > storing them in plain text globally isn't desired. > > cu > Ludwig > I don't agree. Historically, network connections was a system-wide resource. But if you start thinking that a 3G connection is a personal resource, as personal as a cellphone, you will see that we need a better model that the one we use nowadays. This is because any user, and any process, may use this resource, without any control. You can imagine that one user start a P2P download, with some kind of client, said, amule, then leaves the machine's console. Then another user comes to the console, and opens a new session, without logging out the previous one. A classical case of "user switching". The he/she plugs in a 3g modem, and start a new connection. As the network settings, now, are system wide, the connection stablished by the user will be used by the amule process left by the previous user, also. The more I think about it, the more I feel that we need a new model. :-/ ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: UMTS modem disappeared after upgrading to Ubuntu 10.04
Did you installed usb-modeswitch? Ubuntu Lucid uses usb-modeswitch 1.1, which is ***very*** different from the version used in Lucid. 2010/5/22 Massimiliano Polito : > Dear all, > > I had some problems with Ubuntu 9.10 (I had to reboot several times > before having the HSDPA modem working), I wrote to this list and you > suggested me that I should open a bug on Lunchpad. I did it: > > https://bugs.launchpad.net/ubuntu/+bug/506620 > > It seemed that Ubuntu 10.04 had solved the problem. I upgraded to it > and now my HSDPA modem has completely disappeared. I can see there is > a modem in dmesg but both nm-tool and ifconfig doesn't show it at all. > So I'm moved from a bad situation to a far worst one. > > I've asked for support on Ubuntu forum some weeks ago: > > http://ubuntuforums.org/showthread.php?t=1469486 > > I got ZERO replies. > > I wrote on Ubuntu Geek > > http://ubuntugeek.com/forum/index.php/topic,241.0.html > > and the only help I got was "reinstal eveything". Obviously, I'm not > going to reinstall everything, first of all because nobody can say for > certain that this will solve the problem, and because if I have to > install the OS from scratch I'm not going to install Ubuntu again, as > I had only troubles with UMTS. > > What can I do before throwing my laptop out of the window :-) ? > > I'm not subscribed to this list, if you reply please keep > massimiliano.pol...@gmail.com in CC. Thanks. > > Ciao, > Max > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Suggestion for Shared Connection: Reserve IPs for MAC Addresses
2010/4/22 Kay Wrobel > > * Reserve IP addresses for specific MAC addresses > * Do not hand out addresses from the defined range other than for > reserved MAC addresses. > These functions are handled, now, by the DHCP server... ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Add vpn connections disabled
Hi Damian, It will be a great help if you say which version of NM you're using, which distribution, and what internet connection you have. 2010/4/22 Damian Nadales Agut > I've seen a lot of posts of users complaining about this. In most of the > cases the problem was that the appropriate plug-ins weren't installed. > But I have installed the pptp, cisco, and openvpn plugins, I've > restarted dbus and the network manager, but the add button is disabled. > > I just want to connect to the vpn described here: >http://www.win.tue.nl/bcf/diensten/netwerk/vpn.php > > Thanks in advance, > Damian. > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Vlan support in NetworkManager
Hi, What kind of VLAN support you're thinking about? 2010/4/1 hadzhimurad ustarkhanov > Hi, > > I`d like to ask is it possible to add support VLAN in networkmanager. > > Thank you. > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Reboot for password to work
Yes, it haves an additional cost. No pain, no gain ;) But the authentication server may be set up by an automated script, or part of an installation process. And once installed, it may work with little maintenance. It may also work authenticating 802.1x wired connections, composing a bigger, complete, solution. 2010/3/19 Simon Geard > On Fri, 2010-03-19 at 01:04 -0300, José Queiroz wrote: > > > AES authenticate pairs of (user,password) against an authentication > > server --- RADIUS, TACACS+, etc ---, in a way that if your costumer > > don't pay another 15-minute session, you can log it off just > > invalidating his/her username, without messing with the other users. > > Which has the downside of requiring an authentication server, and > someone who knows how to maintain it. PSK works out of the box with the > cheap access point bought from the local electronics store, and can be > administered by a cafe owner with a minimum of technical knowledge... > > Simon. > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Reboot for password to work
Em 19 de março de 2010 00:37, Bill Moseley escreveu: > > > 2010/3/18 José Queiroz > > >> 2010/3/18 Bill Moseley >> >> >>> I use wireless at one location where the WPA password changes weekly. >> >> >> >> There should be a good case to use WPA-AES, instead of PSK. >> > > If I understand your comment, the password isn't changed to protect against > hacking. The wireless is in a cafe and I think they are probably trying to > keep people from buying a cup of coffee one time and then using the wireless > for weeks or longer without buying anything else. Or so I assume -- I'll ask > the reasoning next time I'm in the cafe. > > PSK stands for Pre-Shared Key, so anyone that knows this key can use the service. AES authenticate pairs of (user,password) against an authentication server --- RADIUS, TACACS+, etc ---, in a way that if your costumer don't pay another 15-minute session, you can log it off just invalidating his/her username, without messing with the other users. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Reboot for password to work
2010/3/18 Bill Moseley > > I use wireless at one location where the WPA password changes weekly. There should be a good case to use WPA-AES, instead of PSK. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disabling wireless networking.
Sorry for the naive answer, but, if you're not using wireless, why do you have a wireless adapter in your system? Is this some kind of mobile device, like a noteboot/netbook? Doesn't it have some kind of "rfkill" button??? 2010/3/15 Michael H. Warfield > Hey all, > > Pop question. This is one of my burning annoyances with NetworkManager > and maybe there's an easy way to do this and I just can't find it. > But... How do I disable wireless networking by default. I can disable > it but, the next time I log in, it's enabled again. I want it stone > cold dead unless I overtly and explicitly choose to enabled it and then > I want it off if I log out and log back in again. > > The problem is that I work in an environment that is very rich in IPv6 > support, at home and at work and on the road and at my colocation > facility. I have v6 everywhere. The problem is that NM brings up wlan0 > long after eth0 has been up and then the wlan0 interface gets hit with a > new RA (router advertisement) which then causes all the v6 traffic to be > routed out through the wireless WHICH I DO NOT WANT even though the v4 > default route is out eth0. Because wlan0 gets the RA later than the > eth0 address in response to its RD (router discovery) request, it has a > later expiration time on the routes so it gets preference over the eth0 > interface. This is by design. It's the way v6 is suppose to work and > is how you renumber autoconfed v6 networks. But is screws me over > royally when I'm in a situation where I've got a hard wired network > connection and the wireless is less than stable and keeps screwing up > all my v6 connections. Disabling it after logging in is useless because > it has already brought it up and loaded the v6 routes with a new default > and that then just breaks things. > > I want wireless off and to STAY OFF unless I want it on and know that I > want it on. But I can't find a sticky setting that basically tells it > to play dead and STAY DEAD. (The wireless "switch" on my laptop only > switches the bluetooth, unfortunately). > > Mike > -- > Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com > /\/\|=mhw=|\/\/ | (678) 463-0932 | > http://www.wittsend.com/mhw/ > NIC whois: MHW9 | An optimist believes we live in the best of > all > PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi and PPP support
Hi, It isn't usual to have a direct DSL connection which is both cabled and wireless. Seems that you have some device between your DSL connection and your wifi net. This device is, in general, a router. All you have to do, using a router, is connect your DSL modem to the router's WAN port, and configure the router to autenticate the PPPoE. This is a very confortable setup, as you don't need to worry with PPPoE in the local machines. 2010/3/1 Marco Antonelli : > Hello, > I am trying to configure a network connection with Ubuntu 9.10 through my > DSL modem, which is connected to my laptop through ethernet or wifi (I can > estabilish a connection to my home wlan). > I managed to establish a connection to the Internet with a DSL connection I > created with NetworkManager, but it only works if I attach the ethernet > cable, thus not through WiFi. > After some web-searching I ended up here: > http://mail.gnome.org/archives/networkmanager-list/2008-November/msg00218.html > were I read that NetworkManager at the time of that post was not supporting > PPP over Wifi. > I therefore tried pppoeconf, and it worked (!) until I rebooted: pppoeconf > messed up NetworkManager, so I could not connect to my WLAN. > My questions: > -Is the 'PPP over Wifi' feature scheduled in a next release or under > development? > -Does somebody know a way to configure pppoeconf which allows ppp over wifi > without messing up NetworkManager? > Thank you very much for this project. I am using GNU/Linux since RedHat 8 > and NetworkManager has been one of the best additions in all these years. > Marco > > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Prompt the user for login credentials?
Sorry for the naive question, but shouldn't be easier just use separate user accounts? Separate documents, separate desktop settings, separate action logs, ability to control who can and who can't use the machine... 2010/2/24 David Wagner : > I am using NetworkManager 0.7.1 to connect to a wireless network secured > with 802.1x and TTLS authentication. Everything is working great, but is it > possible to prompt the user for their logon credentials when establishing > the connection? > My situation is that this laptop will be loaned out to many different users > and they will login to linux with a single shared account. I would like to > pre-configure the wireless network setup, but have the users each use their > own network account to authenticate. As far as I have been able to find, > the only way I can save the configuration for this wireless network is to > enter a username and password that are stored in gconf and the gnome > keyring. Is it possible to not use a stored username and password and have > them supplied by the user every time a connection is established? > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Is there a way to get nm-applet to prompt for network security credentials through dbus?
2010/2/24 Greg Suarez : > > > > Sorry, I should've explained that I'm writing an application and I'm > interfacing with NetworkManager through dbus. > I want my application to get the list of wireless networks from > NetworkManager and allow the user to select it and > then tell NetworkManager to connect to the network. What I was hoping I > could do was to somehow tell nm-applet, > from my application, to prompt the user for security credentials. Then I > can tell NetworkManager to use the new connection. > Did I misunderstood you, or are you trying to replicate knetworkmanager behaviour? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager doesn't detect my device
What kind of device you have? May you post the output of "lsusb"? 2010/2/21 Jochen Wiedmann : > > Hi, > > I am trying to use my UTMS stick on a different machine running Fedora 11. I > was doing this on another machine with Fedora 10 and Fedora 11 before. > Details are described in my Blog on > > > http://grumpyapache.blogspot.com/2009/05/mobile-internet-with-fedora-10-and.html > http://grumpyapache.blogspot.com/2009/05/mobile-internet-with-fedora-10-and.html > > I am now following basically the same procedure. I get so far, that the > stick is recognized as a modem and the right kernel module is loaded: > > [a...@tethys ~]$ hal-find-by-capability --capability=modem > > /org/freedesktop/Hal/devices/usb_device_af0_6971_Serial_Number_if0_serial_unknown_1 > > /org/freedesktop/Hal/devices/usb_device_af0_6971_Serial_Number_if0_serial_unknown_0 > [a...@tethys ~]$ lsmod | grep option > option 20188 0 > usbserial 27572 1 option > > However, when I start nm-connection-editor and try to enter a new mobile > broadband device, then the device list is greyed out. So it looks like > NetworkManager doesn't recognize my device anyways. > > Any ideas, what might be wrong? > > Thanks, > > Jochen > > -- > View this message in context: > http://old.nabble.com/NetworkManager-doesn%27t-detect-my-device-tp27676275p27676275.html > Sent from the Gnome - NetworkManager mailing list archive at Nabble.com. > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ttyACM0, ttyUSB0, usb0 ???
Good news: I finally got NM working with my Onda MSA405HS modem. When you told about modem-manager, I thought on trying to trace it. I started it with "--debug" option, and it said: (...) ** Message: (ttyUSB2) opening serial device... ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling) ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'ATE0 V1' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- 'OK' ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CPIN?' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+CPIN: READYOK' ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'ATZ E0 V1 X4 &C1 +CMEE=1;+CFUN=1;' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- 'OK' ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling -> enabled) ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CPIN?' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+CPIN: READYOK' ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+COPS=0,,' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- 'OK' ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CREG?' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+CREG: 0,1OK' ** (modem-manager:24805): DEBUG: Registration state changed: 1 ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled -> registered) ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+COPS=3,2;+COPS?' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+COPS: 0,2,"72402",0OK' ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+COPS=3,0;+COPS?' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+COPS: 0,0,"TIM BRASIL",0OK' ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CSQ' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+CSQ: 15,99OK' ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CGDCONT?' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+CGDCONT: 1,"IP","www.tim.com.br","0.0.0.0",0,0+CGDCONT: 2,"IP","www.tim.com.br","0.0.0.0",0,0+CGDCONT: 3,"IP","bandalarga.claro.com.br","0.0.0.0",0,0OK' ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting) ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'ATD*99***1***1#' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- 'ERROR' ** (modem-manager:24805): DEBUG: Got failure code 100: Unknown error ** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CEER' ** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '+CEER: No cause information availableOK' ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> registered) (...) That's when I saw that NM was dialing "*99***1***1#", instead of "*99***1#", as I configured the connection. So I had the idea of changing the dial number to "*99#", as I saw in some documentations (despite the fact that I use "*99***1#" in wvdial), and it worked. Wow! Now, only two questions arise: 1) Why was NM addind "**1" to the dial number? It didn't done that on the other connection, using the Sony MD300 modem. 2) I had to use my chipmunk brain a little more than usual, to activate the debug mode of modem-manager, because just stopping it whilst NetworkManager was active was of no use --- NM restarted it immediately. So I had to first stop NM, then stop modem-manager. Maybe there should be a way to do that directly from NM. And if there is such a way, knetworkmanager should implement it... ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ttyACM0, ttyUSB0, usb0 ???
Em 4 de fevereiro de 2010 20:35, Dan Williams escreveu: > On Mon, 2010-02-01 at 10:11 -0200, José Queiroz wrote: >> Hi, >> >> I used to use a 3g usb dongle (Sony MD300). The first time I plugged >> it, it created a device called "ttyACM0", in a way that I could use >> wvdial and use pppd to conect it. >> >> But after some updates on NetworkManager, it started to show up as >> "usb0", and the pppd process was hidden in some way that wvdial could >> no more work. > > The Sony Ericsson MD300/MD400, F3507g, and F3607gw don't normally use > PPP. Instead, they provide a ttyACM0 control channel and a cdc-ether > usb0 network device. The control channel is used to set up the > connection, and then DHCP is used on the usb0 network device. > > Keep in mind that PPP is entirely pointless on 3G networks; the PPP is > solely between your computer and the dongle, and it actually slows > connections down to the point where you cannot achieve 3.6Mbps or > 7.2Mbps HSDPA transfer rates. Wow, this is interely new for me. "Fiat Lux". kkk. > >> Now I have another dongle (Onda MSA405HS), from another ISP, and when >> I plug it, it shows up as "ttyUSB2". I can easily connect using >> wvdial, but NetworkManager doesn't works. > > The ONDA/ZTE device does use PPP since it does not have the capability > to bypass PPP and use a network device. > >> My questions: >> >> 1) Why did the MD300 changed from "ttyACM0" to "usb0"? Will this be a >> rule, in all 3g connections? > > Not all cards support bypassing PPP. Only Ericsson and Option cards > support it at this time. > >> 2) Why didn't "ttyUSB2" turned into "usb0", also? > > Because the ZTE/ONDA device's firmware does not have the capability to > bypass PPP. > >> 3) The MSA405HS have 2 other devices, "ttyUSB0" and "ttyUSB1". Why do >> NM chooses to work with "ttyUSB2"? > > ModemManager automatically detects the modem ports that a device > provides, but sometimes the device only handles PPP on one of its ports. > Unfortunately we can't always automatically detect that, so ModemManager > needs a little help. > > You may need to update your version of ModemManager to get a new version > of the /lib/udev/rules.d/77-mm-zte-port-types.rules file. If you don't > see your device's USB IDs in that file, please tell me: > > 1) what the USB IDs of your device are > 2) what port works for PPP (ie, what you can use with wvdial) > > and I'll update that file which will make ModemManager use the correct > port. > Yes, they are there (0x19d2:0x0037). And, in fact, ttyUSB2 is the right one to use, as is the same one I use with wvdial. But, still, NM doesn't connects it. >> 4) How can I configure NM to give me more information, said, activate >> debug messages right from boot? > > Run it with --no-daemon. Or just look in /var/log/messages > or /var/log/daemon.log, depending on your distribution. > Kubuntu 9.10, NM 0.8~rc2-0ubuntu2~nmt3~karmic, KDE nm-applet 0.9~svn1040607-0ubuntu1~karmic1~ppa1. I dream of being able to debug just 3G connections, without messing with wireless. :) So I could fix this 3G connection, without getting offline in the meantime. -- OFF-Topic: Is it too hard to configure the list server, so our messages get replied automaticaly back to ??? I lost the account of times I sent answers in pvt just because I forgot to change the address of the reply... ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: how to find out why networkmanager does not connect any longer?
2010/2/2 Rolf Schumacher : > upgraded to debian sid 2.6.32-7 > kde 4.3.4 > network-manager 0.7.999 > > What I did: > I installed the package network-manager-kde, that is based on > network-manager. > I installed it on 2.6.32-6 and was happy: > I could choose from wlan ssid's surrounding me. > I could enter my 3G details and connected to two different umts networks > via two different chips: Huawei E160 and Ericsson F3507g. > > Than, I upgraded to the newer kernel (and maybe some other newer libs). > > What I got: > > Now, I'm no longer able to connect to a ssid. If I click on an ssid the > KNetworkManager dialog closes without any message, but no connetion is > done (in the past there was a rotating gear till connection). > Did you certified that the new kernel recognizes your wifi adapter? > Also the ttyasp interface is not shown any longer in favor of usb0. And > it constantly displays "no carrier" below it where my umts supplier used > to get displayed. My Sony MD300 modem also turned from "ttyACM" to "usb". But it works well, except that in the change, it stopped configuring default route. Had do edit the connection file by hand to fix it. But I blame it on the KDE NM applet, not in NM at all. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
ttyACM0, ttyUSB0, usb0 ???
Hi, I used to use a 3g usb dongle (Sony MD300). The first time I plugged it, it created a device called "ttyACM0", in a way that I could use wvdial and use pppd to conect it. But after some updates on NetworkManager, it started to show up as "usb0", and the pppd process was hidden in some way that wvdial could no more work. Now I have another dongle (Onda MSA405HS), from another ISP, and when I plug it, it shows up as "ttyUSB2". I can easily connect using wvdial, but NetworkManager doesn't works. My questions: 1) Why did the MD300 changed from "ttyACM0" to "usb0"? Will this be a rule, in all 3g connections? 2) Why didn't "ttyUSB2" turned into "usb0", also? 3) The MSA405HS have 2 other devices, "ttyUSB0" and "ttyUSB1". Why do NM chooses to work with "ttyUSB2"? 4) How can I configure NM to give me more information, said, activate debug messages right from boot? 5) I created a connection called "Claro3G" to use with the MD300, and another one called "TimWeb" to use with the MSA405HS. How can I assure that "Claro3G" will use the "usb0" device, and "TimWeb" will use "ttyUSB2"? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: net manager wireless disabled
There used to be a control in file /etc/NetworkManager/nm-system-settings that could be used to enable NM to manage interfaces configured in "/etc/network/interfaces": (...) [ifupdown] managed=false (...) --- Changing this line to "true" and restarting NM use to activate managing of those interfaces. I don't know if it still works in the latest NM versions. 2010/1/29 : > Dan > > You are another Network Manager angel! Now all is well with my network > manager. Hopefully all I will need at home is a key for my router and > all will be well there too. > > Cheers! > > > > >> On Fri, 2010-01-29 at 13:06 -0800, shelt...@berkeley.edu wrote: >>> Hi folks >>> >>> When I click the Network Manager Icon (Ubuntu 9.10) it says: >>> >>> Wired Networks >>> device not managed >> >> By default, the debian/Ubuntu plugin for NetworkManager settings will >> ignore any devices that are listed in /etc/networking/interfaces to >> preserve backwards compatibility with older releases. >> >> If you remove anything relating to 'eth0' >> from /etc/networking/interfaces, NM should then managed your wired >> device. >> >> Dan >> >> >> > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM vs clock
Are you using VMware to host this VM??? There are various issues with VMware and clock on Linux guests. 2010/1/25 Neal Becker : > I have a virtual machine running F12, setup to bring up eth0 at boot (nm > controlled). > > It kept failing dhcp. > Jan 25 04:32:14 localhost NetworkManager: DHCP: device eth0 state > changed (null) -> preinit > Jan 25 04:32:14 localhost dhclient[1310]: Listening on > LPF/eth0/08:00:27:b5:b3:6f > Jan 25 04:32:14 localhost dhclient[1310]: Sending on > LPF/eth0/08:00:27:b5:b3:6f > Jan 25 04:32:14 localhost dhclient[1310]: Sending on Socket/fallback > Jan 25 04:32:15 localhost dhclient[1310]: DHCPREQUEST on eth0 to > 255.255.255.255 port 67 > Jan 25 04:32:15 localhost dhclient[1310]: DHCPNAK from 10.32.111.2 > Jan 25 04:32:15 localhost NetworkManager: DHCP: device eth0 state > changed preinit -> expire > Jan 25 04:32:15 localhost NetworkManager: DHCP: device eth0 state > changed expire -> preinit > Jan 25 04:32:15 localhost dhclient[1310]: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 5 > Jan 25 09:32:16 localhost ntpd[1380]: ntpd 4.2@1.1612-o Wed Dec 9 > 11:49:11 UTC 2009 (1) > Jan 25 09:32:16 localhost ntpd[1381]: precision = 0.076 usec > Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #0 wildcard, > 0.0.0.0#123 Disabled > Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #1 wildcard, > ::#123 Disabled > Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #2 lo, ::1#123 > Enabled > Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #3 lo, > 127.0.0.1#123 Enabled > Jan 25 09:32:16 localhost ntpd[1381]: Listening on routing socket on fd #20 > for interface updates > Jan 25 09:32:16 localhost ntpd[1381]: kernel time sync status 2040 > Jan 25 09:32:16 localhost ntpd[1381]: frequency initialized -68.076 PPM from > /var/lib/ntp/drift > Jan 25 09:32:17 localhost dhclient[1310]: No DHCPOFFERS received. > > Notice the clock changed from 04:00 to 09:00 when ntpd started. Apparantly, > confusion over the clock time. > > Fixing the clock time seems to have solved the problem. I guess the time > change made dhclient think it should have timed out? > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Static address and resolvconf problem
2010/1/24 Michael Biebl : > If you install resolvconf, NM won't touch your /etc/resolv.conf file (at > least in current versions of NM in Debian and Ubuntu). > > Michael Interesting, didn't know that. But, and dhclient? I think that it is affected by resolvconf. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Static address and resolvconf problem
Because you didn't configured resolvconf to fix your nameserver in /etc/resolv.conf. You do that adding the line "nameserver 127.0.0.1" to "/etc/resolvconf/resolv.conf.d/head" and reconnecting. There may be a better way, indeed. 2010/1/24 Aldo Caruso : > That doesn't solve the problem: when I select static configuration and > reboot, the nameserver entry is deleted from /etc/resolv.conf ( whichever it > is, 127.0.0.1 or other ). > > José Queiroz escribió: > > Why don't you install a dns server on your machine? This way you can > use resolvconf to fix "nameserver 127.0.0.1" to you, and never again > need to guess what is your dns server right now... > > 2010/1/23 Aldo Caruso : > > > Hi, > I have Ubuntu 8.0, two network manager configurations corresponding to two > locations: one when I'm at home with a static IP address, and the other for > using wi fi with dynamic IP addressed. > Everything worked well until I installed the resolvconf package. > When I use the dynamic configuration there is no problem. If instead I > select the static one, everything works fine until I reboot my machine. > After a boot, the file /etc/resolv.conf has no entries (only default > comments), and I must reselect the static configuration from network manager > in order to get the static DNSs listed in /etc/resolv.conf > > Thanks for any clue. > Aldo > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Static address and resolvconf problem
Why don't you install a dns server on your machine? This way you can use resolvconf to fix "nameserver 127.0.0.1" to you, and never again need to guess what is your dns server right now... 2010/1/23 Aldo Caruso : > Hi, > I have Ubuntu 8.0, two network manager configurations corresponding to two > locations: one when I'm at home with a static IP address, and the other for > using wi fi with dynamic IP addressed. > Everything worked well until I installed the resolvconf package. > When I use the dynamic configuration there is no problem. If instead I > select the static one, everything works fine until I reboot my machine. > After a boot, the file /etc/resolv.conf has no entries (only default > comments), and I must reselect the static configuration from network manager > in order to get the static DNSs listed in /etc/resolv.conf > > Thanks for any clue. > Aldo > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DHCP timeout is too short for this college network
2010/1/22 Daniel Gnoutcheff : > From what I've seen, it looks like dhclient already does something similar. > > If I put "timeout 45;" in dhclient.conf and then run dhclient on a network > where no DHCP servers are present (i.e. no OFFERs are received), then > dhclient does indeed timeout in 45 seconds. > > However, as soon as it gets an OFFER, it seems that the 45 second countdown > stops. dhclient then proceeds to try and get an ACK, and this process seems > to be subject to a separate (hard coded?) timeout. If that fails, then > dhclient returns to the DISCOVER stage and once again waits 45 seconds for > an OFFER. > > So the good news is, dhclient is already setup so that it times out > relatively quickly when DHCP servers are not present, and it's also willing > to wait longer when dealing with lazy servers. > > The bad news is that this behavior is not well documented, and I don't know > if there are any limits on how many times it will "loop" like this. If I > were to hit a broken DHCP server that always sent OFFERs but never sent > ACKs, it's possible that dhclient would never time out. But I'd argue that > this would be a dhclient bug that may be worth fixing anyway. > Maybe this second timeout is defined in the RFCs. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to let NM prompt duplicate ip address?
Some systems fire an arp request on the new IP address prior activating it, if there is an answer, it's sure that the address is a duplicate. But the inverse isn't true: if the station with the duplicated address isn't operational in the moment you test it (e.g. powered down), the test will fail, and NM will incorrectly assume that the address is free. Maybe another daemon (e.g. AVAHI) could monitor for "gratuitous ARPs" and syslog the duplicates. 2010/1/19 Bin Li : > Hi, > > When assigning a static ip address by NM, and this ip addresses > already be in use. > The NM don't prompt any information, I use the openSUSE 11.2. > > Any idea? > Thanks! > > Sincerely Yours, > > Bin Li > > http://cn.opensuse.org > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Is accounting supported?
What about using SNMP data to gather accounting on interfaces? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Connection sharing with WPA/WPA2
2010/1/18 Marc Herbert : > Gonsolo a écrit : >> I think my WG511 card would allow WPA > > Note that it is not because a card works as a WPA station that it works > as an WPA Access Point. > I agree. I remember that when I was testing a rt61-based card, I had problems when tried to use WPA with ad-hoc mode. I had to switch to the ndiswrapper driver to do that. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DHCP timeout is too short for this college network
2010/1/11 Sven Nielsen : > Ask the dhcp team on your campus why they are giving away DHCP leases > for 3! days (286274 seconds): > >> >> Jan 10 21:40:12 DHCPACK of 149.106.215.247 from 149.106.192.253 >> >> Jan 10 21:40:13 bound to 149.106.215.247 -- renewal in 286274 > seconds. > > Maybe the DHCP server is continously short on free IP addresses because > many addresses that are actually free, are still bound to clients that > connected e.g. 2 days ago. (It surely gets hundreds of requests every > day.) Might be that every time it tries to process a DHCP requests, it > has no addresses left and then has to go through all addresses manually > by way of pinging them to find out which ones are not in use anymore > before it finds a free address. This might easily be one of the causes > for the long delays. I understand that, if the address pool is exausted, the DHCP server should respond immediatelly with a DHCPNACK, and not start a ping sweep to find free addresses. > > Also, perhaps the DHCP configuration should be divided into two address > pools (it it isn't already), one address pool for resident computers > (Destkop PCs and laptops of university staff), and another pool for > student laptops (unknown DHCP clients). The only way I can think of to implement this division without separating "known" and "unknown" clients in independent broadcast domains (by means of physical separated switches, or even VLANs), is pre-registering the known clients in dhcp configuration. Is there a better way to do that? o_O ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
