RE: How to deal with trojans?
-Original Message- From: networkmanager-list-boun...@gnome.org [mailto:networkmanager-list-boun...@gnome.org] On Behalf Of Daniel Gnoutcheff Sent: Thursday, May 20, 2010 4:10 AM To: networkmanager-list@gnome.org Subject: How to deal with trojans? While researching/brainstorming for my GSoC project, I've been thinking a lot about related security issues, specifically the issue of trojan programs messing with user settings data. It seems that, while this has long been a concern for N-M development, it hasn't been addressed directly yet. --- Daniel - As a long time UNIX/Linux developer and NM user, I can understand your concerns. Your interest in protecting the user from undesired changes is valid. However, I subscribe to the basic UNIX/Linux principle that tools should focus on doing small things, and doing them well. A tool should parse user-data for syntax, ie, an IP address is a dotted-quad, with each number between 0 and 255; but trying to parse data based on user intent creates a rift between what the user wants to do, and what "you" believe the user is trying to do. I think the detection of Trojans is best left to tools that focus on that task. If you extend your premise that NM should deal with detecting Trojan data to all tools, then we have a great duplication of effort with "all" tools trying (perhaps differently) to detect Trojan data. We should avoid bloating NM with functionality that is not directly network related. That's my two cents. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: blacklisting a usb device with network manager
Your virtual machine is only going to see the virtual network that vmware creates. The host system gets to access the hardware directly, all the guests only see the virtual network. -Original Message- From: networkmanager-list-boun...@gnome.org on behalf of FS Inc. Sent: Wed 4/29/2009 10:46 PM To: networkmanager-list@gnome.org Cc: Subject:blacklisting a usb device with network manager Hey all. I have two usb wireless devices that I have plugged into my computer. I am on ubuntu 9.04 so the rt73usb is the kernel module used to drive them. However I only want to use one of them in my host system. The other one I want to use exclusively in a VM machine. It is also driven by the rt73. The vm has intrepid 8.10 installed and uses the serial monkey rt73 driver. My question is is there anyway I can make networkmanager ignore the one I wish to use in the vmware. As of right now network is picking up both of them and I can see them when I click on the applet. I only want netowrkmanager to manage the one I use on the host while ignoring the other one. Thanks. _ More than messages–check out the rest of the Windows Live™. http://www.microsoft.com/windows/windowslive/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Fedora 10 issue?
Hi Dan, and others - I didn't really think it was an NM issue, but hoped someone on the list might have seen the same behavior. After more exhaustive testing, it looks like it's hardware related since the same behavior now occurs within Windows XP as well. Might be something in the BIOS, but I haven't seen anything yet. - Jon -Original Message- From: Dan Williams [mailto:d...@redhat.com] Sent: Thu 1/8/2009 1:12 PM To: Miner, Jonathan W (US SSA) Cc: networkmanager-list@gnome.org Subject:Re: Fedora 10 issue? On Tue, 2009-01-06 at 09:21 -0500, Miner, Jonathan W (US SSA) wrote: > Hi - > > I've noticed that since upgrading from Fedora 9 to Fedora 10, with: > > NetworkManager-glib-0.7.0-0.12.svn4326.fc10.i386 > NetworkManager-0.7.0-0.12.svn4326.fc10.i386 > NetworkManager-gnome-0.7.0-0.12.svn4326.fc10.i386 > > The wireless interface on my HP/Compaq 6910p is not active if I'm using the > docking station (and the lid is closed). Dmesg reports: > > iwlagn :10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > iwlagn :10:00.0: restoring config space at offset 0x1 (was 0x12, > writing 0x16) > firmware: requesting iwlwifi-4965-2.ucode > iwlagn: Radio disabled by HW RF Kill switch This would indicate that the driver itself things the rfkill switch has been flipped, and NM will disable the wifi in that case. Sounds more like a kernel bug... If you see that message, it's kernel-land. Dan > The wifi adapter is: > > 10:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN > Network Connection (rev 61) > > If I plug in an external USB adapter: > > Bus 001 Device 007: ID 0586:3413 ZyXEL Communications Corp. AG-225H v2 > 802.11a/g Wi-Fi Finder & Adapter > > and, via the NM applet disable and re-enable wireless, I can use the external > adapter. > > Is this the expected behaviour? > > - Jon > > ___ > 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
Fedora 10 issue?
Hi - I've noticed that since upgrading from Fedora 9 to Fedora 10, with: NetworkManager-glib-0.7.0-0.12.svn4326.fc10.i386 NetworkManager-0.7.0-0.12.svn4326.fc10.i386 NetworkManager-gnome-0.7.0-0.12.svn4326.fc10.i386 The wireless interface on my HP/Compaq 6910p is not active if I'm using the docking station (and the lid is closed). Dmesg reports: iwlagn :10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwlagn :10:00.0: restoring config space at offset 0x1 (was 0x12, writing 0x16) firmware: requesting iwlwifi-4965-2.ucode iwlagn: Radio disabled by HW RF Kill switch The wifi adapter is: 10:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) If I plug in an external USB adapter: Bus 001 Device 007: ID 0586:3413 ZyXEL Communications Corp. AG-225H v2 802.11a/g Wi-Fi Finder & Adapter and, via the NM applet disable and re-enable wireless, I can use the external adapter. Is this the expected behaviour? - Jon ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: problems with intel wireless cards
> I, too, run that Intel Wireless adapter on my Lenovo T61p and I, too, > have terrible problems with the device. Hi - Me too... it's most frustrating when trying to connect to a known open network and having to click several times before it connects. To the best of my knowledge, it appears to associate with the AP, but the DHCP requests never get to the wired network. 10:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) I also have a ZyXEL USB-adaptor, (AG-225H) and have not had any problems using it. It also tends to show higher signal strengths then the internal card. - Jon ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: blank lines added to /etc/hosts [PATCH]
I think this will fix my issue... only append the newline if we're not parsing
the last line of the file.
--- src/NetworkManagerPolicy.c.orig 2008-11-03 09:33:08.0 -0500
+++ src/NetworkManagerPolicy.c 2008-11-04 17:02:39.0 -0500
@@ -306,7 +306,8 @@
if (add_line) {
g_string_append (new_contents, *line);
- g_string_append_c (new_contents, '\n');
+if (*(line+1)) /* if not the last line */
+ g_string_append_c (new_contents, '\n');
}
}
-Original Message-
From: [EMAIL PROTECTED] on behalf of Miner, Jonathan W (US SSA)
Sent: Tue 11/4/2008 4:54 PM
To: NetworkManager-list@gnome.org
Cc:
Subject:blank lines added to /etc/hosts
Hi -
Each time I unplug, or reconnect my network cable, a blank line gets added to
the end of /etc/hosts.
# wc -l /etc/hosts
4 /etc/hosts
(unplug my cable...)
# wc -l /etc/hosts
5 /etc/hosts
(plug cable back in...)
# wc -l /etc/hosts
6 /etc/hosts
Guessing that it is the g_string_append_c() call on line 309 of
src/NetworkManagerPolicy.c which could needlessly add '\n' characters?
___
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
blank lines added to /etc/hosts
Hi - Each time I unplug, or reconnect my network cable, a blank line gets added to the end of /etc/hosts. # wc -l /etc/hosts 4 /etc/hosts (unplug my cable...) # wc -l /etc/hosts 5 /etc/hosts (plug cable back in...) # wc -l /etc/hosts 6 /etc/hosts Guessing that it is the g_string_append_c() call on line 309 of src/NetworkManagerPolicy.c which could needlessly add '\n' characters? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: location of DHCP lease files
I understand the need for multiple lease files, based on network.
My concern was the two different directories being used. I was trying to solve
a network problem, and couldn't understand why my lease files were several
months old... Then I discovered that NM was putting lease files somewhere else.
Persistence across boots would require some cooperation with the DHCP server,
which, in my case, may give me a new IP each time I boot. (It's some 3rd party,
Windows based DHCP/DNS "solution", which I don't manage)
- Jon
-Original Message-
From: Dan Williams [mailto:[EMAIL PROTECTED]
Sent: Tue 11/4/2008 1:41 PM
To: Miner, Jonathan W (US SSA)
Cc: networkmanager-list@gnome.org
Subject:Re: location of DHCP lease files
On Tue, 2008-11-04 at 11:47 -0500, Miner, Jonathan W (US SSA) wrote:
> Hi -
>
> I've noticed that the native Fedora "ifup-eth" script puts its lease files
> into
>
> /var/lib/dhclient/dhclient-${DEVICE}.leases
>
> but, NetworkManager puts the lease files into
>
> /var/run/dhclient-${DEVICE}.lease
Correct. NM uses different lease files because in the near future,
we'll want to use separate lease files for _each connection_. Since
many machines move around, it's pretty pointless to use the same lease
file for your home AP as for your work AP.
What happens right now is that you'll get a lease from work, dhclient
will cache it, and then when you come home it'll try to renew that work
lease at home, leading to DHCP lag. That's bad.
So even if the lease files _did_ stay in the same place as dhclient puts
them, you'd have a lot more lease files anyway. But, once we modify NM
to handle leasefile-per-connection, we should probably move them back
to /var/lib/dhclient just to they are persistent.
I assume you're worried about persistence of the lease across boots?
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
location of DHCP lease files
Hi -
I've noticed that the native Fedora "ifup-eth" script puts its lease files into
/var/lib/dhclient/dhclient-${DEVICE}.leases
but, NetworkManager puts the lease files into
/var/run/dhclient-${DEVICE}.lease
It looks like this is coming from nm-dhcp-manager.h, which builds
NM_DHCP_MANAGER_RUN_DIR from LOCALSTATEDIR and the constant "/run". The
localstatedir is set to /var in the top level Makefile.
Is this inconsistency related to running an SVN version (r4254), when compared
to an official Fedora yum update?
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Network-Manager applet r955 fails to compile
I'm also seeing compilation errors this morning... OS: Fedora 9 / 2.6.26.5-45.fc9.i686 NetworkManager: 4196 network-manager-applet: 955 nma-gconf-connection.c: In function 'nma_gconf_connection_class_init': nma-gconf-connection.c:472: error: 'NMExportedConnectionClass' has no member named 'get_secrets' -Original Message- From: [EMAIL PROTECTED] on behalf of Dan Williams Sent: Mon 10/20/2008 1:07 PM To: Pramod Dematagoda Cc: NetworkManager ML Subject:Re: Network-Manager applet r953 fails to compile. On Sat, 2008-10-18 at 19:13 +0530, Pramod Dematagoda wrote: > I've just pulled r953 of network-manager-applet, however when I try to > compile it I get the following errors from make:- > > gconf-helpers.c: In function 'write_one_secret_to_keyring': > gconf-helpers.c:1254: error: 'NM_SETTING_VPN_SECRETS' undeclared (first > use in this function) > gconf-helpers.c:1254: error: (Each undeclared identifier is reported > only once > gconf-helpers.c:1254: error: for each function it appears in.) > make[3]: *** [libgconf_helpers_la-gconf-helpers.lo] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > > Is this something wrong with nm-applet itself or is there something I'm > doing wrong here? This is on a Fedora 9 PC. What version of NetworkManager are you using? You'll generally have to build latest NetworkManager along with the applet. I bet you've got svn4022.4 installed and you're trying to build trunk applet, which isn't going to work... 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: bug in resolv.conf rewrite
Thanks.. I hadn't svn updated in the last several days. -Original Message- From: Tambet Ingo [mailto:[EMAIL PROTECTED] Sent: Fri 8/15/2008 10:17 AM To: Miner, Jonathan W (US SSA) Cc: NetworkManager-list@gnome.org Subject:Re: bug in resolv.conf rewrite On Fri, Aug 15, 2008 at 4:55 PM, Miner, Jonathan W (US SSA) <[EMAIL PROTECTED]> wrote: > I may have found a bug in the resolv.conf rewriting code. Here is the > scenario that caused this: > > 1) Booted up with wireless network, ISP #1. I didn't verify, but the file > should have contained: > > nameserver A.B.C.35 > nameserver A.B.C.36 > > 2) Connected to physical ethernet, ISP #2. The contents of /etc/resolv.conf > now has, with names obscured in CAPS > > <> > # generated by NetworkManager, do not edit! > > DOMAIN.NAME.COMPANY.COM.search DOMAIN.NAME.COMPANY.COM. > > nameserver X.Y.26.118 > nameserver X.Y.12.27 > nameserver A.B.C.35 > > # NOTE: the glibc resolver does not support more than 3 nameservers. > # The nameservers listed below may not be recognized. > nameserver A.B.C.36 > <> > > > The "search" line is broken. Yes, I accidentally made a typo with that commit, but Dan fixed it on August 12th, r3943. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
bug in resolv.conf rewrite
I may have found a bug in the resolv.conf rewriting code. Here is the scenario that caused this: 1) Booted up with wireless network, ISP #1. I didn't verify, but the file should have contained: nameserver A.B.C.35 nameserver A.B.C.36 2) Connected to physical ethernet, ISP #2. The contents of /etc/resolv.conf now has, with names obscured in CAPS <> # generated by NetworkManager, do not edit! DOMAIN.NAME.COMPANY.COM.search DOMAIN.NAME.COMPANY.COM. nameserver X.Y.26.118 nameserver X.Y.12.27 nameserver A.B.C.35 # NOTE: the glibc resolver does not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver A.B.C.36 <> The "search" line is broken. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Cannot connect with iwl4965
> I have problems connecting with iwl4965 to secure networks, I just keep > getting: > [..snip..] > I have been trying to find some info on this but have not managed to > find anything conclusive, can anyone shed some light on this problem? Magnus - I had similar problems when the previous (*.9-76 ?) Fedora 9 kernel came out, but the issue appeared to be fixed when 2.6.25.10-86.fc9 was released. However, this weekend, my laptop started to fail to connect to my open network at home. It appeared that the laptop was associated with the AP, since tcpdump could see broadcasts from the router... but could not see outgoing DHCP requests. Rebooting with the 2.6.25.6-55.fc9 kernel fixed it. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Trying to start the system settings daemon... why?
>> ** Message:ifcfg-fedora: parsing >> /etc/sysconfig/network-scripts/ifcfg-eth0 ... >> ** Message:ifcfg-fedora: error: Invalid IP4 prefix '0' > > What's the NETMASK or PREFIX field in that ifcfg file? This could well > be a bug. Neither one is set... should be coming from the dhcp server. # Intel Corporation 82566MM Gigabit Network Connection DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:1b:38:c4:db:8e ONBOOT=no DHCP_HOSTNAME=aa948228 TYPE=Ethernet USERCTL=no PEERDNS=yes IPV6INIT=no NM_CONTROLLED=yes DNS2=129.86.12.27 SEARCH=usa02.na.baesystems.com. DNS1=129.86.26.118 >> ** Message:ifcfg-fedora: parsing >> /etc/sysconfig/network-scripts/ifcfg-wlan0 ... >> ** Message:ifcfg-fedora: error: Missing SSID > > Missing ESSID in the ifcfg, so NM has no idea what net to connect to > there. I guess I'm not sure why the ESSID should be set in that file... should NM get that from somewhere else? Maybe the file just needs to be cleaned up? # Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection DEVICE=wlan0 BOOTPROTO=dhcp ONBOOT=no HWADDR=00:1d:e0:5f:c2:93 NETMASK= DHCP_HOSTNAME=aa948228 IPADDR= DOMAIN= TYPE=Wireless ESSID= CHANNEL=11 MODE=Auto RATE=auto USERCTL=no PEERDNS=yes IPV6INIT=no NM_CONTROLLED=yes SEARCH=usa02.na.baesystems.com. DNS2=129.86.12.27 DNS3= DNS1=129.86.26.118 > Any SELinux errors that you can see with setroubleshoot? SELinux is not enabled on this machine! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Trying to start the system settings daemon... why?
> It means that the system settings service couldn't be started. We should figure out _why_ it can't be started, actually. Could be due to selinux policy denials perhaps. Can you stop NetworkManager and run: > /usr/sbin/nm-system-settings --debug --plugins=ifcfg-fedora On this particular system, selinux is disabled. Here is my output... but I had to ^C it, since the command ended up hanging. ** Message: Loaded plugin ifcfg-fedora: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. ** Message:ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... ** Message:ifcfg-fedora: error: Invalid IP4 prefix '0' ** Message:ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... ** Message:ifcfg-fedora: error: Ignoring loopback device config. ** Message:ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ... ** Message:ifcfg-fedora: error: Missing SSID ** Message: Adding default connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_1b_38_c4_db_8e ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Trying to start the system settings daemon... why?
I happily using NM 0.7.0 (Fedora 9 and r3830)... but my system log repeatedly
reports:
Jul 18 08:12:38 localhost NetworkManager: Trying to start the system
settings daemon...
every two minutes. This message comes from src/nm-manager.c, but I'm not sure
what the message is trying to tell me. There is a conditional statement right
above it that would report if a dbus proxy fails. I'm tempted to remove this
message since it doesn't seem to report anything of value, and just adds to the
system message log. Please correct me if I'm mistaken.
--- nm-manager.c.r3830 2008-07-14 09:25:00.0 -0400
+++ nm-manager.c2008-07-18 08:21:44.0 -0400
@@ -1280,7 +1280,7 @@
goto out;
}
- nm_info ("Trying to start the system settings daemon...");
+ // nm_info ("Trying to start the system settings daemon...");
dbus_g_proxy_call_no_reply (proxy, "ListConnections", G_TYPE_INVALID);
g_object_unref (proxy);
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Networkmanager Crash after update
Dan - I don't know if my problem is related, but this morning after updating to the 2.6.25.9-76.fc9.i686 kernel, I can no longer connect to my WPA2-Enterprise network. The system works when booted to the older (2.6.25.6-55.fc9.i686) kernel. NetworkManager: r3799 network-manager-applet: r774 lspci: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) Thanks -Original Message- From: [EMAIL PROTECTED] on behalf of Dan Williams Sent: Mon 6/30/2008 11:31 PM To: [EMAIL PROTECTED] Cc: networkmanager-list@gnome.org Subject:Re: Networkmanager Crash after update [..snip..] It's the kernel's fault; a kernel update that got pushed to fix a critical security issue crashes when connecting to WEP networks and using mac80211-based drivers (of which b43 is one). Grab the packages from this update: https://admin.fedoraproject.org/updates/F9/FEDORA-2008-5893 downloadable here for all architectures: http://koji.fedoraproject.org/koji/buildinfo?buildID=54043 I ran into this last Friday as well. An updated kernel should be out fairly soon. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
security selection via nm-applet
When I try to create a new wireless network connection using the nm-applet dialog, I get two different "Wireless Security" drop-down lists, depending on whether I use "Create New Wireless Network..." (4 options) or "Connect to Other Wireless Network...", then select "New..." at the "Connection" prompt (8 options). This looks like it comes from the security_combo_init() function in wireless-dialog.c, but I'm not sure why the options would be different... or even why there would be two different paths to create a new network. Would users be too confused if the menu simply said "Connect to Wireless Network..." ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
output from nm-tool
When I run "nm-tool", I get duplicate output for "Default". For example: - Device: eth0 - Type: Wired Driver:e1000e State: connected Default: yes Default: no - Device: wlan0 - Type: 802.11 Wireless Driver:iwl4965 State: connected Default: no Default: no It looks like the loop (r3758, nm-tool.c, line 230) might be iterating one too many times? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
"Unknown" security?
When I look at the "Connection Information" under the applet, my hardwired ethernet connection is listed as having "unknown" security. If I connect to an open wireless network, its security is shown as "none". Can someone explain the difference between "none" and "unknown"? Isn't it true that you could apply MAC filtering in either case, and NetworkManager wouldn't know that filtering was being applied? Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
dbus-glibc dependancy (Fedora 9)
Hi - Recent updates to NetworkManager have changed the dbus-glib dependency to 0.75, while the version provided by Fedora 9 is still 0.74. r3751 is the latest version that still builds on Fedora 9. If I update my configure script to check for the 0.74 version, it builds without errors, and seems to work. What features might be broken if I'm using the older version of dbus-glib? Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: connecting to a non-broadcasted SSID
Responses at the bottom... apologies for using MS-Outlook... -Original Message- From: Dan Williams [mailto:[EMAIL PROTECTED] Sent: Thu 6/12/2008 11:15 AM To: Miner, Jonathan W (US SSA) Cc: networkmanager-list@gnome.org Subject:Re: connecting to a non-broadcasted SSID On Thu, 2008-06-12 at 08:34 -0400, Miner, Jonathan W (US SSA) wrote: > I've noticed that when I successfully connect to a wireless network with a > non-broadcasted SSID that the applet reports: > > "You are now connected to the wireless network '(none)'." > > This message comes from network-manager-applet/src/applet-device-wifi.c, line > 1131 > > Clearly, NetworkManager knows the SSID of the network, since it was able to > look for it, and successfully connect to it. But it appears that the applet > can't determine it? Depends; the applet _should_ have the right idea of the current AP, but if you run 'nm-tool' is there a * next to your SSID while connected? If not, then the problem lies in NetworkManager. I did test hidden SSID last week and it worked OK for me, but enough people have reported this problem that I think there is a bug. Also, can you report what '/sbin/iwconfig wlan0' (or whatever your wifi interface name is) says when you're definitely connected? NM grabs that information periodically and tries to match it up with an AP that it's scanned, and if I cannot find the AP that the card says it's associated too (because it hasn't shown up in scan yet) then you'll end up with NULL. So, if you have more than one AP in the same SSID, but none of them are broadcasting their SSIDs, NM can only auto-match the SSID AP's its seen before. So if the card roams to a new AP that NM hasn't seen before, and also isn't broadcasting it's SSID, that AP won't necessarily be in the scan list yet, and even if it was, we wouldn't know it's SSID necessarily. The solution? _Don't_ hide your AP's SSID. It's security through obscurity, and if you're using good encryption like WPA[2] + 802.1x, it's completely unnecessary anyway. Anyone with WireShark can fire up a frame sniffer and grab your SSID at any time anyway. Dan >>>> My responses: Right now, I only have one AP, but we'll grow to two or three when this gets rolled out. I agree with you on the SSID hiding issue, but that is a political issue. nm-tool does has an asterisk: Wireless Access Points(* = Current AP) *FooBar:Infra, 00:12:17:70:0C:D0, Freq 2437 MHz, Rate 0 Mb/s, Strength 96 WPA Enterprise iwconfig output: wlan0 IEEE 802.11 ESSID:"FooBar" Mode:Managed Frequency:2.437 GHz Access Point: 00:12:17:70:0C:D0 Bit Rate=54 Mb/s Tx-Power=14 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:9A2C-BE5F-2F1C-1595-D71B-8761-0B04-B11E-B396-1F94-B70C-7BB8-2C8A-D5D3-18B8-5073 [2] Link Quality=100/100 Signal level:-42 dBm Noise level=-94 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
connecting to a non-broadcasted SSID
I've noticed that when I successfully connect to a wireless network with a non-broadcasted SSID that the applet reports: "You are now connected to the wireless network '(none)'." This message comes from network-manager-applet/src/applet-device-wifi.c, line 1131 Clearly, NetworkManager knows the SSID of the network, since it was able to look for it, and successfully connect to it. But it appears that the applet can't determine it? OS: Fedora 9 network-manager-applet: r755 NetworkManager: r3750 Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
patch to applet-dialogs
If the default gateway is not explicitly set, then it currently is displayed as
"0.0.0.0" in the "Connection Information" box. This patch disables the display
of the "Default Route" tag if it isn't set.
--- src/applet-dialogs.c.orig 2008-06-02 08:28:05.0 -0400
+++ src/applet-dialogs.c2008-06-03 11:47:59.0 -0400
@@ -367,13 +367,15 @@
row++;
/* Gateway */
- gtk_table_attach_defaults (table,
+ if ( def_addr->gateway != 0 ) {
+ gtk_table_attach_defaults (table,
create_info_label
(_("Default Route:")),
0, 1, row, row + 1);
- gtk_table_attach_defaults (table,
+ gtk_table_attach_defaults (table,
create_info_label
(ip4_address_as_string (def_addr->gateway)),
1, 2, row, row + 1);
- row++;
+ row++;
+ }
/* DNS */
dns = nm_ip4_config_get_nameservers (ip4_config);
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
corrected typo in nm-applet
I noticed that the "IP Address" label was misspelled in the "Connection
Information" dialog. Here are `diff -u` output for patches to the three files
that need to be corrected. If there is a better way to submit patches, please
let me know.
--- ./src/applet-dialogs.c.orig 2008-06-02 08:28:05.0 -0400
+++ ./src/applet-dialogs.c 2008-06-03 11:26:29.0 -0400
@@ -337,7 +337,7 @@
/* Address */
gtk_table_attach_defaults (table,
- create_info_label
(_("IP Adrress:")),
+ create_info_label
(_("IP Address:")),
0, 1, row, row + 1);
gtk_table_attach_defaults (table,
create_info_label
(ip4_address_as_string (def_addr->address)),
--- ./po/ru.po.orig 2008-06-02 08:28:05.0 -0400
+++ ./po/ru.po 2008-06-03 11:26:20.0 -0400
@@ -308,7 +308,7 @@
msgstr "??:"
#: ../src/applet-dialogs.c:340
-msgid "IP Adrress:"
+msgid "IP Address:"
msgstr "IP-?:"
#: ../src/applet-dialogs.c:353
--- ./po/es.po.orig 2008-06-02 08:28:05.0 -0400
+++ ./po/es.po 2008-06-03 11:26:08.0 -0400
@@ -312,7 +312,7 @@
msgstr "Seguridad:"
#: ../src/applet-dialogs.c:340
-msgid "IP Adrress:"
+msgid "IP Address:"
msgstr "Dirección IP:"
#: ../src/applet-dialogs.c:353
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
