Re: [ANNOUNCE] ModemManager (for GSM and CDMA)

2008-08-01 Thread Helmut Schaa

Am Do 31 Jul 2008 17:10:57 CEST schrieb Tambet Ingo [EMAIL PROTECTED]:


Q: What does it have to do with NetworkManager?
A: NetworkManager will use ModemManager instead of current basic code
in the future.


Great.

Which changes will be needed for NM frontends? Are there any drastic  
API changes or do the settings need refactoring?


Thanks,
Helmut
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: [ANNOUNCE] ModemManager (for GSM and CDMA)

2008-08-01 Thread Tambet Ingo
On Fri, Aug 1, 2008 at 8:59 AM, Helmut Schaa [EMAIL PROTECTED] wrote:
 Which changes will be needed for NM frontends? Are there any drastic API
 changes or do the settings need refactoring?

First of all, this all will happen after 0.7 release.

There are no NetworkManager API changes, but we'll need to add new
methods and signals to the modem devices to use the new functionality.
The settings already contain all the required fields (some of which
are currently not used by NM).

Tambet
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: [ANNOUNCE] ModemManager (for GSM and CDMA)

2008-08-01 Thread Tambet Ingo
On Fri, Aug 1, 2008 at 12:30 AM, Roberto Majadas
[EMAIL PROTECTED] wrote:
 I'm Roberto Majadas (mobile-manager developer). I was reading your spec
 about modem-manager. It's really interesting but i think you are trying
 to implement the same thing that we've implementated.

 Mobile Manager has a public and documentated Dbus API[1]. It support
 many features like pin/puk management, device and status information,
 plug  play support, device plugin system

 At the moment we support this devices :
  - Huawei
  - Option
  - Nozomi
  - Sierra
  - Novatel
  - Usb devices
  - Bluetooth devices

 And in the future we'll support more devices.

 About the programming language that should be written a daemon. Yeah C
 it's a good option in fact (i'm C programmer). But there are many, many,
 many situations easier to resolve using python in this case. The GPRS/3G
 devices sometimes are evils ;), belive me, i was working on it the last
 two years :). In this way MobileManager only depends of python,
 python-dbus and python-gobject (5-10Mb in memory)

 At the moment we use wdial to establish the ppp connection but we can
 change it and use NM ppp system.

 We are open to talk everything and we are open to colaborate ;)

Again, all this work has been done to support other modem driving
solutions (like mobile-manager). There were two missing pieces: It
wasn't possible to use other languages than C before, which is solved
by writing code to NetworkManager to talk to modems over dbus. Another
thing that was missing was the dbus API. Now that is defined as well
(but is open for changes). There are other (from mobile-manager)
interested parties and everyone has their own API. NM shouldn't try to
implement all of them, so we needed to define something that everyone
can target. ModemManager that I just announced is just one
implementer. As you say, it takes time to write a good one, and using
existing programs (which need to adapt the API changes, or just
provide another set of API to be integrated with NM) we have a
complete solution today.

The way to collaborate (to integrate with NM) is to try to implement
the API I've defined, and give me feedback on what should change
there.

Tambet
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: [ANNOUNCE] ModemManager (for GSM and CDMA)

2008-08-01 Thread Tambet Ingo
It looks like I did terrible job explaining _why_ I wrote
ModemManager. Let me try again.

Where were we before ModemManager.
The current state in NetworkManager 0.7 is that we have the absolute
minimum support for modems to claim that we support modems. There are
a couple of advanced solution out there (mobile-manager, vmc, umtsmon)
that do much better job and have many more features. Multiple people
contacted us asking if we could integrate their solution, each with
different API.

How to solve that?
Given that the existing mobile applications were written in other
languages than C, it became clear we need an out of process design for
modems. So DBus was chosen. The next obstacle is that each existing
solution has it's own API. The solution I chose for this is to define
a common API that NetworkManager uses and any project that wants to be
integrated, can implement two simple interfaces. I felt it was a
better choice than using any of the existing APIs to not make anyone
feel left out.

Why did I write ModemManager?
I'm no a genius and can't define API without trying to use it.
Therefore, I needed something to test on. ModemManager is very little
apart from the newly defined DBus interface plus the modem handling
code from NetworkManager. So it's not like I've made huge investments
trying to reimplement a wheel (or existing projects).

Where are we now?
I wrote the code for NetworkManager to support out of processes modem
handling API. It's in 'ModemManager' branch in the NetworkManager's
SVN tree. We have a clear answer to any project that wants to
integrate with NetworkManager.

Do I keep working on ModemManager?
Yes. As long as existing solution can be used with NetworkManager, I
feel like I've solved the main goal. If my pet project doesn't
succeed, there's no great loss. If it does, it gives me (and possibly
others) more choice. If there are two backends, one written in python
and one in C and both do the job for me, I'd choose the C one. Other
people, depending on their specific hardware, beliefs or what not,
might choose the other.

Does it make sense?
Tambet

On Thu, Jul 31, 2008 at 6:10 PM, Tambet Ingo [EMAIL PROTECTED] wrote:
 Announcing ModemManager.
 It's a standalone DBus system service to provide a common API to
 communicate with broadband modems. It is derived from the modem
 handling code from NetworkManager and in addition to DBus API, it adds
 more operations (scanning, signal quality, changing network mode,
 band, ...). It is easy to extend by having a plugin system to provide
 drivers for non standard operations. There is currently one plugin
 implemented for Huawei cards. It's fully functional and can be used as
 an example to write plugins for other cards (hint! hint!).

 Some QA

 Q: Where can I get it?
 A: git clone git://gitorious.org/modemmanager/mainline.git modemmanager

 Q: What does it have to do with NetworkManager?
 A: NetworkManager will use ModemManager instead of current basic code
 in the future.

 Q: Can I see it in action?
 A: Yes! I've ported NM to use it already, but haven't exposed any of
 the new functionality in the UI. The fully working branch can be
 downloaded from the NetworkManager SVN branch:

 svn co svn+ssh://[EMAIL PROTECTED]/svn/NetworkManager/branches/modem-manager
 NetworkManager-mm

 [or using anonymous svn]
 svn co http://svn.gnome.org/svn/NetworkManage/branches/modem-manager
 NetworkManager-mm

 Q: Why?
 A: There have been some requests to integrate some existing mobile
 programs with NM (vodafone, telefonica) and it's never been easier:
 All that needs to happen is to implement the same public DBus API and
 NM will use that instead.
 A2: The current modem handling code in NM is very basic, and
 supporting non standard operations and cards is pretty much impossible
 without total reorganization. Well, ModemManager is the
 reorganization.

 Q: You lied, it doesn't support signal monitoring while connected!
 A: No, it just means it's a non standard feature and needs a card
 specific plugin which isn't written for your card yet.

 Q: Is there any documentation available for it?
 A: Yes, pass a --with-docs argument to the configure and it'll create
 docs/spec.html which is the DBus API reference. There's also some
 information in the README file.

 Q: Can I write a plugin for my own card?
 A: Yes! Take a look at plugins/ directory to see the Huawei plugin, it
 should be pretty easy to write new ones based on that.

 Q: I think I've found a bug.
 A: Great! let me (tambet /at/ gmail.com for now) know. Extra points if
 you can provide a patch!

 Q: You API sucks!
 A: If there's something you'd like to change, either to add new
 methods or to modify the existing ones, let me know, it's not set in
 the stone.

 Tambet

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Network Manager fails to connect to a network when a static IP is in use

2008-08-01 Thread Sebastian
Hi,

I suppose I found a problem concerning Network Manager. I have a laptop
which connects via WIFI to a small home network. The laptop runs openSUSE
11.0:

 uname --all
Linux portatilgris 2.6.25.11-0.1-pae #1 SMP 2008-07-13 20:48:28 +0200 i686
i686 i386 GNU/Linux

WIFI hardware is Intel 3945ABG. Laptop make is HP 530.
Network Manager Applet ver. 0.7.0

The laptop needs a static IP in order to have access to a fileserver. When I
try to configure static IP address with a help of Gnome Network Manager
Applet, I cannot connect to the network then. It looks like the Network
Manager fails to write a proper DNS address into resolv file. To be more
specific, the file it writes is empty. The same happens when I try to
configure static IP address via Yast.
The only workaround of the problem I found is to choose ifup as a network
manager for the laptop.

It is also very annoying that it takes several second for the Network
Manager to connect to a network. It is very sad because previous version of
the Netwok Manager seems to connect much faster to the same network.

Is there any solution to the Network Manager problem or do I have to use
ifup?

Regards
Sebastian.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Network Manager fails to connect to a network when a static IP is in use

2008-08-01 Thread Tambet Ingo
On Fri, Aug 1, 2008 at 1:18 PM, Sebastian [EMAIL PROTECTED] wrote:
 The laptop needs a static IP in order to have access to a fileserver. When I
 try to configure static IP address with a help of Gnome Network Manager
 Applet, I cannot connect to the network then. It looks like the Network
 Manager fails to write a proper DNS address into resolv file. To be more
 specific, the file it writes is empty.

Could you please be more specific describing how you did that? Could
you try to create a new connection, fill in all the information there
and make a note of each step? Also, please attach the NM log file
(/var/log/NetworkManager) of the time when you try to activate the
newly created connection and fails to produce usable /etc/resolv.conf.

The same happens when I try to
 configure static IP address via Yast.

Static IP configuration from yast is in a terrible state. The main
cause of this is that when you configure DNS information in yast, it
only saves it in /etc/resolv.conf. That means that if you use NM with
DHCP on any device, the information filled with yast is lost forever.
There are hacky work arounds to make it possible, but if you use
NetworkManager on suse, I'd suggest to remove all the network device
configuration in yast and use NM exclusively. (and yes, we are trying
to improve the situation).

 It is also very annoying that it takes several second for the Network
 Manager to connect to a network. It is very sad because previous version of
 the Netwok Manager seems to connect much faster to the same network.

This is more likely caused by the new driver for your card (opensuse
10.3 had a different driver from 11.0).

Tambet
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Support for adding /etc/hosts entries

2008-08-01 Thread Michal Sawicz
It would be great if it would be possible to add hosts entries
to /etc/hosts based on the network we're connected to.

I'd see it as additional tab in the network configuration.

What do you think about that? Shouldn't be too difficult and really
usable.

Cheers
-- 
Michal Sawicz [EMAIL PROTECTED]

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Network Manager fails to connect to a network when a static IP is in use

2008-08-01 Thread Stuart Ward
Wouldent a better solution be to configure your DHCP server to give the
laptop the correct address rather than use static IP address on the laptop.

To do this create a subnet clause in dhcpd.conf with a:
hardware ethernet 0:0:c0:5d:bd:95;
Clause in it.

Then you dont need to change anything when you use the laptop somewhere
else.

-- Stuart Ward M +44 7782325143
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Network Manager fails to connect to a network when a static IP is in use

2008-08-01 Thread Sebastian
Thanks for the hint.
However, I need a static IP to have access to a NFS file server. DHCP server
is a hardware device (router/WIFI) and I have no idea how to make it keep
the same IP address for the laptop.

Besides, I thought this was exactly NetworkManager designed for. When I need
to connect my laptop to a network where a static IP is needed I just
configure my laptop with NetworkManager. Pure and simple, to make users'
life easier and make them happy running Linux.

I think I would wait until the problem will be successfully solved rather
than use any workarounds (The easiest would be just to switch to ifup). I
thought I found a bug which developers of NetworkManager may find
interesting. If so, I can provide any information to support them working on
the solution.

Please expect logs and answers to previous questions in my next post.

2008/8/1 Stuart Ward [EMAIL PROTECTED]

 Wouldent a better solution be to configure your DHCP server to give the
 laptop the correct address rather than use static IP address on the laptop.

 To do this create a subnet clause in dhcpd.conf with a:
 hardware ethernet 0:0:c0:5d:bd:95;
 Clause in it.

 Then you dont need to change anything when you use the laptop somewhere
 else.

 -- Stuart Ward M +44 7782325143



___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Support for adding /etc/hosts entries

2008-08-01 Thread Fred Welland
That would be cool.

I use about 4 different networks routinely.   2 of them use vanilla
/etc/hosts or wins.   I resort to just memorizing ip numbers.and some
times -- since hostnames are distinct -- I just put everything in my
/etc/hosts

It would be cool if the VPN stuff had this too -- I do use 1 cisco VPN and
setting up etc hosts for that would be cool too.


On Fri, Aug 1, 2008 at 4:13 AM, Michal Sawicz [EMAIL PROTECTED] wrote:

 It would be great if it would be possible to add hosts entries
 to /etc/hosts based on the network we're connected to.

 I'd see it as additional tab in the network configuration.

 What do you think about that? Shouldn't be too difficult and really
 usable.

 Cheers
 --
 Michal Sawicz [EMAIL PROTECTED]

 ___
 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: Support for adding /etc/hosts entries

2008-08-01 Thread Dan Williams
On Fri, 2008-08-01 at 10:13 +0200, Michal Sawicz wrote:
 It would be great if it would be possible to add hosts entries
 to /etc/hosts based on the network we're connected to.
 
 I'd see it as additional tab in the network configuration.
 
 What do you think about that? Shouldn't be too difficult and really
 usable.

Ideally this could be handled with a dispatcher script that distros
could ship if they wanted; we do need to make the dispatcher export a
few more options so that it's trivial to match up the connection that
got activated with the dispatcher event.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


ip4 setting method name changes

2008-08-01 Thread Dan Williams
Hi,

As of svn 3882, I've changed two of the IPv4 'method' names:

dhcp - auto
autoip - link-local

Since both VPN and PPP connections can have IPv4 settings, the term
'dhcp' doesn't really make sense here.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Network Manager fails to connect to a network when a static IP is in use

2008-08-01 Thread Sebastian
2008/8/1 Dan Williams [EMAIL PROTECTED]

 [cut]

 Happiness usually doesn't involve manual network configuration and NFS
 though :)


No, it does not, indeed. ;) I am sure we will make it happen in the
foreseeable future :)

In any case, NM 0.7 should handle static IPs fine.  For 0.6.6, it
 depends on whether your distro has written a backend correctly.


Bad news:
Name: NetworkManager
Version: 0.7.0.r3685-7.1
Arch: i586

It looks like my NM 0.7 does not handle static IP correctly. Do you think it
can be an openSUSE problem? Do you recommend me letting openSUSE team know
about that?

Sebastian.


 Dan

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Broken OpenVPN

2008-08-01 Thread Nathaniel McCallum
So I upgraded to the stuff in F9 updates-testing and it broke NM-OpenVPN.
Particularly, the problem is routing.

Routing before the upgrade:
$ route -n | grep tun
10.254.0.1  10.254.0.9  255.255.255.255 UGH   0  00 tun0
10.254.0.9  0.0.0.0 255.255.255.255 UH0  00 tun0

Routing after the upgrade:
$ route -n | grep tun
10.254.0.1  10.254.0.9  255.255.255.255 UGH   0  00 tun0
10.254.0.0  0.0.0.0 255.255.255.0   U 0  00 tun0

Interface info:
$ ifconfig tun0
tun0  Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
  inet addr:10.254.0.10  P-t-P:10.254.0.9  Mask:255.255.255.0
  UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
  RX packets:19 errors:0 dropped:0 overruns:0 frame:0
  TX packets:171 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:100
  RX bytes:2643 (2.5 KiB)  TX bytes:11045 (10.7 KiB)
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Support for adding /etc/hosts entries

2008-08-01 Thread Brett Johnson
On Fri, 2008-08-01 at 10:13 +0200, Michal Sawicz wrote:
 It would be great if it would be possible to add hosts entries
 to /etc/hosts based on the network we're connected to.

I currently do this with a script in /etc/dhcp3/dhclient-exit-hooks.d/
It just checks for the appropriate domain name in $new_domain_name,
and copies/links an appropriate /etc/hosts file based on that.

Not saying that a GUI to do it via NM wouldn't be nice, just that it's
possible now w/out it.

-- 
Brett Johnson [EMAIL PROTECTED]
 Irritated at Outlook's plain-text quoting?
 http://home.in.tum.de/~jain/software/outlook-quotefix/

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list