Re: Networkmanager + Bluetooth
Hi. After some more testing I found out that NM is able to bring up the connection when following these steps: 1. sudo rfcomm connect hci0 2. In nm-applet you can now start the already configured connection My questions are now: - Is it possible to lable the bluetooth based connections as "Bluetooth" or whatever. - why do i need to open the rfcomm connection? Isn't it enought to bind to the mobile? -- HG > I am currently looking for way to use bluetooth based dial up together > with networkmanager. > > Can someone give me an overview? What I'm looking for is > > 1. simple dialog for the initial pairing > 2. an entry in nm-applet to bring up or disconnect the connection > 3. I need to configure the apn + chap credentials. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IP4Config and routes
On Thu, 2009-12-17 at 14:22 -0800, Dan Williams wrote: > What would you expect the routing table to look like in your case? I > suppose we could do a default route for link-local. Not sure if that > will confuse apps that expect a default route to mean an internet > connection though. I would expect the subnet route, as NM is creating already: dest=169.254.0.0 gateway=0.0.0.0 genmask=255.255.0.0 I would also like the routing table to either include a default route: dest=0.0.0 gateway=0.0.0.0 genmask=0.0.0.0 or a multicast one: dest=224.0.0.0 gateway=0.0.0.0 genmask=240.0.0.0 The routing table that NM is setting up now is reasonable, in my opinion, but there should be some way of customizing the behaviour in the settings object. Daniel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IP4Config and routes
Dan Williams a écrit : > What would you expect the routing table to look like in your case? I > suppose we could do a default route for link-local. Not sure if that > will confuse apps that expect a default route to mean an internet > connection though. Such apps are damned to be confused anyway, think for instance of a private network. So not worth considering. Correctly designed apps just try to connect whenever they see a chance, and report the connection failure if any. Anything more clever is doomed to fail in some of the zillions possible network configurations out there. Note that I am *not* talking about NetworkManager here, but about network apps. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Networkmanager + Bluetooth
Hello, I am currently looking for way to use bluetooth based dial up together with networkmanager. Can someone give me an overview? What I'm looking for is 1. simple dialog for the initial pairing 2. an entry in nm-applet to bring up or disconnect the connection 3. I need to configure the apn + chap credentials. Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
Hello Dan Doing as you told (killing and starting the service as sudo) i have the following results: The error message from nm-applet is that the vpn-service can not b e started. When this happens there are no messages in the terminal. When I retry this a few times then hundreds of messages appear and the vpn connection is setup normally. I think this will not be to interresting. Finally closing vpn and then try to reopen gives the following: Fri Dec 18 09:04:09 2009 us=69544 SIGTERM[hard,] received, process exiting Fri Dec 18 09:04:09 2009 us=70616 PKCS#11: pkcs11_terminate - entered Fri Dec 18 09:04:09 2009 us=70716 PKCS#11: pkcs11h_terminate entry Fri Dec 18 09:04:09 2009 us=70758 PKCS#11: Removing providers Fri Dec 18 09:04:09 2009 us=70795 PKCS#11: Releasing sessions Fri Dec 18 09:04:09 2009 us=70829 PKCS#11: Terminating slotevent Fri Dec 18 09:04:09 2009 us=70864 PKCS#11: _pkcs11h_slotevent_terminate entry Fri Dec 18 09:04:09 2009 us=70899 PKCS#11: _pkcs11h_slotevent_terminate return Fri Dec 18 09:04:09 2009 us=70933 PKCS#11: Marking as uninitialized Fri Dec 18 09:04:09 2009 us=70983 PKCS#11: pkcs11_terminate - return ** Message: Connect timer expired, disconnecting. ** (process:20896): WARNING **: connect_timer_expired(): Disconnect failed: Could not process the request because no VPN connection was active. ** Message: Connect timer expired, disconnecting. Op donderdag 17-12-2009 om 14:54 uur [tijdzone -0800], schreef Dan Williams: > /usr/lib/network-manager-openvpn/nm-openvpn-service > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
