Re: So very close, but so frustrating...
On Fri, 2009-10-02 at 18:44 -0700, Dan Williams wrote: On Fri, 2009-10-02 at 00:19 +0100, Bastien Nocera wrote: On Thu, 2009-10-01 at 14:39 -0700, Dan Williams wrote: On Wed, 2009-09-30 at 20:18 -0400, Darren Albers wrote: snip At this time Network Manager does not support Bluetooth modems. I think 0.8 supports phones if they use Bluetooth PAN but not Bluetooth DUN. Correct; I may just get bored enough today triaging bugs to go implement DUN in 0.8. That opens up a huge number of cellphones, which will inevitably lead to even more bugs since there's much more phone variation than in the relatively small data card space. Oh well; it would help a lot of people out. 1. Add ability for MM to identify Bluetooth modems I believe that would mostly work automatically after NM tells bluez to create the port and connect, right? Basically, after the BT parts come up and the serial port is active, MM should get the add even from udev and probe the port like any other port. What I'm not clear about is when the serial port actually shows up in sysfs and when udev sends the event; does that only happen when the BT connection between computer and phone is up and the port can actually be used? Or does the port appear immediately before the phone/host have connected to each other? To answer some of these questions... the port shows up when connection is possible. I fixed a few bugs causing MM to fail to detect the rfcomm ports: e5441115a2dda5d81de2e9a336fc34e23d20b309 ed059286c5361bf4dfa849088ee16c04cd075e51 aa78b5f5e5319e04f5b57f928bfab69dd4b93d88 Next, we need to see if the probing actually works on these phones, and figure out the bugs. We'll get assloads of bugs about this I'm sure, but we just have to suck that up and quirk all the stupid phones out there. 2. Add plugin in bluez to poke at the modem with MM if it doesn't know the type of device, cache the result, the bluez plugin exports the information through a service Why not just do this from the gnome-bluetooth plugin? The plugin would probably just ask bluez to connect to the phone via DUN, let MM discover the port via the normal mechanisms, and then query MM for the modem type, then create the right connection in GConf. That should be pretty straightforward when (1) is done. I dont' really see why we'd need something bluez itself to do this. See the 'btdun' branch of nm-applet, where I've added DUN support to the gnome-bluetooth plugin. There's nothing in the applet or NM side yet, both will need further fixes. But the gnome-bt plugin seems to work OK at the moment. Bastien, can you sanity check it? There's a lot of async dbus calls going on there between the plugin, Bluez, and MM. Needs another set of eyes. 8b0ae181efd1e3856851e6a44e16bd51d440d0ce c1c13b9dff6772bf13ab6217a2eecb986bd67687 3. Add DUN gnome-bluetooth plugin to nm-applet which would poke the bluez service See above. 4. Add native support in NM to do the connection through bluetoothd That's mostly already there; we wrote it but didn't connect it up to ModemManager. This gets a bit interesting, because now we have the NMBTDevice object, but by default we'll also get a Modem subclass when ModemManager announces it ahs the device. We need to intercept that in NM and just attach the modem to the NMBtDevice. Haven't looked into this yet; getting all the corner cases right in the gnome-bluetooth plugin was hard enough for one night. Dan After 3., if the box is ticked, the device should appear like an unconfigured WWAN modem to the user. The service configuration can then be done through nm-applet. I thought we were going to be doing the service configuration through the gnome-bluetooth plugin? Basically, when you tick the box for use my phone for dial-up networking in the plugin, it would throw up a spinner and say Detecting phone type..., tell bluez to fire up the rfcomm port, let MM find the rfcomm port, then ask MM for the type, and then launch the mobile broadband config wizard to get the rest of the settings. When that's done, it stores the config in GConf just like the PAN stuff. No? I can certainly take care of 2. and 3. if you do 1. and the left-overs of 4 :) Yeah, I'm the best for 1 4. I'll try to take a look tonight. 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: Weird wireless phantom device
--On Friday, October 02, 2009 18:25:59 -0700 Dan Williams d...@redhat.com wrote: On Fri, 2009-10-02 at 22:54 +0100, Rick Jones wrote: I think your call on VBox was the right one. So now having installed 2.2 again, there's no problems with the WiFi device. Bizarre bug, I'd never have made that connection. It showed up because people got duplicate connections like this. VirtualBox seems to screw around with /sys in a broken attempt to virtualize it or something, which causes erroneous udev signals, which cause HAL to get the wrong information and duplicate the device. What's in your /sys/class/net/ directory? As follows: eth0 - ../../devices/pci:00/:00:1c.1/:04:00.0/net/eth0 lo - ../../devices/virtual/net/lo pan0 - ../../devices/virtual/net/pan0 ra0 - ../../devices/pci:00/:00:1c.3/:01:00.0/net/ra0 vboxnet0 - ../../devices/virtual/net/vboxnet0 This is with VBox 2.2, I don't know what was there with 3.0. I've been running VBox 2 since I got this m/c nearly a year ago, and had no problems. It must have appeared with the update to 3 (or maybe a subsequent point-version update), I just didn't make the connection. Cheers, Rick --On Thursday, October 01, 2009 14:13:14 -0700 Dan Williams d...@redhat.com wrote: On Thu, 2009-10-01 at 16:31 +0100, Rick Jones wrote: I'm getting a repeated problem of my WiFi device showing up twice in NM. This isn't really an NM problem, but I'm hoping someone here will have an idea how to fix it. NM 0.8? Or NM 0.7? For 0.7, run 'lshal' and look for device blocks with 'wlan0' in them. If you see two, then it's a hal problem (though we've seen cases where VirtualBox in it's misguided attempts to virtualize /sys completely screws over HAL). For 0.8, what do you have in /sys/class/net/ ? Dan The device appears twice in DBus, which is obviously the source of the problem, as NM is just listing what it finds. Both entries in DBus are identical, and point to the same device (which messes up NM as it tries to open and connect on the same device twice). The DBus node names are almost identical, the second entry just has an extra _0 at the end. The output of lspci shows only one device: 01:00.0 Network controller: RaLink RT2860 Subsystem: RaLink Device 2790 Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at f800 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/5 Enable- Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting ? Kernel driver in use: rt2860 Kernel modules: rt2860sta Running lsmod | grep 2860 shows only one user: rt2860sta 513240 1 Whether one or two devices show up is set from boot, and it seems random when I re-boot what I'm going to get. Anyone got any ideas? TIA Rick ___ 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: OLPC mesh support backported to NM-0.7
2009/9/18 Daniel Drake d...@laptop.org: Hi Dan, I'm sending you 6 patches which backport the NM mesh support to the v0.7 branch. They are all direct backports from the patches you committed to master, with only the minimal changes needed to get things working on 0.7. I've tested it with my modified Sugar and it is working well. ping.. any thoughts on these patches? Thanks! Daniel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Use libnl and nl80211 to get bitrate information
I've revised the patch to use system's nl80211.h with ifdefs. If nl80211
is too old the code will not be compiled and wext will be used
On Thu, 2009-09-24 at 18:48 +0300, Valmantas Palikša wrote:
This patch allows us to see 11n bitrates in nm-applet's connection
properties.
Comments/suggestions?
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
diff --git a/src/nm-device-wifi.c b/src/nm-device-wifi.c
index f2c9350..b192325 100644
--- a/src/nm-device-wifi.c
+++ b/src/nm-device-wifi.c
@@ -30,6 +30,13 @@
#include sys/wait.h
#include signal.h
#include unistd.h
+#include netlink/netlink.h
+#include netlink/genl/genl.h
+#include netlink/genl/family.h
+#include netlink/genl/ctrl.h
+#include netlink/socket.h
+#include linux/nl80211.h
+
#include nm-glib-compat.h
#include nm-device.h
@@ -53,6 +60,7 @@
#include nm-setting-ip6-config.h
#include NetworkManagerSystem.h
+
static gboolean impl_device_get_access_points (NMDeviceWifi *device,
GPtrArray **aps,
GError **err);
@@ -1561,8 +1569,59 @@ out:
close (sk);
return priv-ssid;
}
+/* this symbol should be defined in recent nl80211.h */
+#ifdef NL80211_ATTR_REASON_CODE
+#define LIBNL_BITRATES
+#endif
+
+#ifdef LIBNL_BITRATES
+static int bitrate_cb(struct nl_msg *msg, void *arg)
+{
+ int *rate = (int*)arg;
+
+ struct nlattr *tb[NL80211_ATTR_MAX + 1];
+ struct genlmsghdr *gnlh = nlmsg_data(nlmsg_hdr(msg));
+ struct nlattr *sinfo[NL80211_STA_INFO_MAX + 1];
+ struct nlattr *rinfo[NL80211_RATE_INFO_MAX + 1];
+ static struct nla_policy stats_policy[NL80211_STA_INFO_MAX + 1] = {
+ [NL80211_STA_INFO_TX_BITRATE] = { .type = NLA_NESTED },
+ };
+ static struct nla_policy rate_policy[NL80211_RATE_INFO_MAX + 1] = {
+ [NL80211_RATE_INFO_BITRATE] = { .type = NLA_U16 },
+ [NL80211_RATE_INFO_MCS] = { .type = NLA_U8 },
+ [NL80211_RATE_INFO_40_MHZ_WIDTH] = { .type = NLA_FLAG },
+ [NL80211_RATE_INFO_SHORT_GI] = { .type = NLA_FLAG },
+ };
+
+ nla_parse(tb, NL80211_ATTR_MAX, genlmsg_attrdata(gnlh, 0),
+ genlmsg_attrlen(gnlh, 0), NULL);
+
+ if (!tb[NL80211_ATTR_STA_INFO]) {
+ *rate = 0;
+ return NL_STOP;
+ }
+ if (nla_parse_nested(sinfo, NL80211_STA_INFO_MAX,
+ tb[NL80211_ATTR_STA_INFO],
+ stats_policy)) {
+ *rate = 0;
+ return NL_STOP;
+ }
+
+ if (sinfo[NL80211_STA_INFO_TX_BITRATE]) {
+ if (nla_parse_nested(rinfo, NL80211_RATE_INFO_MAX,
+ sinfo[NL80211_STA_INFO_TX_BITRATE], rate_policy)) {
+ *rate = 0;
+ } else {
+ if (rinfo[NL80211_RATE_INFO_BITRATE]) {
+*rate = nla_get_u16(rinfo[NL80211_RATE_INFO_BITRATE]) * 100;
+ }
+ }
+ }
+ return NL_STOP;
+}
+#endif
/*
* nm_device_wifi_get_bitrate
*
@@ -1573,21 +1632,62 @@ out:
static guint32
nm_device_wifi_get_bitrate (NMDeviceWifi *self)
{
+ NMDeviceWifiPrivate *priv = NM_DEVICE_WIFI_GET_PRIVATE (self);
+ int rate = 0;
+
+#ifdef LIBNL_BITRATES
+ struct nl_handle *sock;
+ struct nl_msg *msg;
+ int family;
+
int err = -1, fd;
struct iwreq wrq;
+#endif
+
g_return_val_if_fail (self != NULL, 0);
- fd = socket (PF_INET, SOCK_DGRAM, 0);
- if (fd 0)
- return 0;
+#ifdef LIBNL_BITRATES
+
+ sock = nl_handle_alloc();
+ msg = nlmsg_alloc();
+
+ genl_connect(sock);
- memset (wrq, 0, sizeof (wrq));
- strncpy (wrq.ifr_name, nm_device_get_iface (NM_DEVICE (self)), IFNAMSIZ);
- err = ioctl (fd, SIOCGIWRATE, wrq);
- close (fd);
+ family = genl_ctrl_resolve(sock, nl80211);
+
+ genlmsg_put(msg, 0, 0, family, 0, NLM_F_DUMP, NL80211_CMD_GET_STATION, 0);
+ nla_put_u32(msg, NL80211_ATTR_IFINDEX, priv-ifindex);
+
+ if(nl_send_auto_complete(sock, msg) 0)
+ goto cleanup;
- return ((err == 0) ? wrq.u.bitrate.value / 1000 : 0);
+ nl_socket_modify_cb(sock, NL_CB_VALID, NL_CB_CUSTOM, bitrate_cb, rate);
+
+ nl_recvmsgs_default(sock);
+
+
+cleanup:
+ nlmsg_free(msg);
+ nl_handle_destroy(sock);
+
+#endif
+
+ /* nl80211 failed to return a valid bitrate, let's try wext */
+ if(rate == 0) {
+
+ fd = socket (PF_INET, SOCK_DGRAM, 0);
+ if (fd 0)
+ return 0;
+
+ memset (wrq, 0, sizeof (wrq));
+ strncpy (wrq.ifr_name, nm_device_get_iface (NM_DEVICE (self)), IFNAMSIZ);
+ err = ioctl (fd, SIOCGIWRATE, wrq);
+ close (fd);
+
+ return ((err == 0) ? wrq.u.bitrate.value / 1000 : 0);
+ }
+ return rate;
}
/*
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Wireless problems on Acer Aspire One using Ubuntu Karmic
Hi, I've reported a bug on Ubuntu's launchpad but as time is pressing toward the release, I thought I'd bring it up here. https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/433720 When I connect to my wireless access point here (since upgrading to Karmic), the network manager shows a successful connection and then after a couple of seconds, I get disconnected. This makes wifi moreorless impossible to use. It's not clear to me if this is a NM problem or something else. Could someone give me an indication of this? dmesg gives me the following information: [ 122.156114] wlan0: associated [ 124.204212] wlan0: disassociating by local choice (reason=3) [ 135.655652] wlan0: authenticate with AP 00:11:f5:b9:b3:96 [ 135.660813] wlan0: authenticated [ 135.660824] wlan0: associate with AP 00:11:f5:b9:b3:96 [ 135.663000] wlan0: RX AssocResp from 00:11:f5:b9:b3:96 (capab=0x431 status=0 aid=2) [ 135.663012] wlan0: associated [ 147.535173] wlan0: disassociating by local choice (reason=3) [ 265.564837] wlan0: authenticate with AP 00:11:f5:b9:b3:96 [ 265.571219] wlan0: authenticated [ 265.571231] wlan0: associate with AP 00:11:f5:b9:b3:96 [ 265.573446] wlan0: RX AssocResp from 00:11:f5:b9:b3:96 (capab=0x431 status=0 aid=1) [ 265.573458] wlan0: associated [ 277.537460] wlan0: disassociating by local choice (reason=3) Is there other information I should provide? Gavin ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: So very close, but so frustrating...
Dan Williams wrote: Which is why the people doing Blueman might as well have helped out getting the native NM support up and running in the first place; the answer at the time was help get modem-manager working so we can do this properly, but the Blueman people took the short, hack-for-today route. While I dont' like that decision, it does make some people's modems work (but definitely not everyones), and it's not the optimal interface for making your hardware work for you. The objective is and always has been to make this all just work and integrate well in NetworkManager, instead of having yet more tools added to the mix. Ah, ha - some politics. :) At the moment, I fall into the camp that's glad to have a (partial) solution now - even if it's badly engineered and with lots of caveats. I do understand where you're coming from. The NM OpenVPN plugin doesn't implement export yet. After getting import to work, I moved on to other also-quite-important stuff. openvpn export would be a great piece of low-hanging fruit that somebody could easily develop a patch for, actually. Any takers? Nice attempt at coercion... Erm - I'm not refusing, but don't hold your breath. I've lots of other stuff on my own to-do list that is more urgent for me. I mentioned it mainly out of surprise... I like the idea of a save/restore configuration - but think it would be most effective if it covered all configuration - including VPNs, DSLs and WiFi. Having found the effort had been taken to provide the UI for the fine-grained approach, I didn't expect the functionality to be missing. :) Solid support for mobility is definitely a goal we're always improving on. Every project needs more help, and NetworkManager is no different. For my own sob-story, today I spent time fixing a few bugs with certificate handling, fixing the connection editor retrieving your secrets/passwords when you edit connections, and reviewing some patches. I'd hoped to get back to improving the 3G/mobile broadband support earlier this week, but a bunch of UI stuff had to be done instead. If I could clone myself and a some of the others who contribute a lot to the project, we'd (a) have a more awesome NetworkManager, and (b) get rich of the patents we'd file for cloning technology. Oh well. That sounds like good progress to me - even without cloning technology. ;) One idea that has occurred - on a more general basis than my specific user-oriented problem - relates to how NetworkManager establishes connectivity when multiple connections are viable. Choosing the 'fastest' might not always be appropriate... I'm thinking about these scenarios: 1. Currently I'm in-range of two Wi-Fi routers to which I can authenticate - each with an independent broadband connection... it would be great if I both could be used simultaneously... of course, with a mobile device, the viable connections would change over time - and, ideally, the transition from one Wi-Fi router to the next would be seamless - and wouldn't even cause tcp connections to drop... assuming, of course, movement is constrained to an area with sufficiently many accessible Wi-Fi routers. Perhaps this is an issue with the underlying Wi-Fi support? 2. If multiple routers can be accessed, it would be great if the bandwidth of these routers could be combined, for example, when downloading a large file. 3. Cost seems a reasonable criteria to consider, too. For example, I know my mobile has a 1Gb fair-use policy; that I have to pay by the hour at some hot-spots and that my home router is un-metered, but slow. It would be great if configuration of my interfaces somehow embraced these concerns - and, perhaps, offered me options about the level of resources I'm willing to consume. I wonder if there are any plans to take development in these directions? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
2 usability ideas
Some suggestions: - let's add some info to http://projects.gnome.org/NetworkManager/ from http://www.arachnoid.com/linux/NetworkManager/index.html ...so that when the user clicks around (I never thought to right click it for a while) and clicks the About button, they will get some userful information - perhaps there should be a help button available with this info too It took me ages to figure out that settings are stored in gconf. It also took me ages to figure out if I right click and go to `edit connections` I can specify an IP manually and all sorts of things. I can now see that NetworkManager is a great program. But it took me so long to figure that out I was beginning to consider alternatives like wicd, like a lot of people. NetworkManager is an important program that people will judge the whole of linux so I want it even more idiot proof :-) _ Access your other email accounts and manage all your email from one place. http://clk.atdmt.com/UKM/go/167688463/direct/01/___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: So very close, but so frustrating...
snip then the following wvdial configuration to establish a PPP connection... snip So far, so good... but, when NetworkManager is not aware of a network connection (because the mobile phone connection has been patched-through from the command line) it refuses to allow me to turn on my VPN. OK. I may be way off here, but you mentioned two things: wvdial and command line as possible reasons for your problem. I don't understand all the nuances of it, but here is a thought: kppp instead of wvdial? NM does interfere with the kppp dialup (causing an instant disconnect upon connect) when it actively tries to connect to a WiFi network (or is already connected), but all I have to do then is to un-Enable Wireless, to prevent the interference. (Also, FWIW, for me kppp has worked flawlessly with my mobile broadband dialup. wvdial also works for me but takes A LOT longer to dial up, for some reason, than kppp - sometimes half a minute or more, whereas kppp is rather instantaneous) Again, I may be way off, but it's just that kppp has been a much smoother option than wvdial for me, and if command-line versus GUI is part of the NM issue here, maybe the VPN will work with a kppp connection? (At the moment I cannot test this myself) Andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: So very close, but so frustrating...
mobile device, the viable connections would change over time - and, ideally, the transition from one Wi-Fi router to the next would be seamless - and wouldn't even cause tcp connections to drop... assuming, I don't see how a transition like than can be seamless when I, for instance, have an SSH or FTP session. The ssh/ftp server would most definitely disconnect from the client, if the client changes its IP address. Or am I totally wrong? of course, movement is constrained to an area with sufficiently many accessible Wi-Fi routers. Perhaps this is an issue with the underlying Wi-Fi support? 2. If multiple routers can be accessed, it would be great if the bandwidth of these routers could be combined, for example, when downloading a large file. I once read something about combining multiple independent network interfaces (each with its own IP address) to make single requests, but it sounded rather complicated IIRC. Andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
pre-down hooks
Hi all, first of all, I'm new to this list, so greetings to everyone. I am missing pre-down hook functionality, too, as discussed previously on bugzilla [1] and this list [2], to safely shut down network services (unmount nfs shares, etc.) before nm brings down the connection. I am willing to hack on this, but I need a hand. I played with the code a bit, found the functions in nm-device.c and NetworkManagerUtils.c where the Action method on nm-dispatcher.action is called via DBus, and have a working patch that runs a dispatcher script before the interface is brought down by the code in nm-device.c. Unfortunately, there is some other code somewhere (nm-device-wifi.c?), which stops my wireless connection prematurely. Is there a place to call the pre-down hooks that will work for all devices, or do I have to hack multiple (all?) of the nm-device-*'s? Regards, Chris [1]https://bugzilla.gnome.org/show_bug.cgi?id=387832 [2]http://mail.gnome.org/archives/networkmanager-list/2009-August/msg00012.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: So very close, but so frustrating...
Andrew wrote: mobile device, the viable connections would change over time - and, ideally, the transition from one Wi-Fi router to the next would be seamless - and wouldn't even cause tcp connections to drop... assuming, I don't see how a transition like than can be seamless when I, for instance, have an SSH or FTP session. The ssh/ftp server would most definitely disconnect from the client, if the client changes its IP address. Or am I totally wrong? The IP address of the client need not change - if a VPN is used... of course, movement is constrained to an area with sufficiently many accessible Wi-Fi routers. Perhaps this is an issue with the underlying Wi-Fi support? 2. If multiple routers can be accessed, it would be great if the bandwidth of these routers could be combined, for example, when downloading a large file. I once read something about combining multiple independent network interfaces (each with its own IP address) to make single requests, but it sounded rather complicated IIRC. It is complicated, IMHO - but not impossible. Perhaps it is impractical - I'm not sure. It would be neat. Steve P.S. Humph - while (as far as I can tell) I had mobile connections working from my desk - today, trying to use the connection in real life, it failed... what's more - my adoption of Blueman prevented my old wvdial script from working - or, at least, I think that's what changed. Hurumph - it is rather temperamental. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Orinoco_cs WiFi under kernel-2.6.30
Dan Williams wrote: My classic Orinoco Gold PCMCIA card has not been working under Fedora/KDE (with WEP) for some time. Does anyone have this card working under Fedora? It works perfectly under Windows XP. I was looking at this again today. My laptop with a classic Orinoco Gold PCMCIA card, running Fedora-11, with NetworkManager-0.7.1-8.git20090708.fc11.i586, connects with WiFi under Windows XP, and also under Fedora with the network service. But it fails with the NetworkManager service. With the network service on, I see in /var/log/messages: [...@mary ~]$ sudo grep eth1 /var/log/messages* = Oct 3 21:43:42 mary kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Oct 3 21:43:42 mary kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Oct 3 21:43:42 mary avahi-daemon[1640]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.2.19. Oct 3 21:43:42 mary avahi-daemon[1640]: New relevant interface eth1.IPv4 for mDNS. Oct 3 21:43:42 mary avahi-daemon[1640]: Registering new address record for fe80::202:2dff:fe21:3c9 on eth1.*. Oct 3 21:43:42 mary avahi-daemon[1640]: Registering new address record for 192.168.2.19 on eth1.IPv4. Oct 3 21:43:45 mary ntpd[1859]: Listening on interface #3 eth1, fe80::202:2dff:fe21:3c9#123 Enabled Oct 3 21:43:45 mary ntpd[1859]: Listening on interface #5 eth1, 192.168.2.19#123 Enabled Oct 3 21:44:29 mary nm-system-settings:ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ... Oct 3 21:44:29 mary nm-system-settings:ifcfg-rh: read connection 'System dd-wrt (eth1)' = After turning NetworkManager on, and network off, and re-booting: = = Oct 3 23:21:24 mary kernel: pcmcia 0.0: pcmcia: registering new device pcmcia0.0 Oct 3 23:21:24 mary kernel: orinoco_cs 0.0: firmware: requesting agere_sta_fw.bin ... Oct 3 23:21:29 mary NetworkManager: info starting... Oct 3 23:21:29 mary NetworkManager: WARN nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():#012Sucess#012 ... Oct 3 23:21:29 mary NetworkManager: info (eth1): driver supports SSID scans (scan_capa 0x01). Oct 3 23:21:29 mary NetworkManager: info (eth1): new 802.11 WiFi device (driver: 'orinoco_cs') Oct 3 23:21:29 mary NetworkManager: info (eth1): exported as /org/freedesktop/Hal/devices/net_00_02_2d_21_03_c9 Oct 3 23:21:29 mary NetworkManager: info (ttyS0): ignoring due to lack of mobile broadband capabilties Oct 3 23:21:29 mary NetworkManager: info Trying to start the supplicant... Oct 3 23:21:29 mary NetworkManager: info Trying to start the system settings daemon... Oct 3 23:21:29 mary NetworkManager: info (eth1): supplicant manager state: down - idle Oct 3 23:21:29 mary nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Oct 3 23:21:29 mary nm-system-settings:ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ... Oct 3 23:21:29 mary nm-system-settings:ifcfg-rh: read connection 'System dd-wrt (eth1)' Oct 3 23:21:29 mary nm-system-settings:ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Oct 3 23:21:29 mary nm-system-settings:ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Oct 3 23:21:29 mary nm-system-settings:ifcfg-rh: read connection 'System eth0' ... Oct 3 23:21:34 mary NetworkManager: info (eth1): device state change: 1 - 2 (reason 2) Oct 3 23:21:34 mary NetworkManager: info (eth1): bringing up device. Oct 3 23:21:34 mary NetworkManager: info (eth1): preparing device. Oct 3 23:21:34 mary NetworkManager: info (eth1): deactivating device (reason: 2). Oct 3 23:21:34 mary kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Oct 3 23:21:34 mary NetworkManager: info (eth1): device state change: 2 - 3 (reason 0) Oct 3 23:21:34 mary NetworkManager: info (eth1): supplicant interface state: starting - ready = -- 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
