NM and local caching nameserver
Hello, I apologise if this has surfaced before, but I've not kept real track of NM developments recently. In the past I remember NM was going to use a local caching-only nameserver for resolution and put nameserver 127.0.0.1 in /etc/resolv.conf and use DBUS to notify it of upstream nameservers and interface changes. Does this still exist, and is there any canonical way to use it in Fedora 11? Thanks, James. -- The Holy ettlz theholyet...@googlemail.com PGP key ID: 03F94B5D --- 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: Network disabled after suspend/resume - sometimes
On Wed, 2009-01-07 at 09:35 +0100, Christoph Höger wrote: Hi folks, something strange happens on my fedora 9 notebook (thinkpad r61, e1000, iwl4965, nm-0.7 stable rpm): randomly (at least I could not figure out how to reproduce it yet), my network is set to disabled state after a suspend resume cycle. Setting to enabled makes things working again. So I would guess its NM not the driver having problems here. Hello, I've reported this in RH Bugzilla #477964: https://bugzilla.redhat.com/show_bug.cgi?id=477964 Regards, James -- The Holy ettlz theholyet...@googlemail.com PGP key ID: 03F94B5D --- 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
[Suggestion] Specify additional DHCP options?
Hello, Just trying out NetworkManager-0.7.0-0.11.svn3930.fc8 from Koji. send-hostname seems to be working great --- nice. You know, it might be useful (in the future) if there were a way to specify extra DHCP options via the GUI (or system settings?) to retrieve from the server, and expose them in the usual manner. Regards, James. -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: Network Manager and NFS
On Thu, 2008-08-14 at 11:29 -0700, Robert Smits wrote: I think what you're asking for is called Network Location Awareness --- how an interface distinguishes to which network it is attached, and then the machine configures itself as appropriate. I think there a few implementations of this [standards, anybody?] but personally I like this one: authenticated DHCP, since it should also work securely for plain old wired Ethernet. Will that also work with fixed IP addresses? Not unless said addresses are dished out by the DHCP server from its own fixed database. Otherwise, one would have to resort to something more exotic to determine the network, or do it manually. From my point of view, SCMP already works, but I can't use it together with Network Manager. Can we either configure Network Manager to work with SCMP or SCMP to work with Network Manager? I don't know which route is more feasible, largely because I don't understand from a technical viewpoint why the programs don't play nicely together. Is there a solution here that's easier than re-inventing the wheel? The best solution is probably a dbus-aware module for SCMP that listens for changes announced by NM, and reacts accordingly. This is something you might wish to discuss with the SCMP developers. James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: An Idea
On Wed, 2008-08-13 at 14:36 +0300, Tambet Ingo wrote: This can (and should) be done easily with dispatcher scripts. There's a lot of things that might need to be changed depending on location (things like printers, browser proxies, SMTP server, firewall, ...) I've been thinking about this recently --- is there an established, medium-neutral way of securely identifying a network? I was thinking of doing something like adding an extra option to DHCP that gave clients a HTTPS URL which they could use to identify and authenticate a network (triggered by an NMD hook), and then configure themselves according to a local database. James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: Network Manager and NFS
On Wed, 2008-08-13 at 14:37 -0700, Robert Smits wrote: My workaround, which isn't entirely satisfactory, is to use ifup and dispense with network manager altogether. Unfortunately, that doesn't allow me to see other possible network connections and make quick and easy connections when I'm on the road. What I still don't understand, though, is why Network Manager isn't configured to deal with managing changing nfs networks. I think what you're asking for is called Network Location Awareness --- how an interface distinguishes to which network it is attached, and then the machine configures itself as appropriate. I think there a few implementations of this [standards, anybody?] but personally I like this one: authenticated DHCP, since it should also work securely for plain old wired Ethernet. http://www.cl.cam.ac.uk/~sjm217/papers/securecomm07authdhcp.pdf I've got a bit of time on my hands, I might code up my earlier HTTPS idea. There's a whole bunch of things you can hook into changes in network such as iptables, service daemons, etc., and of course NFS mounts. But before that the relevant NLA infrastructure needs to be in place. This means having (1) a mechanism to identify the network, and (2) telling other processes (such as other config daemons) that we're on that network. It should be up to the latter what action we take. NM already has network link awareness, viz. Pidgin and Evolution. Am I right in thinking that the replacement for init is also dbus-aware? Of course, all this takes time ...and planning ;) James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: Network Manager and NFS
Hello,
I like the way Knetwork Manager and Network Manager work for the most part,
but I find I cannot use them - why - because I need to change my nfs networks
at each site I log into. And because network manager doesn't understand this,
I have to use ifup and scpm to do it.
The semi-canonical way to do it probably to add some hook scripts
into /etc/NetworkManager/dispatcher.d/. Last time I checked, the
dispatcher ran each of these scripts in alphanumeric order with
arguments
interface {up|down}
You'll probably need to cook up some of your own wizardry in order to
automatically decide what network you're on, then change the NFS mounts,
etc. (I don't think there's any way at present to automate this on a
per-user basis, although as far as I understand it'd certainly be
possible with the current NM to write a user session daemon that waits
for a particular network connection and then, say, does a FUSE mount.)
James.
--
The Holy ettlz [EMAIL PROTECTED]
PGP key ID: 03F94B5D
---
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: Automatic eth0 lost, and using DHCP send-hostname
Hi, 2. I can't seem to get the DHCP send-hostname feature to work. It only works for system connections at the moment, but if you have DHCP_HOSTNAME in your ifcfg file, it should pick that up and send it. Verify this by dumping /var/run/nm-dhclient-eth0.conf and seeing what options are in it. I've just been playing with this one at the moment in F8. I've got DHCP_HOSTNAME=rhapsody in both /etc/sysconfig/networking/devices/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth0 nm-applet on F8 now shows just Auto eth0, but I'll leave that for the time-being... anyway, with NetworkManager nm-dhclient-eth0.conf contains send host-name rhapsody; BUT I don't think the client is actually sending this --- I captured the packets with Wireshark and it's not in any of the DHCP request's options. When I ran /sbin/dhclient eth0 -cf /etc/dhclient-eth0.conf (which contains the same lines as nm-dhclient-eth0.conf above), the hostname request is part of the request packet, and the name resolves OK. Regards, James. -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: Automatic eth0 lost, and using DHCP send-hostname
On Sun, 2008-07-27 at 14:42 -0400, Dan Williams wrote: What's the output of: ps aux | grep dhclient root 886 0.0 0.0 4044 660 pts/0R+ 19:58 0:00 grep dhclient root 26497 0.0 0.0 2384 1044 ?S19:29 0:00 /sbin/dhclient -d -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/run/dhclient-eth0.lease -cf /var/run/nm-dhclient-eth0.conf eth0 while you're connected using NetworkManager? Are there any _more_ lines in /etc/dhclient-eth0.conf than what was in nm-dhclient-eth0.conf? Ah, sorry, Dan, seems I botched something... I had the old /etc/dhclient-eth0.conf lying around when I used NM and nm-dhclient-eth0.conf was # Created by NetworkManager # Merged from /etc/dhclient-eth0.conf send host-name rhapsody; /etc/dhclient-eth0.conf is *just* the last line above. Now I've removed /etc/dhclient-eth0.conf, nm-dhclient-eth0.conf is just # Created by NetworkManager In either case, the host name doesn't get set. I've also tried restarting NM, nm-applet nm-system-settings to see if I can get the System eth0 entry back, but it's now just Auto eth0, even though I have the relevant files in /etc/sysconfig/... Thanks, James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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
Automatic eth0 lost, and using DHCP send-hostname
Hello,
Just giving NetworkManager-0.7.0-0.11.svn3846.fc{89} a spin. A couple of
things:
1. My F8 machine has only System eth0 (no auto),
and my F9 machine has only Auto eth0.
I've purged /system/networking/connections in gconf, and restarted
nm-applet, but I can't get the missing connections back. Shouldn't
there be both? And how can I choose which one I want to auto-connect?
Actually, it seems that if I enable eth0 on boot on the F8 machine with
s-c-n, it will autoconnect System eth0... this doesn't *seem* to be
required on F9, since it only presents Auto eth0. Maybe the s-c-n
checkbox should be relabeled Connect automatically whenever link
available or something?
2. I can't seem to get the DHCP send-hostname feature to work.
I've set it using s-c-n, but in F9 (choosing Auto eth0) the machine
gets bound to a dynamically-assigned name, *not* the DHCP_HOSTNAME I
configured in ifcfg-interface. I still need the
old /etc/dhclient*.conf for it to work. Likewise in F8 (choosing System
eth0), although I've not been able to get it working even
with /etc/dhclient*.conf in place.
What have I done wrong?
Thanks,
James.
--
The Holy ettlz [EMAIL PROTECTED]
PGP key ID: 03F94B5D
---
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
Local caching nameserver
Hello, Forgive me as I've not been paying much attention, but what ever happened to NM configuring a local caching nameserver (rather than specifying servers in /etc/resolv.conf)? Is it still there, but hidden by some option I need to check? Thanks, James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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
Lots of segfaults in nm-system-settings
An excerpt from dmesg: nm-system-setti[14680]: segfault at ccbe5004 eip 00d01d78 esp bfbcba3c error 5 nm-system-setti[15193]: segfault at cb3e5004 eip 00d01d78 esp bf93279c error 5 nm-system-setti[15706]: segfault at b70e5004 eip 00d01d78 esp bf8e9f5c error 4 nm-system-setti[16222]: segfault at a79e5004 eip 00d01d78 esp bf909f7c error 4 nm-system-setti[16732]: segfault at 092e5004 eip 00d01d78 esp bff51dcc error 4 nm-system-setti[17246]: segfault at d9ce5004 eip 00d01d78 esp bfcba32c error 5 There are loads of other similar messages. This is with NetworkManager-0.7.0-0.6.8.svn3669.fc8 --- let me know if you need any more information. James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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
NetworkManager-0.7.0-0.6.7.svn3614.fc8 aborting on suspend/resume?
Hello, NM 0.7.0-0.6.7.svn3614.fc8 from Koji seems to be crashing on me through a suspend/resume cycle... seen on two different machines using iwl4965 and b43 drivers. NetworkManager: info (wlan0): device state change: 8 - 3 NetworkManager: info Deactivating device wlan0. Nothing to flush. Nothing to flush. NetworkManager: nm_act_request_get_connection: assertion `NM_IS_ACT_REQUEST (req)' failed NetworkManager: WARN remove_network_cb(): Couldn't remove network from supplicant interface: The requested network does not exist.. NetworkManager: WARN remove_network_cb(): Couldn't remove network from supplicant interface: The requested network does not exist.. NetworkManager: info Waking up from sleep. NetworkManager: info (eth0): now unmanaged NetworkManager: info (eth0): device state change: 2 - 1 NetworkManager: info eth0: Device is fully-supported using driver '8139too'. NetworkManager: info Found new Ethernet device 'eth0'. NetworkManager: info (eth0): exported as /org/freedesktop/Hal/devices/net_00_02_3f_68_15_45 A handler is already registered for the path starting with path[0] = org NetworkManager: Failed to register GObject with DBusConnection ** (process:2453): WARNING (recursed) **: WARN nm_signal_handler(): Caught signal 6. Generating backtrace... aborting... Aborted Thanks, James. -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: Some questions
Hmmm... My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack paper, but my Radius server is currently down). I frequently run into the situation where NetworkManager is not succeeding in authenticating to the AP. I have no sniffing data; I would like to see some packets, but Wireshark does not show interface eth1 (the wireless one). I end up having to reboot to get wireless working, or switch to wired. Does it authenticate OK when you take down the interface and restart NetworkManager? (I ask because I have a similar problem with one WAP that'll only authenticate once, *guaranteed*, but then never again; yet with another WAP backending to the same RADIUS server, it'll re-authenticate with no problems whenever I ask. See RH Bugzilla #434821.) James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: what do the two lights on NM tray icon mean?
I think it's basically: Bottom left: local station attempting to authenticate; then making DHCP request. Top right: DHCP response received, interface configured. James On 06/03/2008, Forrest Sheng Bao [EMAIL PROTECTED] wrote: Hi, There are two lights on NM tray icon when trying to connect to a network. One is at the bottom left corner of the icon. Another is at the top right of the icon. And there is a stuff circulating among those two. Generally the bottom left one turns to green before the top right one. After the connection is established, this icon turns back to a status icon. Can someone tell what do those two lights mean? Thanks, Forrest -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. ___ 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
nm-applet 0.7.0-0.6.7.svn3302.fc8 crash caused by bad auth?
On Wed, 2008-02-27 at 21:36 -0500, Dan Williams wrote: Did you downgrade _all_ the NM RPMs (nm, nm-gnome, nm-glib, etc) and then restart the machine to ensure a clean bootup? Worked OK again after a clean bootup. ;) As for nm-applet crashing, I've discovered some more. I power-cycled the WAP concerned and it now connects OK. I then killed the remote RADIUS server. As expected, it just kept prompting for secrets and fell back to wired when I pressed escape. I then power-cycled the WAP, still no RADIUS. I also restarted NetworkManager, and chose the misbehaving network. Again, it prompted me for the secrets. I filled these in. It failed to connect (good, no RADIUS). This time, I pressed escape and let it connect to wired. Then I chose the wireless network again --- and nm-applet terminated abnormally. To get it working again, I restarted NetworkManager and the WAP. So as far as I can see, there's some yet-to-be-understood state for a network (perhaps resulting from failed WPA/EAP-TLS auth?) which upsets nm-applet... James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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
NM 0.7.0-0.6.7.svn3302.fc8 broken with dbus-glib 0.73-6.fc8?
Hello, Having problems with nm-applet 0.7.0-0.6.7.svn3302.fc8. If I try to connec to my usual (WPA) network, I get this: ** (nm-applet:23750): WARNING **: Invalid connection given. ** (nm-applet:23750): WARNING **: WARN applet_menu_item_activate_helper(): Invalid connection; asking for more information. (nm-applet:23750): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed (nm-applet:23750): GLib-GObject-WARNING **: gtype.c:3339: type id `0' is invalid (nm-applet:23750): GLib-GObject-WARNING **: can't peek value table for type `invalid' which is not currently referenced and then it quits on signal 15, Bug Buddy kicks in, and there's a stack dump. The only thing I can think of that could've caused this is an update to dbus-glib-0.73-6.fc8. However I'm not convinced of this since downgrading doesn't help. The only other possible relevant packages upgraded then were pam-0.99.8.1-17.1.fc8.i386 and libnetfilter_conntrack-0.0.82-1.fc8.i386. [As a side note, I tried downgrading to NM 0.7.0-0.6.7.svn3235.fc8, but for some reason now the daemon just segfaults. Don't know what caused that, either.] Many thanks, James. -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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
NM 0.7.0-0.6.7.svn3302.fc8
Hello, I'm using the current Fedora 8 NetworkManager build from Koji (0.7.0-0.6.7.svn3302.fc8) and seeing some issues with WPA2. I just got a new router/access point that's configured for WPA2/EAP-TLS, alongside my old access point with WPA/EAP-TLS. Both connect to the same RADIUS server. The WPA network works fine, but the new WPA2 set-up seems to only ever be able to connect just *once*. This first connection will work fine. If I try to connect again, it fails and prompts for the certificate information again. To get it to work, I have to stop NetworkManager and nm-applet, ifconfig the interface down, and start them up again. Note in the logs that eth1 never gets beyond stage 4 with the second go. I've attached some logs (adjusted for privacy!) from nm-applet and NetworkManager. I also see the following from both the applet and manager: WARNING **: WARN list_connections_cb(): Couldn't retrieve system connections: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.. Setting SELinux to Permissive doesn't help. Thanks, James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- ** (nm-applet:19896): WARNING **: Settings invalid. ** (nm-applet:19896): WARNING **: Settings invalid. ** (nm-applet:19896): WARNING **: Settings invalid. ** (nm-applet:19896): WARNING **: Settings invalid. ** (nm-applet:19896): WARNING **: Settings invalid. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid or missing ssid ** (nm-applet:19896): WARNING **: Invalid connection read from GConf at /system/networking/connections/2. ** (nm-applet:19896): WARNING **: Invalid
[NM 0.7.0-0.6.7.svn3235/Fedora 8] DHCP and dynamic DNS send host-name
Hello, Just installed Fedora 8 with NetworkManager 0.7.0-0.6.7.svn3235 and I've been unable to figure out how to get the DHCP client to send host-name so my notebook is identified by the local DNS with its host-name (rather than dyn-192-168-192-nnn from the DHCP server). Under NM 0.6, this used to work by placing send host-name given-name; in /etc/dhclient-eth1.conf, but now DHCP seems to be handled by something called nm-dhcp-client.action. Have I missed something, or is this unimplemented? Thanks, James. -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
