AW: Re: howto disable default multiple device activation?
>Do you have any reasons to hate it, I for instance would - although much less on a unixoid OS than on *eew* Windoze. With multiple IP interfaces, there is a strong tendency for nonunicast IP packets leaving the box via the "wrong" interface - regardless of the source address being written into the packet. So in general, I would see use cases for not automatically having a wired and a wireless interfaces active at the same time. Some Laptop firmwares even have such a "Wifi XOR LAN" switch you can activate in their BIOSs. >The fastest device is always used for new TCP connections, so it's not like >it'll slow anything down. How does TCP know about an interface's speed? I would assume that it just passes it's segments to the IP layer - which will then forward packets according to what the routing table says. >Here's a specific example why it's good: I'm connected through my wifi >device only and have a bunch of open TCP connections (ssh, irc, ...). >Then I need to transfer a large file from the local network. I plug in >the cable (to make it faster) and start the transfer. The way you describe it, it sounds like a small setup witha single router/firewall towards the internet, with some (file) server on your internal LAN. So both your WiFi and LAN NICs will probably have addresses from the same subnet and use the same router/firewall to reach non-local networks. As soon as your LAN NIC is up, the routing table gets modified to reach the local LAN via that interface and maybe another default route, pointing to the same router/firewall. Like this, TCP connections to the outside world will survive and not seem out-of-state to that firewall. But what happens to your routing table once you get DHCP lease and default route from a completely different LAN? Will the new default route take precedence over the existing one? How do you prevent problems if your now dual-homed hosts needs to talk to hosts beyond the respective local subnet - on both interfaces simultaneously? >My point is, there's simply no reason to deactivate the previously active >device, Yes. There are use cases where this is mandatory. As you pointed out - this needs to be taken care of by the administrator. regards Marc ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
manual mode options
Hi At work I have a wireless network with static address and wpa-psk protection but and don't broadcast the ssid. So I've configured nm in manual mode to use the statical ip and save this profile/location but to work I'have to add manualy in the file /etc/network/interface the options wpa-scan-ssid 1!! It's possible save this option in the profile/location of nm and where nm save/store the configuration of the manual profiles, I know that in roaming save the parameters in gconf at system/networking/wireless/networks/SSID but where in manual mode??? thnx everyone Tiscali.Fax: ricevi gratis sulla tua email e invii a 12 cent per pagina senza scatto alla risposta ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager-list Digest, Vol 39, Issue 18
will you pls quit sending to me, -- Original Message: - From:[EMAIL PROTECTED] To: networkmanager-list@gnome.org Subject: NetworkManager-list Digest, Vol 39, Issue 18 Date:Wed, 5 Dec 2007 19:08:48 + > Send NetworkManager-list mailing list submissions to > networkmanager-list@gnome.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.gnome.org/mailman/listinfo/networkmanager-list > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NetworkManager-list digest..." > > > Today's Topics: > >1. Re: Fwd: NetworkManager no-go (Dan Williams) >2. Re: ppp using NM (Tambet Ingo) >3. Re: scan list limitation -- doesn't like 127 APs? (Derek Atkins) >4. Re: Another dropped connection with iwl3945 and NM-0.6.5 on > FC7 (Derek Atkins) >5. Re: ppp using NM (Jon Escombe) >6. Re: VPN API (Jon Escombe) >7. Re: ppp using NM (Dan Williams) >8. Re: VPN API (Casey Harkins) > > > ------ > > Message: 1 > Date: Wed, 05 Dec 2007 11:56:23 -0500 > From: Dan Williams <[EMAIL PROTECTED]> > Subject: Re: Fwd: NetworkManager no-go > To: Yasha Karant <[EMAIL PROTECTED]> > Cc: networkmanager-list@gnome.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > On Tue, 2007-12-04 at 19:07 -0800, Yasha Karant wrote: > > I have been informed that the behavior below evidently is a bug > > in NetworkManager. I am using NetworkManager Applet 0.6.4 under > > RHEL 5, and NetworkManager and NetworkManagerDispatcher 0.6.5 . > > > > NetworkManager did not offer me any choices in network, nor did it > > change from the pre-existing channel 11 under the circumstances > > below. > > > > Is this a bug? If so, what is the fix? > > Best thing to do is to file a bug in Red Hat bugzilla and then we can > diagnose this issue further. If you could put some more details into > the bug report, like: > > 1) What kernel version, what wireless card, and what driver the card is > using > > 2) Attach a /var/log/messages that shows a NetworkManager connection > attempt to the bug report > > #2 is important; without that it's hard to figure out where things are > going wrong. > > Thanks, > Dan > > > > > > I have now tried NetworkManager on the University 802.11g from > > my office. No go. > > > > Here is the output from scan (I wrote a small script to run > > the scan > > and remind me that I needed to be root for the scan to work -- > > output > > captured via script in a typescript file): > > > > Script started on Tue 04 Dec 2007 11:34:40 AM PST > > ^[]0;[EMAIL PROTECTED]:[EMAIL PROTECTED] ~]$ su > > Password: > > ^[]0;[EMAIL PROTECTED]:/home/[EMAIL PROTECTED] > > ykarant]# ./iwlist-scan > > > > You need to be root to get a current scan > > > > eth1 Scan completed : > > Cell 01 - Address: 00:12:00:51:BC:60 > > ESSID:"CSUSB" > > Protocol:IEEE 802.11bg > > Mode:Master > > Channel:1 > > Encryption key:off > > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 > > Mb/s; 9 Mb/s > > 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 > > Mb/s; 36 Mb/s > > 48 Mb/s; 54 Mb/s > > Quality=82/100 Signal level=-48 dBm > > Extra: Last beacon: 27ms ago > > Cell 02 - Address: 00:15:F9:A6:76:80 > > ESSID:"CSUSB" > > Protocol:IEEE 802.11bg > > Mode:Master > > Channel:6 > > Encryption key:off > > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 > > Mb/s; 9 Mb/s > > 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 > > Mb/s; 36 Mb/s >
VPN Connections and DNS configurations
Hi there, I'd like to know if theres is a way to manualy enter DNS server names and domains when using M$ PPTP and OpenVPN connections under Network Manager. Can i do that editing each connections configuration file? where are theese files located? Thanks in advance ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Add support of LEAP with WPA
Is it possible to add support of LEAP ? I've done it easily using ubuntu source package. Regards Daniel GARY ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
networkmanager doesn't appear
hi! i've just installed the following packages on my ubuntu system: - network-manager - network-manager-gnome afterwards i've added "sn-applet --sm-disable" to Session > Startup Programs and rebootet my notebook as recommended in a manual. but finally, when the machine started up i couldn't find or even start the networkmanager because it doesn't seem to be installed?! if i check in Synaptic Package manager everything seems to be installed properly. why that? could anybody help me? thanks a lot! greeetz stefan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Latest Ndiswrapper
Yes! With ndiswrapper-1.12 isn't necessary workarround to get it work ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Security combinations status?
What's the status of include security policies combinations (per example WAP and second stage PAP)? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Monitor Capabilities in NM
I think that an icon as gnome-netstatus-applet show all information that you want: wired/wireless, wireless signal strength and traffic ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: NetworkManager FC5 -- No WEP key
I have contributed to the patch with the necessary code for ndiswrapper, my problem was the same one that yours nm-device-802-11-wireless.patch Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager FC5 -- No WEP key
See Robert Love's wireless driver work around. A question, why you don't use gentoo? ;) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: pptp connection fails
NetworkManager finalizes spontaneously >On Tue, 2006-03-07 at 13:24 +0100, [EMAIL PROTECTED] wrote: >> pptp connection fails and kill NetworkManager >Did you hit Ctrl-C here? Or is that something else that's sending NM a >TERM? >Mar 7 13:21:39 eclipse NetworkManager: nm_signal_handler (): Caught signal 15, shutting down normally. >Mar 7 13:21:39 eclipse NetworkManager: Caught terminiation signal >Mar 7 13:21:39 eclipse NetworkManager: nm_vpn_service_process_signal (): VPN failed for service 'org.freedesktop.NetworkManager.pptp', signal 'ConnectFailed', with message 'VPN Connection failed'. >Mar 7 13:21:39 eclipse NetworkManager: [1141734099.819149] nm_print_open_socks (): Open Sockets List: >Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
pptp connection fails
pptp connection fails and kill NetworkManager NM.log Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: WPA wireless connection fails
if I choose "Other wireless network" from the applet's menu and fill in the information for WPA, the result is the same. Some idea? >On Mon, 2006-03-06 at 17:36 +0100, [EMAIL PROTECTED] wrote: >> NetworkManager doesn't connect to WPA wireless nectworks for >> me. wpasupplicant connect without problems. >The log doesn't really say much, it appears that NM hasn't even been >told to try association with the access point? What happens if you >choose "Other wireless network" from the applet's menu and fill in the >information for WPA? Can you post the log from that? This log isn't >long enough. >Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA wireless connection fails
With non-security wireless network fails too. Only work fine with WEP wireless network. NM2.log Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
WPA wireless connection fails
NetworkManager doesn't connect to WPA wireless nectworks for me. wpasupplicant connect without problems. NM.log Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-vpn-properties fail
I need to compile and install vpnc an open-vpn too, I only had compiled pptp. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-vpn-properties fail
With new 0.6 when non root users run nm-vpn-properties it fails without messages. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: spanish translation
This works for new 0.6 es.po Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: ANNOUNCE: NetworkManager 0.6 Release
Thanks! The error now is: In file included from NetworkManagerMain.h:28, from nm-device-802-3-ethernet.c:32: /usr/include/hal/libhal.h:306: aviso: la declaración de 'index' oscurece una declaración global /usr/include/string.h:304: aviso: aquí está la declaración oscurecida In file included from /usr/include/linux/mii.h:12, from nm-device-802-3-ethernet.c:395: /usr/include/linux/if.h:95: error: redefinición de `struct ifmap' /usr/include/linux/if.h:131: error: redefinición de `struct ifreq' /usr/include/linux/if.h:181: error: redefinición de `struct ifconf' make[3]: *** [NetworkManager-nm-device-802-3-ethernet.o] Error 1 make[3]: Leaving directory `/usr/src/NetworkManager/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/NetworkManager/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/NetworkManager' make: *** [all] Error 2 >On Sat, 2006-03-04 at 16:45 +0100, [EMAIL PROTECTED] wrote: >> When compile CVS I receive this error: >> In file included from ../../src/NetworkManagerMain.h:28, >> from ../../src/NetworkManagerDbusUtils.h:31, >> from nm-dbus-vpn.h:25, >> from nm-vpn-connection.c:25: >> /usr/include/hal/libhal.h:306: warning: declaration of 'index' >> shadows a global declaration >> /usr/include/string.h:304: warning: shadowed declaration is here >> make[3]: *** [libvpn_manager_la-nm-vpn-connection.lo] Error 1 >> make[3]: Leaving directory >> `/usr/src/NetworkManager/src/vpn-manager' >> make[2]: *** [all-recursive] Error 1 >> make[2]: Leaving directory `/usr/src/NetworkManager/src' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/usr/src/NetworkManager' >> make: *** [all] Error 2 >> >> What is wrong? >Edit configure.in and get rid of the -Werror flag >-- >Paul Betts <[EMAIL PROTECTED]> ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ANNOUNCE: NetworkManager 0.6 Release
When compile CVS I receive this error: In file included from ../../src/NetworkManagerMain.h:28, from ../../src/NetworkManagerDbusUtils.h:31, from nm-dbus-vpn.h:25, from nm-vpn-connection.c:25: /usr/include/hal/libhal.h:306: warning: declaration of 'index' shadows a global declaration /usr/include/string.h:304: warning: shadowed declaration is here make[3]: *** [libvpn_manager_la-nm-vpn-connection.lo] Error 1 make[3]: Leaving directory `/usr/src/NetworkManager/src/vpn-manager' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/NetworkManager/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/NetworkManager' make: *** [all] Error 2 What is wrong? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: wireless driver workarounds
>On Sat, 2006-03-04 at 13:15 +0100, [EMAIL PROTECTED] wrote: >> Firstly, sorry about my english one more time. >> >> The first hunk desn't work correctly because if this is true: >> "Must be in infrastructure mode during scan, otherwise we >> don't get a full list of scan results. Scanning doesn't work >> well in Ad-Hoc mode :( " >> If device is in Ad-Hoc mode but >> nm_device_802_11_wireless_get_mode return IW_MODE_AUTO, >> scanning doesn't work well. >> In my opinion solution is not modify this code, would be >> necessary "force" mode never is IW_MODE_AUTO when connect, if >> it's posible. >If we were in Ad-Hoc mode, though, get_mode() won't return IW_MODE_AUTO. >Robert Love But If I was in Infraestructure mode get_mode() return IW_MODE_AUTO, is it not the same for Ad-Hoc mode? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Re: ANNOUNCE: NetworkManager 0.6 Release
I'm using pptp and it works fine for me >On Saturday 04 March 2006 08:11, Dan Williams wrote: >> Notable Improvements >> >> >> * WPA/WPA2 Personal and Enterprise support >> * Two new VPN services; openvpn and pptp >hmm, is someone really using pptp? It's not very stable and at least for >my university scenario (nothing unusal I think) it doesn't work. I have >some patches localy and will send it to the ML. But, is someone using it >successfuly? >Nikolaus >-- >out of signatures >___ >NetworkManager-list mailing list >http://mail.gnome.org/mailman/listinfo/networkmanager-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
scanning continuously?
nm-applet causes that NetworkManager is scanning continuously, is really necessary? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wireless driver workarounds
Firstly, sorry about my english one more time. The first hunk desn't work correctly because if this is true: "Must be in infrastructure mode during scan, otherwise we don't get a full list of scan results. Scanning doesn't work well in Ad-Hoc mode :( " If device is in Ad-Hoc mode but nm_device_802_11_wireless_get_mode return IW_MODE_AUTO, scanning doesn't work well. In my opinion solution is not modify this code, would be necessary "force" mode never is IW_MODE_AUTO when connect, if it's posible. >Attached patch is a collection of workarounds for madwifi, orinoco, and >ndiswrapper that I have worked on or that have been posted to this list. >We are probably not going to merge any of this. If NM does not work for >you but works with this patch, we would like to know. > Robert Love ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wireless driver workarounds
Modified patch to work with gentopia-overlay, and some small change nmwirelessdriverworkaroundsrml-aj2r.patch Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
>aj2r, just as an FYI, you don't need dynamic allocations here. > const char *driver = "madwifi"; >is sufficient. As it stands, this code allocates both a static >character array and a dynamic one. Just a tip ;-) > Robert Love Ok, thanks. But later you don't make driver="ndiswrapper" because you are using non reserved memory, no? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
spanish translation
Added translation of notify messages, Where have I to send it so that it is including? P.D. -> My english is very bad but I translate english to spanish good. es.po Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
> if (nm_device_802_11_wireless_get_mode (self) == mode)
> return TRUE;
This is true, but if nm_device_802_11_wireless_get_mode
(self) is IW_MODE_AUTO and mode is IW_MODE_INFRA, condition is
false because device mode is changed.
This patch work fine for me and "all changes are needed"
--- NetworkManager-0.5.2/src/nm-device-802-11-wireless.c
2006-02-21 11:39:33.0 +0100
+++ /root/Desktop/nm-device-802-11-wireless.c 2006-03-03
13:55:08.0 +0100
@@ -1808,7 +1808,10 @@
/* Must be in infrastructure mode during scan, otherwise
we don't get a full
* list of scan results. Scanning doesn't work well in
Ad-Hoc mode :(
*/
- nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+
+ if (nm_device_802_11_wireless_get_mode (self) ==
IW_MODE_ADHOC) {
+ nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+ }
nm_device_802_11_wireless_set_frequency (self, 0);
wrq.u.data.pointer = NULL;
@@ -2282,13 +2285,27 @@
const char *iface = nm_device_get_iface (NM_DEVICE (self));
gbooleansuccess = FALSE;
int tries = 0;
+ char * driver;
if (!(ctrl = wpa_ctrl_open (WPA_SUPPLICANT_GLOBAL_SOCKET,
NM_RUN_DIR)))
goto exit;
+ if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
"ndiswrapper")) {
+ driver= g_malloc(sizeof(char)*(strlen("ndiswrapper")+1));
+ driver= strcpy(driver, "ndiswrapper");
+ }
+ else if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
"ath_pci")) {
+ driver= g_malloc(sizeof(char)*(strlen("madwifi")+1));
+ driver= strcpy(driver, "madwifi");
+ }
+ else {
+ driver= g_malloc(sizeof(char)*(strlen("wext")+1));
+ driver= strcpy(driver, "wext");
+ }
+
/* wpa_cli -g/var/run/wpa_supplicant-global interface_add
eth1 "" wext /var/run/wpa_supplicant */
if (!nm_utils_supplicant_request_with_check (ctrl, "OK",
__func__, NULL,
- "INTERFACE_ADD %s\t\twext\t"
WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface))
+ "INTERFACE_ADD %s\t\t%s\t" WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface, driver))
goto exit;
wpa_ctrl_close (ctrl);
@@ -2308,6 +2325,7 @@
success = TRUE;
exit:
+ g_free (driver);
return success;
}
>On Thu, 2006-03-02 at 10:15 -0500, Dan Williams wrote:
>> On Thu, 2006-03-02 at 10:03 -0500, Robert Love wrote:
>> > On Thu, 2006-03-02 at 09:49 -0500, Dan Williams wrote:
>> >
>> > > So which hunk of this patch seems to fix the problem?
The first part
>> > > for the set_mode, or the second part passing the
ndiswrapper driver to
>> > > wpa_supplicant?
>> >
>> > The first hunk. I just checked a variant into CVS.
>>
>> The reason this hunk exists is really for just adhoc. Same
for the
>> frequency set to 0, I think. If you want to move both of
them into
>> if (orig_mode == IW_MODE_ADHOC)
>>
>> block just above, that would be fine. I initially observed
with prism54
>> cards that adhoc mode pretty much didn't work at all unless
the mode was
>> infrastructure and the bitrate was unlocked.
Unfortunately, the bitrate
>> had to be locked during normal adhoc operation, otherwise
you never got
>> any traffic. Now that our custom adhoc setup code is gone,
I think we
>> can remove that bitrate unlock line.
>>
>> Note that NM only supports two modes right now, INFRA and
ADHOC. The
>> other mode is MASTER, and of course we don't do that yet.
>On second look, your commit is fine. I forgot that if
wpa_supplicant
>sets up the stuff, we need to switch it back anyway.
>However, there's another problem... The code for set_mode
already
>checks to see what the mode was, and if you request to set
the mode that
>the card is in already, it just returns without doing anything:
> if (nm_device_802_11_wireless_get_mode (self) == mode)
> return TRUE;
>So I'm not sure what your commit fixes? It's more likely
that the
>driver here dislikes the frequency set, and that we should
only unlock
>the frequency when the card is in ad-hoc mode.
>Candidate patch attached, does this fix the issue?
>Dan
nm-ndiswrapper2.patch
Description: application/data
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
I've the same problem (broadcom+ndiswrapper). See my post "wep key lost", do you lost wep key too? My english sucks, sorry. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
This patch solve the problem:
Index: src/nm-device-802-11-wireless.c
===
RCS file:
/cvs/gnome/NetworkManager/src/nm-device-802-11-wireless.c,v
--- src/nm-device-802-11-wireless.c 2006-02-21
11:39:33.0 +0100
+++ src/nm-device-802-11-wireless.c 2006-03-01
19:06:34.0 +0100
@@ -1808,8 +1808,10 @@
/* Must be in infrastructure mode during scan, otherwise
we don't get a full
* list of scan results. Scanning doesn't work well in
Ad-Hoc mode :(
*/
- nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
- nm_device_802_11_wireless_set_frequency (self, 0);
+ if (nm_device_802_11_wireless_get_mode (self) ==
IW_MODE_ADHOC) {
+ nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+ nm_device_802_11_wireless_set_frequency (self,
0);
+ }
wrq.u.data.pointer = NULL;
wrq.u.data.flags = 0;
@@ -2282,13 +2284,23 @@
const char *iface = nm_device_get_iface (NM_DEVICE (self));
gbooleansuccess = FALSE;
int tries = 0;
+ char * driver;
if (!(ctrl = wpa_ctrl_open (WPA_SUPPLICANT_GLOBAL_SOCKET,
NM_RUN_DIR)))
goto exit;
+ if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
"ndiswrapper")) {
+ driver= g_malloc(sizeof(char)*(strlen("ndiswrapper")+1));
+ driver= strcpy(driver, "ndiswrapper");
+ }
+ else {
+ driver= g_malloc(sizeof(char)*(strlen("wext")+1));
+ driver= strcpy(driver, "wext");
+ }
+
/* wpa_cli -g/var/run/wpa_supplicant-global interface_add
eth1 "" wext /var/run/wpa_supplicant */
if (!nm_utils_supplicant_request_with_check (ctrl, "OK",
__func__, NULL,
- "INTERFACE_ADD %s\t\twext\t"
WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface))
+ "INTERFACE_ADD %s\t\t%s\t" WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface, driver))
goto exit;
wpa_ctrl_close (ctrl);
@@ -2308,6 +2320,7 @@
success = TRUE;
exit:
+ g_free (driver);
return success;
}
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wep key lost
This patch solve the problem:
Index: src/nm-device-802-11-wireless.c
===
RCS file:
/cvs/gnome/NetworkManager/src/nm-device-802-11-wireless.c,v
--- src/nm-device-802-11-wireless.c 2006-02-21
11:39:33.0 +0100
+++ src/nm-device-802-11-wireless.c 2006-03-01
19:06:34.0 +0100
@@ -1808,8 +1808,10 @@
/* Must be in infrastructure mode during scan, otherwise
we don't get a full
* list of scan results. Scanning doesn't work well in
Ad-Hoc mode :(
*/
- nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
- nm_device_802_11_wireless_set_frequency (self, 0);
+ if (nm_device_802_11_wireless_get_mode (self) ==
IW_MODE_ADHOC) {
+ nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+ nm_device_802_11_wireless_set_frequency (self,
0);
+ }
wrq.u.data.pointer = NULL;
wrq.u.data.flags = 0;
@@ -2282,13 +2284,23 @@
const char *iface = nm_device_get_iface (NM_DEVICE (self));
gbooleansuccess = FALSE;
int tries = 0;
+ char * driver;
if (!(ctrl = wpa_ctrl_open (WPA_SUPPLICANT_GLOBAL_SOCKET,
NM_RUN_DIR)))
goto exit;
+ if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
"ndiswrapper")) {
+ driver= g_malloc(sizeof(char)*(strlen("ndiswrapper")+1));
+ driver= strcpy(driver, "ndiswrapper");
+ }
+ else {
+ driver= g_malloc(sizeof(char)*(strlen("wext")+1));
+ driver= strcpy(driver, "wext");
+ }
+
/* wpa_cli -g/var/run/wpa_supplicant-global interface_add
eth1 "" wext /var/run/wpa_supplicant */
if (!nm_utils_supplicant_request_with_check (ctrl, "OK",
__func__, NULL,
- "INTERFACE_ADD %s\t\twext\t"
WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface))
+ "INTERFACE_ADD %s\t\t%s\t" WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface, driver))
goto exit;
wpa_ctrl_close (ctrl);
@@ -2308,6 +2320,7 @@
success = TRUE;
exit:
+ g_free (driver);
return success;
}
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Strange behaviour from 0.5.1 and 2006-02-21 cvs
man dhclient: "The -x argument enables eXtended option information to be created in the -s dhclient-script environment, which would allow applications running in that environment to handle options they do not know about in advance." With -x in dhclient do you have problem? >I'm having a strange problem with NetworkManager 0.5.1 and 0.5.2 from >2006-02-21 (The two current builds in the Gentopia portage overlay) >NetworkManager will set the essid and the wep key for the network properly, >it'll get an ip address and set a route, and then it will just... hang there, >spinning its icon ... and then drop the ip/route, and ask for the key again. >The app versions are: >dhcdbd is 1.12 (I made a modification to this as an experiment, patched out >the use of -x with dhclient) >dbus is 0.60 >hal is 0.5.6 >I would tentatively guess that this is an issue with dhcdbd not telling >NetworkManager that everything worked, and it timing out and killing the >dhclient process, but like I said, that's just a guess. >Has anyone seen something like this? >___ >NetworkManager-list mailing list >http://mail.gnome.org/mailman/listinfo/networkmanager-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: Wireless silently disconnects?
This patch created by me solve the problem:
Index: src/nm-device-802-11-wireless.c
===
RCS file:
/cvs/gnome/NetworkManager/src/nm-device-802-11-wireless.c,v
--- src/nm-device-802-11-wireless.c 2006-02-21
11:39:33.0 +0100
+++ src/nm-device-802-11-wireless.c 2006-03-01
19:06:34.0 +0100
@@ -1808,8 +1808,10 @@
/* Must be in infrastructure mode during scan, otherwise
we don't get a full
* list of scan results. Scanning doesn't work well in
Ad-Hoc mode :(
*/
- nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
- nm_device_802_11_wireless_set_frequency (self, 0);
+ if (nm_device_802_11_wireless_get_mode (self) ==
IW_MODE_ADHOC) {
+ nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+ nm_device_802_11_wireless_set_frequency (self,
0);
+ }
wrq.u.data.pointer = NULL;
wrq.u.data.flags = 0;
@@ -2282,13 +2284,23 @@
const char *iface = nm_device_get_iface (NM_DEVICE (self));
gbooleansuccess = FALSE;
int tries = 0;
+ char * driver;
if (!(ctrl = wpa_ctrl_open (WPA_SUPPLICANT_GLOBAL_SOCKET,
NM_RUN_DIR)))
goto exit;
+ if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
"ndiswrapper")) {
+ driver= g_malloc(sizeof(char)*(strlen("ndiswrapper")+1));
+ driver= strcpy(driver, "ndiswrapper");
+ }
+ else {
+ driver= g_malloc(sizeof(char)*(strlen("wext")+1));
+ driver= strcpy(driver, "wext");
+ }
+
/* wpa_cli -g/var/run/wpa_supplicant-global interface_add
eth1 "" wext /var/run/wpa_supplicant */
if (!nm_utils_supplicant_request_with_check (ctrl, "OK",
__func__, NULL,
- "INTERFACE_ADD %s\t\twext\t"
WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface))
+ "INTERFACE_ADD %s\t\t%s\t" WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface, driver))
goto exit;
wpa_ctrl_close (ctrl);
@@ -2308,6 +2320,7 @@
success = TRUE;
exit:
+ g_free (driver);
return success;
}
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wep key lost
This patch created by me solve the problem:
Index: src/nm-device-802-11-wireless.c
===
RCS file:
/cvs/gnome/NetworkManager/src/nm-device-802-11-wireless.c,v
--- src/nm-device-802-11-wireless.c 2006-02-21
11:39:33.0 +0100
+++ src/nm-device-802-11-wireless.c 2006-03-01
19:06:34.0 +0100
@@ -1808,8 +1808,10 @@
/* Must be in infrastructure mode during scan, otherwise
we don't get a full
* list of scan results. Scanning doesn't work well in
Ad-Hoc mode :(
*/
- nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
- nm_device_802_11_wireless_set_frequency (self, 0);
+ if (nm_device_802_11_wireless_get_mode (self) ==
IW_MODE_ADHOC) {
+ nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+ nm_device_802_11_wireless_set_frequency (self,
0);
+ }
wrq.u.data.pointer = NULL;
wrq.u.data.flags = 0;
@@ -2282,13 +2284,23 @@
const char *iface = nm_device_get_iface (NM_DEVICE (self));
gbooleansuccess = FALSE;
int tries = 0;
+ char * driver;
if (!(ctrl = wpa_ctrl_open (WPA_SUPPLICANT_GLOBAL_SOCKET,
NM_RUN_DIR)))
goto exit;
+ if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
"ndiswrapper")) {
+ driver= g_malloc(sizeof(char)*(strlen("ndiswrapper")+1));
+ driver= strcpy(driver, "ndiswrapper");
+ }
+ else {
+ driver= g_malloc(sizeof(char)*(strlen("wext")+1));
+ driver= strcpy(driver, "wext");
+ }
+
/* wpa_cli -g/var/run/wpa_supplicant-global interface_add
eth1 "" wext /var/run/wpa_supplicant */
if (!nm_utils_supplicant_request_with_check (ctrl, "OK",
__func__, NULL,
- "INTERFACE_ADD %s\t\twext\t"
WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface))
+ "INTERFACE_ADD %s\t\t%s\t" WPA_SUPPLICANT_CONTROL_SOCKET
"\t", iface, driver))
goto exit;
wpa_ctrl_close (ctrl);
@@ -2308,6 +2320,7 @@
success = TRUE;
exit:
+ g_free (driver);
return success;
}
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wep key lost
The problem is in ../src/nm-device-802-11-wireless.c at
function "static gboolean nm_device_802_11_wireless_scan
(gpointer user_data)". Probe to substitute with:
static gboolean
nm_device_802_11_wireless_scan (gpointer user_data)
{
return FALSE;
}
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
The problem is in ../src/nm-device-802-11-wireless.c at
function "static gboolean nm_device_802_11_wireless_scan
(gpointer user_data)". Probe to substitute with:
static gboolean
nm_device_802_11_wireless_scan (gpointer user_data)
{
return FALSE;
}
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
wep key lost
My problem is that I type correctly wep key but networkmanager
doesn't configure interface with the key:
--
wlan0 IEEE 802.11g ESSID:"Router" Nickname:"eclipse"
Mode:Managed Frequency:2.437 GHz Access Point:
00:0E:6A:C8:21:4E
Bit Rate=54 Mb/s Tx-Power:24 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:100/100 Signal level:-53 dBm Noise
level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
because it doesn't connect.
I 've changed code:
-
./src/nm-device-802-11-wireless.c
line 2291
if (!nm_utils_supplicant_request_with_check (ctrl, "OK",
__func__, NULL,
- "INTERFACE_ADD %s\t\tndiswrapper\t"
WPA_SUPPLICANT_CONTROL_SOCKET "\t", iface)) {
+ "INTERFACE_ADD %s\t\tndiswrapper\t"
WPA_SUPPLICANT_CONTROL_SOCKET "\t", iface)) {
Now networkmanager connect!! But in few seconds it lost key.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: vpn config
Hi Steev, yes I restarted them, I also tried to reboot my laptop but without success. Something may be missing on my system... I tried to unmerge & reemerge it after I applied Rémi's patch but it still doesn't work. Rgds -- Joris On Thu, 2005-11-17 at 13:14 -0600, Steev Klimaszewski wrote: > Joris, did you restart dbus/hal/NetworkManager? At the current time, > that is a requirement, and though you can add vpn connections to the > list, you will not see them until NetworkManager/nm-applet are > restarted. After that, adding and removing them show up just fine. > > -- Steev > -- Joris Vuffray <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 2 questions...
Nobody? Rgds, Joris > > 1.) Is there a possibility to make networkmanager connect from > commande-line? > > 2.) My nm-applet only show "Disconnect VPN..." in the "VPN Connections" > menu. Is there something special to configure to create a new VPN > connection? > > Regards, > Joris > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list -- (( [EMAIL PROTECTED] )) <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
