Difference between revisions of "Development/Tutorials/Solid/Network Management"

Jump to: navigation, search
(Prerequisites: style)
m (moved Development/Tutorials/Solid Network Tutorial to Development/Tutorials/Solid/Network Management: Make it easier to link to, and organize the Solid section)
 
(4 intermediate revisions by 3 users not shown)
Line 13: Line 13:
 
Our first program is going to be the most common use of the network manager, checking the network status of the system.  This will be useful for programs like KMail which will be able to see if the computer has network connectivity.  It would then be able to judge whether or not it should check for mail.
 
Our first program is going to be the most common use of the network manager, checking the network status of the system.  This will be useful for programs like KMail which will be able to see if the computer has network connectivity.  It would then be able to judge whether or not it should check for mail.
  
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
//get a reference to the network manager
+
Solid::NetworkManager &netmanager = Solid::NetworkManager::self();
+
 
+
 
//test to see if networking is enabled on the system
 
//test to see if networking is enabled on the system
if(netmanager.isNetworkingEnabled() )
+
if(Solid::Networking::status() == Solid::Networking::Connected)
 
{
 
{
     kDebug() << "Networking is enabled. Feel free to go online!"
+
     kDebug() << "Networking is enabled. Feel free to go online!";
            << endl;
+
 
}
 
}
 
else
 
else
 
{
 
{
     kDebug() << "Network not available." << endl;
+
     kDebug() << "Network not available.";
 
}
 
}
</code>
+
</syntaxhighlight>
  
As of 28DEC2006 there are no signals that report a change in the network status so polling is required.
+
To get informed about changes in network connectivity you'll have to connect to the events of Solid::Networking::notifier().
  
 
== Cross-referencing devices to interfaces ==
 
== Cross-referencing devices to interfaces ==
 
It is no longer required for the user to figure out which device corresponds to a given interface as the NetworkManager has the ability to cross-reference a device to its interface name. This can be done with the following code:
 
It is no longer required for the user to figure out which device corresponds to a given interface as the NetworkManager has the ability to cross-reference a device to its interface name. This can be done with the following code:
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
 
//get a reference to the device manager
 
//get a reference to the device manager
 
Solid::DeviceManager &manager = Solid::DeviceManager::self();
 
Solid::DeviceManager &manager = Solid::DeviceManager::self();
Line 43: Line 39:
 
if(netlist.empty() )
 
if(netlist.empty() )
 
{
 
{
     kDebug() << "No network devices found!" << endl;
+
     kDebug() << "No network devices found!";
 
}
 
}
 
      
 
      
Line 51: Line 47:
 
if(!netdev)
 
if(!netdev)
 
{
 
{
     kDebug() << "Device could not be converted. There is a bug." << endl;
+
     kDebug() << "Device could not be converted. There is a bug.";
 
     return 0;
 
     return 0;
 
}
 
}
 
      
 
      
kDebug() << "The iface of " << device.udi() << " is " << netdev->ifaceName() << endl;
+
kDebug() << "The iface of" << device.udi() << "is" << netdev->ifaceName();
</code>
+
</syntaxhighlight>
  
 
== Initializing devices ==
 
== Initializing devices ==

Latest revision as of 14:29, 30 September 2011

Contents

[edit] Prerequisites

This tutorial assumes that you have read Introduction to Solid and are familiar with the Solid hardware framework. If you want to use any backends other than the fake backends provided in kdelibs, you will need to compile and install kdebase.

[edit] Features of the Solid Network Manager

The Solid Network Manager provides many useful features that have, up until now, been missing from KDE. These include:

  • Notification of connection state. This allows applications to know when there is no internet connection, allowing them to not bother the user with "Connection Error" messages
  • Notification of wireless connection state.
  • Access to network devices and interfaces.
  • Device <-> interface cross-referencing.

Note that there is a difference between the devices and the interfaces. The device is a representation of the device itself and all the things that normally are associated with a PCI/USB device such as: bus address, IRQ, etc. The interface is the name of the device e.g. 'eth0' which is used for commands like 'ifconfig.'

[edit] Let's begin

Our first program is going to be the most common use of the network manager, checking the network status of the system. This will be useful for programs like KMail which will be able to see if the computer has network connectivity. It would then be able to judge whether or not it should check for mail.

//test to see if networking is enabled on the system
if(Solid::Networking::status() == Solid::Networking::Connected)
{
    kDebug() << "Networking is enabled. Feel free to go online!";
}
else
{
    kDebug() << "Network not available.";
}

To get informed about changes in network connectivity you'll have to connect to the events of Solid::Networking::notifier().

[edit] Cross-referencing devices to interfaces

It is no longer required for the user to figure out which device corresponds to a given interface as the NetworkManager has the ability to cross-reference a device to its interface name. This can be done with the following code:

//get a reference to the device manager
Solid::DeviceManager &manager = Solid::DeviceManager::self();
 
//get a network device
Solid::DeviceList netlist = manager.findDevicesFromQuery(Solid::Capability::NetworkHw, QString());
 
//check to see if no network devices were found
if(netlist.empty() )
{
    kDebug() << "No network devices found!";
}
 
Solid::Device device = netlist[0];
Solid::NetworkHw *netdev = device.as<Solid::NetworkHw>();
//keep the program from crashing in the event that there's a bug in solid
if(!netdev)
{
    kDebug() << "Device could not be converted. There is a bug.";
    return 0;
}
 
kDebug() << "The iface of" << device.udi() << "is" << netdev->ifaceName();

[edit] Initializing devices

[edit] Encryption

[edit] Putting it all together


This page was last modified on 30 September 2011, at 14:29. This page has been accessed 15,123 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal