RE: v6 only networks broken?
Does nm currently support both stateful and stateless ipv6 address auto configurations? Mentioned below is that the ipv6 infratructure is already done for nm, I wonder what is missing in ipv6 implementation with nm 0.7 RC2 release? I am mostly interested in wired networks. What is the expected time frame for this full ipv6 feature delivery? Thanks, Weiwen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Williams Sent: Friday, November 21, 2008 10:46 AM To: Paul Wouters Cc: networkmanager-list@gnome.org Subject: Re: v6 only networks broken? On Fri, 2008-11-21 at 02:40 -0500, Paul Wouters wrote: > hi, > > I am not sure if someelse else at IETF already raised this, but NM > does not work on IPv6 only networks. After association on the wifi, it > disassociates with "could not obtain an address". We suspect because > it did not get an ipv4 ip address via dhcp, though we did get an ipv6 > address. Correct; NM won't (yet) try to get IPv6 addresses, though we have some infrastructure to handle IPv6 via LL, router advertisements, and DHCP +/- information only mode, it's not all there. Full IPv6 support will be added in the near future and is a major target for post 0.7 development. NM should not stomp on IPv6 LL addresses that get assigned to the interface however. If it does, it's a bug. 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: FWD: [PATCH] (Fixed) Support for openvpn --auth option
On Mon, Nov 24, 2008 at 10:31:13PM +0100, Robert Vogelgesang wrote: > Hello, > > two weeks ago I posted the attached message to this list. > Since then, I received not a single response. Does really > nobody care? Nobody interested in further development of > the openvpn plugin? Openvpn improvements and new features are definitly much appreciated ... its just that NM 0.7 is supposed to be released any day and hence the tree is pretty much locked down. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network manager install ?
On Mon, Nov 24, 2008 at 08:43:07PM +, Walter wrote: > I have just installed Xubuntu and have no icon for NM. Synaptic tells > me it is installed but how do I get it to run? I tried alt F2 with no > success. I then installed WICD got it to work but every few seconds it > looses the connection. I would like to remove this if I can get MN to > run. Any help appreciated. I am quite sure you are having legacy configurations in /etc/network/interfaces ... If so you are probably seeing: https://bugs.launchpad.net/bugs/289466 easiest solution is to clean /etc/network/interfaces and reboot. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
FWD: [PATCH] (Fixed) Support for openvpn --auth option
Hello,
two weeks ago I posted the attached message to this list.
Since then, I received not a single response. Does really
nobody care? Nobody interested in further development of
the openvpn plugin?
Robert
--- Begin Message ---
Hello everybody,
please find attached the second (and fixed) version of my patch to add
support for the --auth option of openvpn to the NetworkManager-openvpn
plugin. The patch is against NetworkManager-openvpn-0.7.0-16.svn4027
(Fedora 9).
My work was triggered by the fact that I tried (and failed) to get a
"SSL VPN" connection to an Astaro firewall, using Fedora 9. The logs
showed that Astaro used MD5 HMAC authentication, whereas my Fedora 9
system used SHA1 (the default). So I started hacking...
The attached patch is sufficient to get a working "SSL VPN" connection
to an Astaro firewall.
For minimal impact, I choose to implement the --auth option in the
same way as the --cipher option. Both the "new" --auth and the "old"
--cipher options share the following issues:
o When a non-default value was saved and you want to switch back
to "Default" later on, then this change does not get saved and
the non-default value remains in the config.
As far as I understand the plugin code, this issue seems to be
caused by NetworkManager or gconfd, not by the openvpn plugin
(the hash returned by advanced_dialog_new_hash_from_dialog() does
not contain the --auth/--cipher value when "Default" was chosen).
Is this a known issue? (bugzilla.gnome.org didn't show anything
similar for NetworkManager)
o Openvpn supports these options for both static and TLS modes.
The openvpn plugin for NetworkManager carries the --cipher option
(and with my patch, the --auth option, too) on the "Certificates
(TLS)" tab of the "advanced" popup, which is only available when
using TLS modes and not when using static keys.
The easiest fix would be to move the popup-menue(s) (GtkComboBox)
for --cipher (and --auth) to the "General" tab. A little bit more
work, but maybe better for future extensions: Introduce a new
tab "Encryption" for these options. What do you think/prefer?
I'm willing to fix the second issue and to do some more research on the
first one if there is a real chance that support for the --auth option
of openvpn gets accepted into the NetworkManager distribution. ;-)
Robert
diff -u NetworkManager-openvpn-0.7.0/properties/auth-helpers.c.hmacauth
NetworkManager-openvpn-0.7.0/properties/auth-helpers.c
--- NetworkManager-openvpn-0.7.0/properties/auth-helpers.c.hmacauth
2008-08-29 15:30:50.0 +0200
+++ NetworkManager-openvpn-0.7.0/properties/auth-helpers.c 2008-11-09
21:35:56.0 +0100
@@ -585,6 +585,7 @@
NM_OPENVPN_KEY_TAP_DEV,
NM_OPENVPN_KEY_PROTO_TCP,
NM_OPENVPN_KEY_CIPHER,
+ NM_OPENVPN_KEY_AUTH,
NM_OPENVPN_KEY_TA_DIR,
NM_OPENVPN_KEY_TA,
NULL
@@ -734,6 +735,50 @@
g_strfreev (items);
}
+#define HMACAUTH_COL_NAME 0
+#define HMACAUTH_COL_DEFAULT 1
+
+static void
+populate_hmacauth_combo (GtkComboBox *box, const char *hmacauth)
+{
+ GtkListStore *store;
+ GtkTreeIter iter;
+ gboolean active_initialized = FALSE;
+ gchar **item;
+ gchar *items[] = {
+ NM_OPENVPN_AUTH_NONE,
+ NM_OPENVPN_AUTH_MD5,
+ NM_OPENVPN_AUTH_SHA1,
+ NULL
+ };
+
+ store = gtk_list_store_new (2, G_TYPE_STRING, G_TYPE_BOOLEAN);
+ gtk_combo_box_set_model (box, GTK_TREE_MODEL (store));
+
+ /* Add default option which won't pass --auth to openvpn */
+ gtk_list_store_append (store, &iter);
+ gtk_list_store_set (store, &iter,
+ HMACAUTH_COL_NAME, _("Default"),
+ HMACAUTH_COL_DEFAULT, TRUE, -1);
+
+ /* Add options */
+ for (item = items; *item; item++) {
+ gtk_list_store_append (store, &iter);
+ gtk_list_store_set (store, &iter,
+ HMACAUTH_COL_NAME, *item,
+ HMACAUTH_COL_DEFAULT, FALSE, -1);
+ if (hmacauth && !strcmp (*item, hmacauth)) {
+ gtk_combo_box_set_active_iter (box, &iter);
+ active_initialized = TRUE;
+ }
+ }
+
+ if (!active_initialized)
+ gtk_combo_box_set_active (box, 0);
+
+ g_object_unref (store);
+}
+
static void
tls_auth_toggled_cb (GtkWidget *widget, gpointer user_data)
{
@@ -840,6 +885,10 @@
value = g_hash_table_lookup (hash, NM_OPENVPN_KEY_CIPHER);
populate_cipher_combo (GTK_COMBO_BOX (widget), value);
+ widget = glade_xml_get_widget (xml, "hmacauth_combo");
+ value = g_hash_table_lookup (hash, NM_OPENVPN_KEY_AUTH);
+
Network manager install ?
I have just installed Xubuntu and have no icon for NM. Synaptic tells me it is installed but how do I get it to run? I tried alt F2 with no success. I then installed WICD got it to work but every few seconds it looses the connection. I would like to remove this if I can get MN to run. Any help appreciated. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: default route problem
On Mon, 24/11/2008 at 14:13 -0500, Dan Williams wrote: > > Once I've tried to define custom routes but failed. I don't try to > > modify the routes via UI. As far as I see it does not allow to > configure > > the default route device. > > > > The issue is that the NM doesn't configure the routing table > correctly. > > It does not use the ppp0 device for routing at all. And I have no > any > > idea where does it get the over rules from. > > If the VPN connection has custom non-host routes (either entered via > the > UI or sent from the server), the VPN will not be the default device. > If > there are no custom routes, or custom host routes, the VPN connection > will be the default. > > Which exact svn revision are you running? I'm using following packages: --- $ rpm -qa | grep NetworkManager NetworkManager-pptp-0.7.0-0.10.svn4027.fc9.i386 NetworkManager-glib-0.7.0-0.11.svn4022.4.fc9.i386 NetworkManager-gnome-0.7.0-0.11.svn4022.4.fc9.i386 NetworkManager-0.7.0-0.11.svn4022.4.fc9.i386 --- You was right. I've used the custom routes. But I've used --- /etc/ppp/ip-up.local /etc/ppp/ip-down.local --- I just didn't think that NetworkManager uses pptp to establish the pptp connection :) I've removed these files and the NM works correctly. Now my my wife will be able to connect the Internet herself. Thank you for your help. -- Kuznetsov Vyacheslav ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: More VPN foolishness
On Sun, Nov 16, 2008 at 08:57:54AM -0330, Tor Fosnaes wrote: > I finally got DW's rc-2 files and, lo and behold, they don't seem to > want to install using the configure, make, install instructions. > Oh Lord, I grow weary. > > Is there anyone with a straightforward, push the button fix for the VPN > failure? Are you still on ubuntu intrepid? Please test the Stable Release Update package currently sitting in intrepid-proposed. See: https://launchpad.net/ubuntu/+source/network-manager-pptp/0.7~~svn20081015t024626-0ubuntu1.8.10.1 - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM and my Vodafone PCMCIA-card doesnt work, NM uses /dev/ttyUSB0 instead of /dev/ttyUSB2
On Mon, Nov 17, 2008 at 10:53:28AM +0200, Tambet Ingo wrote: > On Mon, Nov 17, 2008 at 10:48 AM, Knud Müller <[EMAIL PROTECTED]> wrote: > > yes! This one works. I made a diff > > I'll ask a HAL maintainer to include it to upstream. Hi, Did that happen yet? Otherwise, I can take care that this gets committed upstream. Thanks! - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IEEE802.1x + STATIC WEP
I think that there is an cisco ap here, so maybe is this the case.
On Mon, 2008-11-24 at 03:38 +0200, Tomas Winkler wrote:
> On Thu, Nov 20, 2008 at 8:20 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
> > On Wed, 2008-11-19 at 14:41 -0600, Mario Medina wrote:
> >> Hi! I have in my office a uncommon configuration of the network, weuse
> >> IEEE802.1x keymanagement with TLS and static WEP keys, is N-M capable
> >> of configuring this type of network?
> >
> > Not at this time; this is the first instance I've heard of this, and
> > kinda pointless actually as the WEP key doesn't rotate...
> >
> > Any idea what AP hardware and RADIUS server is backing your network
> > setup?
>
> > Dan
>
> It may be a case of so called transitional setups where both
> legacy(WEP) only and WPA are supported. Usually bcast is all in WEP.
> Just a guess.
> I think Cisco APs can support this
> Tomas
>
>
> >> At this time I do the connection manually with this:
> >>
> >> ctrl_interface=/var/run/wpa_supplicant
> >> ctrl_interface_group=admin
> >> update_config=1
> >>
> >> network={
> >> ssid="wnetwork"
> >> key_mgmt=IEEE8021X
> >> auth_alg=OPEN
> >> eap=TLS
> >> identity="myusername"
> >> password="mypassword"
> >> ca_cert="/etc/network/cacert.pem"
> >> client_cert="/etc/network/cert.pem"
> >> private_key="/etc/network/key.pem"
> >> private_key_passwd="thekeypassword"
> >> wep_key0=hex static wep key
> >> disabled=0
> >> }
> >>
> >> and it connects. sometimes i need to issue a manual iwconfig to set
> >> the key, but at this time i can't find the way to do this with N-M.
> >>
> >> Thanks
> >>
> >> Cristo te Ama. Por que de tal manera te amó Dios, que dio a su único
> >> Hijo, para que vivas con Dios eternamente, si es que crees en su Hijo.
> >> www.iglesiacristianaebenezer.com
> >> Salud Integral: www.drmedina.com.mx
> >> Todo de Linux: www.viviendolinux.com
> >>
> >> ___
> >> NetworkManager-list mailing list
> >> NetworkManager-list@gnome.org
> >> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: default route problem
On Sun, 2008-11-23 at 23:22 +0300, Kuznetsov Vjacheslav wrote: > > On Mon, 2008-10-06 at 15:51 +0400, Vitja Makarov wrote: > > > Hi, all! > > > > > > Home ISP often use the following network configuration scheme: > > > > > > - Lan IP address is assigned using DHCP > > > - PPTP is used for internet connection > > > > > > If pptp server is in your network, that should be ok to replace > > > default route with ppp one, > > > but when pptp server is routed via DHCP provided default route, you > > > can't simply do it, > > > you have first provide manually route for pptp server, then remove > > default. > > > > NM should be adding a specific route to the PPTP server via the > > underlying device so that you can always get to the PPTP server while > > connected. Then, it should be changing the default route to route > > everything through the VPN _unless_ you've added your own specific > > routes via the connection editor or the server has sent you specific > > routes. > > > > It seems it's not doing that here, correct? > > I have a similar issue trying to use PPTP for internet connection. I > have wrong default gateway device after the pptp connection established. > Here is the routing table before pptp: > > --- > $ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > 10.73.197.0 0.0.0.0 255.255.255.0 U 0 00 > eth0 > 0.0.0.0 10.73.197.1 0.0.0.0 UG0 00 > eth0 > > $ ip route show > 10.73.197.0/24 dev eth0 proto kernel scope link src 10.73.197.6 > default via 10.73.197.1 dev eth0 proto static > --- > > and following I get after connection is done: > > --- > $ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > 0.0.0.0 10.73.197.1 255.255.255.255 UGH 0 00 > eth0 > 10.73.100.1 10.73.197.1 255.255.255.255 UGH 0 00 > eth0 > 10.73.197.0 0.0.0.0 255.255.255.0 U 0 00 > eth0 > 10.73.0.0 0.0.0.0 255.255.0.0 U 0 00 > eth0 > 0.0.0.0 10.73.100.1 0.0.0.0 UG0 00 > eth0 > > $ ip route show > 0.0.0.0 via 10.73.197.1 dev eth0 proto static > 10.73.100.1 via 10.73.197.1 dev eth0 src 10.73.197.6 > 10.73.197.0/24 dev eth0 proto kernel scope link src 10.73.197.6 > 10.73.0.0/16 dev eth0 scope link > default via 10.73.100.1 dev eth0 > --- > > As you can see it does not use the ppp0 device. And I have to correct > the default route to have the internet: Have you defined any custom routes in the UI? AFAIK pptp cannot return custom routes from the VPN server, so that means you probably configured custom routes. These are pointless when the VPN is meant to be the default route (since the traffic to that device would usually just be routed over the VPN anyway when the kernel hits 0.0.0.0 in the routing table). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: v6 only networks broken?
On Fri, 2008-11-21 at 16:56 -0500, Paul Wouters wrote: > On Fri, 21 Nov 2008, Dan Williams wrote: > > > NM should not stomp on IPv6 LL addresses that get assigned to the > > interface however. If it does, it's a bug. > > It disassociates from the wifi network. Yes, because you don't get an IPv4 address. If you use static IP for that network, you'll get assigned an IPv6LL address and NM won't touch it. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IEEE802.1x + STATIC WEP
On Mon, 2008-11-24 at 03:38 +0200, Tomas Winkler wrote:
> On Thu, Nov 20, 2008 at 8:20 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
> > On Wed, 2008-11-19 at 14:41 -0600, Mario Medina wrote:
> >> Hi! I have in my office a uncommon configuration of the network, weuse
> >> IEEE802.1x keymanagement with TLS and static WEP keys, is N-M capable
> >> of configuring this type of network?
> >
> > Not at this time; this is the first instance I've heard of this, and
> > kinda pointless actually as the WEP key doesn't rotate...
> >
> > Any idea what AP hardware and RADIUS server is backing your network
> > setup?
>
> > Dan
>
> It may be a case of so called transitional setups where both
> legacy(WEP) only and WPA are supported. Usually bcast is all in WEP.
> Just a guess.
> I think Cisco APs can support this
Hmmm, could be. Though I was under the impression that devices that
wouldn't have supported WPA at the time (ie, old PDAs, embedded
terminals, PoS stuff, etc) were also usually never updated to support
802.1x either... Not sure though.
dan
> Tomas
>
>
> >> At this time I do the connection manually with this:
> >>
> >> ctrl_interface=/var/run/wpa_supplicant
> >> ctrl_interface_group=admin
> >> update_config=1
> >>
> >> network={
> >> ssid="wnetwork"
> >> key_mgmt=IEEE8021X
> >> auth_alg=OPEN
> >> eap=TLS
> >> identity="myusername"
> >> password="mypassword"
> >> ca_cert="/etc/network/cacert.pem"
> >> client_cert="/etc/network/cert.pem"
> >> private_key="/etc/network/key.pem"
> >> private_key_passwd="thekeypassword"
> >> wep_key0=hex static wep key
> >> disabled=0
> >> }
> >>
> >> and it connects. sometimes i need to issue a manual iwconfig to set
> >> the key, but at this time i can't find the way to do this with N-M.
> >>
> >> Thanks
> >>
> >> Cristo te Ama. Por que de tal manera te amó Dios, que dio a su único
> >> Hijo, para que vivas con Dios eternamente, si es que crees en su Hijo.
> >> www.iglesiacristianaebenezer.com
> >> Salud Integral: www.drmedina.com.mx
> >> Todo de Linux: www.viviendolinux.com
> >>
> >> ___
> >> NetworkManager-list mailing list
> >> NetworkManager-list@gnome.org
> >> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
vpnc compatible racoon configuration (to work with NM)
Hey, I tried to setup racoon.conf to work with NMs vpnc plugin. There were not many helpful google hits, so if someone needs a racoon config for racoon+xauth_psk: http://www.informatik.uni-bremen.de/~fabiand/racoon-vpnc/index.html Greetings fabian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: fqdn, dhclient.conf and networkmanager ?
On Mon, 2008-11-24 at 11:31 +0100, Patrik.Martinsson wrote: > Hi, > > Monday and I'm still stuck with this. However I'm not giving up, the > thing is that i need this working. There a possible workaround for me > until we get this understood. I'm thinking, dhclient-scripts, that's > what I've used before to manually update the dns's with nsupdate. But > that shouldn't be necessary. > > Anyway, back to my problem again. I have noticed when I'm looking > through the logs from wireshark that when dhclient is used from the > commandline, that it looks like this, Can you move /sbin/dhclient-script away and replace it with something that just dumps the environment? Just to isolate the issue to dhclient itself. Dan > --- > Source Destination Protocol Info > CompalIn_f1:ed:84 Broadcast ARP Who has 10.64.0.1? > Tell 10.64.4.89 > Source Destination Protocol Info > Cisco_31:9c:43 CompalIn_f1:ed:84 ARP 10.64.0.1 is at > 00:1e:f6:31:9c:43 > Source Destination Protocol Info > 10.64.4.89 172.16.0.40 DNS Standard query SOA > nrlx038.dyn.smhi.se > Source Destination Protocol Info > 172.16.0.4010.64.4.89DNS Standard query > response > Source Destination Protocol Info > 10.64.4.89 172.16.0.40 DNS Standard query NS > dyn.smhi.se > Source Destination Protocol Info > 172.16.0.4010.64.4.89DNS Standard query > response NS adde.ad.smhi.se NS adele.ad.smhi.se NS adrian.ad.smhi.se > Source Destination Protocol Info > 10.64.4.89 172.16.0.40 DNS Dynamic update SOA > dyn.smhi.se > --- > Notice the ARP question and the DNS querying. > > This is never done when i use NetworkManager, there is neither an ARP > question or DNS querying. > Why that is, i have no idea ?? > > > I cannot come to any other conclusion that this is a bug from > NetworkManagers side, I'm feeling like Ive tried everything now and I'm > running empty on suggestion. > > Patrik Martinsson > ITi > SMHI > [EMAIL PROTECTED] > > > On Fri, 2008-11-21 at 13:17 +0100, Patrik.Martinsson wrote: > > Hi again, > > > > I'm still stuck with the same problem, I've now gotten a step deeper and > > started to dig around with strace. Ive also updated to fedora 10 to try > > it out with the latest versions and give you the results from there. > > I have totally disabled IPV6 and do not seem to have any of those > > packets anymore when i look with wireshark. > > However, i still face the same behavior and my problem remains. > > > > I'm attaching parts of the strace logs from the > > successful /sbin/dhclient and the unsuccessful /usr/sbin/NetworkManager, > > and maybe you guys can figure it out why it acts different depending on > > from where its called. > > > > Maybe i can raise the question somewhere else to, i have no idea where > > thou ? > > > > Suggestions are more then welcome. > > > > Patrik Martinsson > > ITi > > SMHI > > [EMAIL PROTECTED] > > > > > > On Wed, 2008-11-19 at 11:39 -0500, Dan Williams wrote: > > > On Wed, 2008-11-19 at 15:49 +0100, Patrik.Martinsson wrote: > > > > On Tue, 2008-11-18 at 11:08 -0500, Dan Williams wrote: > > > > > On Tue, 2008-11-18 at 10:25 +0100, Patrik.Martinsson wrote: > > > > > > Hello all ! > > > > > > > > > > > > I have a question regarding using NetworkManager and > > > dhclient.conf, > > > > > > maybe i don't understand this right, but however. > > > > > > > > > > > > I would like to use NetworkManager but it seems like im not able > > > to > > > > > > apply the same commands to the dhcp server as with dhclient, is > > > > > > NetworkManager using dhclient or does it gets its ip in some > > > other > > > > > > way ? > > > > > > > > > > > > I need the same behavior with NetworkManager as a have with > > > dhclient, > > > > > > regarding the options for dynamic update. This is how my > > > dhclient.conf > > > > > > looks today, and i need Networkmanagar to act the same, > > > > > > > > > > > > send fqdn.fqdn "hostname."; > > > > > > send fqdn.encoded off; > > > > > > send fqdn.server-update off; > > > > > > append domain-search "foo.bar.com","foo2.bar.com"; > > > > > > > > > > domain-search can be configured in the 'searches' option in the > > > UI, > > > > > either with static or "Automatic (addresses only)". > > > > > > > > > > So does the DHCP server no honor the send-hostname directive? > > > That may > > > > > be a Microsoft DNS only option, but I was under the impression > > > that the > > > > > ISC dhcp server supported that as well. > > > > > > > > > > If not, maybe we need to send the other 3 as well, though the > > > comment in > > > > > 'man dhclient.conf' about encoded on/off doesn't sound very > > > promisin
mobile-broadband-provider-info 20081124 released
mobile-broadband-provider-info 20081124 === * Bjørn Lie added NetworkNorway and a bunch of other operatorusing the same network * Matheus Pacheco de Andrade added Brazilian provider Vivo * Anton Blanchard added Australian provider Exetel * Joseph Price fixed the APN of 3 UK * Konstantinos Togias fixed the APN of Vodafone Greece * Martin Pitt and Alejandro Romero Herrera provided WebSessions * Aldo Bassanini added Ecuadorian provider Porta 3G * Gabor Kelemen updated Hungarian providers * Florian Eberle updated APN of Orange Switzerland http://svn.gnome.org/viewvc/mobile-broadband-provider-info/tags/ What is mobile-broadband-provider-info === The module contains mobile broadband settings for different service providers in different countries. The package contains only informational files so it's safe for distributions to grab updates even during feature freeze and maintenance stages. Service provider specific information is stored in a XML file. XML is not the most optimized format for a database, but it's easy to read, understand and edit. The database is released under Creative Commons Public Domain (CC-PD). for more info, see: http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: fqdn, dhclient.conf and networkmanager ?
Hi, Monday and I'm still stuck with this. However I'm not giving up, the thing is that i need this working. There a possible workaround for me until we get this understood. I'm thinking, dhclient-scripts, that's what I've used before to manually update the dns's with nsupdate. But that shouldn't be necessary. Anyway, back to my problem again. I have noticed when I'm looking through the logs from wireshark that when dhclient is used from the commandline, that it looks like this, --- Source Destination Protocol Info CompalIn_f1:ed:84 Broadcast ARP Who has 10.64.0.1? Tell 10.64.4.89 Source Destination Protocol Info Cisco_31:9c:43 CompalIn_f1:ed:84 ARP 10.64.0.1 is at 00:1e:f6:31:9c:43 Source Destination Protocol Info 10.64.4.89 172.16.0.40 DNS Standard query SOA nrlx038.dyn.smhi.se Source Destination Protocol Info 172.16.0.4010.64.4.89DNS Standard query response Source Destination Protocol Info 10.64.4.89 172.16.0.40 DNS Standard query NS dyn.smhi.se Source Destination Protocol Info 172.16.0.4010.64.4.89DNS Standard query response NS adde.ad.smhi.se NS adele.ad.smhi.se NS adrian.ad.smhi.se Source Destination Protocol Info 10.64.4.89 172.16.0.40 DNS Dynamic update SOA dyn.smhi.se --- Notice the ARP question and the DNS querying. This is never done when i use NetworkManager, there is neither an ARP question or DNS querying. Why that is, i have no idea ?? I cannot come to any other conclusion that this is a bug from NetworkManagers side, I'm feeling like Ive tried everything now and I'm running empty on suggestion. Patrik Martinsson ITi SMHI [EMAIL PROTECTED] On Fri, 2008-11-21 at 13:17 +0100, Patrik.Martinsson wrote: > Hi again, > > I'm still stuck with the same problem, I've now gotten a step deeper and > started to dig around with strace. Ive also updated to fedora 10 to try > it out with the latest versions and give you the results from there. > I have totally disabled IPV6 and do not seem to have any of those > packets anymore when i look with wireshark. > However, i still face the same behavior and my problem remains. > > I'm attaching parts of the strace logs from the > successful /sbin/dhclient and the unsuccessful /usr/sbin/NetworkManager, > and maybe you guys can figure it out why it acts different depending on > from where its called. > > Maybe i can raise the question somewhere else to, i have no idea where > thou ? > > Suggestions are more then welcome. > > Patrik Martinsson > ITi > SMHI > [EMAIL PROTECTED] > > > On Wed, 2008-11-19 at 11:39 -0500, Dan Williams wrote: > > On Wed, 2008-11-19 at 15:49 +0100, Patrik.Martinsson wrote: > > > On Tue, 2008-11-18 at 11:08 -0500, Dan Williams wrote: > > > > On Tue, 2008-11-18 at 10:25 +0100, Patrik.Martinsson wrote: > > > > > Hello all ! > > > > > > > > > > I have a question regarding using NetworkManager and > > dhclient.conf, > > > > > maybe i don't understand this right, but however. > > > > > > > > > > I would like to use NetworkManager but it seems like im not able > > to > > > > > apply the same commands to the dhcp server as with dhclient, is > > > > > NetworkManager using dhclient or does it gets its ip in some > > other > > > > > way ? > > > > > > > > > > I need the same behavior with NetworkManager as a have with > > dhclient, > > > > > regarding the options for dynamic update. This is how my > > dhclient.conf > > > > > looks today, and i need Networkmanagar to act the same, > > > > > > > > > > send fqdn.fqdn "hostname."; > > > > > send fqdn.encoded off; > > > > > send fqdn.server-update off; > > > > > append domain-search "foo.bar.com","foo2.bar.com"; > > > > > > > > domain-search can be configured in the 'searches' option in the > > UI, > > > > either with static or "Automatic (addresses only)". > > > > > > > > So does the DHCP server no honor the send-hostname directive? > > That may > > > > be a Microsoft DNS only option, but I was under the impression > > that the > > > > ISC dhcp server supported that as well. > > > > > > > > If not, maybe we need to send the other 3 as well, though the > > comment in > > > > 'man dhclient.conf' about encoded on/off doesn't sound very > > promising. > > > > > > > > In the end, you should be able to put these options > > > > in /etc/dhclient-eth0.conf (or whatever the interface name is) and > > have > > > > them merged in by NetworkManager. > > > > > > > > Dan > > > > > > Hello, again ! > > > > > > I've spent almost 2 days on this particular problem now, and come up > > > with some conclusions about whats going on and why it's not behaving > > > like i want it to. > > > > > > I take this
