Hi all,
On 11.01.2013 11:07, Bach, Pascal wrote:
Hello
I'm looking to use connman as the network manager for a small NAS
device.
The device could have a wireless adapter, and one or two ethernet
adapters. I'd like to be able to show the user all the network
interfaces
on the box, and allow them to configure them with or without a network
link. Sure, I can use getifaddrs() or similar to list all the
interfaces,
but since connman is controlling them already, and I can use connman
dbus
calls for all other network tasks, it would be nice to stick with that
approach for everything.
Configuring an ethernet device with no link may seem pointless, but it
can
be useful for situations like if you are preparing to move a network-
only
(headless) device to a different network with no DHCP server. In that
case, you would probably want to configure your other, disconnected
interface for the network which you plan to move your device to.
I'd be interested in a similar scenario. Connman is running on a device with
display that shows some environmental information to the user. The system is
usually installed by an installation engineer. However during the installation
the network infrastructure is often not available. So it would be good if the
user could already configure the device to his desire even without the network,
this way when everything goes online the system is already mostly configured.
I also noticed that if I don't show the Ethernet interface if the network is
not plugged in the user gets confused.
Regards
Pascal
One option would be implement provisioning support i.e., .config file
support for ethernet devices. Currently only wifi is supported in
.config files. I just sent a proposal for VPN provisioning support to
the mailing list.
Cheers,
Jukka
_______________________________________________
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
