GNOME.org
 

[gnomeweb-wml] NetworkManager: add various links to the wiki

commit 13576213abea645fcbd979252ca03fffbdfdc0fa
Author: Dan Williams <dcbw redhat com>
Date:   Tue Jan 19 21:52:46 2010 -0800

    NetworkManager: add various links to the wiki

 .../NetworkManager/admins/index.html               |    3 ++
 .../NetworkManager/developers/index.html           |    2 +-
 projects.gnome.org/NetworkManager/index.html       |    2 +-
 projects.gnome.org/NetworkManager/users/index.html |   22 ++++---------------
 4 files changed, 10 insertions(+), 19 deletions(-)
---
diff --git a/projects.gnome.org/NetworkManager/admins/index.html b/projects.gnome.org/NetworkManager/admins/index.html
index 5ec6366..7cd616c 100644
--- a/projects.gnome.org/NetworkManager/admins/index.html
+++ b/projects.gnome.org/NetworkManager/admins/index.html
@@ -16,6 +16,9 @@
 	</div>
 
 	<h1>Administrators</h1>
+	<h2>Architecture</h2>
+	The <a href="http://live.gnome.org/NetworkManagerConfiguration";>wiki</a> has more information about how the the configuration of NetworkManager works.  Also be sure to check out the information on <a href="http://live.gnome.org/NetworkManager/SystemSettings";>system settings</a> to learn how NetworkManager integrates into your distribution's normal configuration system.
+
 	<h2>Deployment</h2>
 	<p>NetworkManager is designed to be fully automatic by default, but offer a high level of manual control when required.  To use NetworkManager, its service must be started.  Simply start the <kbd>NetworkManager</kbd> service.  NetworkManager ships with initscripts to do this for most distributions.  If your distribution is not supported, we would appreciate patches to include support for your distribution of choice.  NetworkManager will then automatically start other services as it requires them (nm-system-settings for system-wide connections, wpa_supplicant for WPA and 802.1x connections, and pppd for mobile broadband).</p>
 
diff --git a/projects.gnome.org/NetworkManager/developers/index.html b/projects.gnome.org/NetworkManager/developers/index.html
index 341aff1..d73494c 100644
--- a/projects.gnome.org/NetworkManager/developers/index.html
+++ b/projects.gnome.org/NetworkManager/developers/index.html
@@ -21,7 +21,7 @@
 	<h2>Or you want to hack on NetworkManager?</h2>
 	<p>First, you should probably consider joining the mailing list as there is a lot of useful information there from other NM hackers: <a 
 href="http://mail.gnome.org/mailman/listinfo/networkmanager-list";>http://mail.gnome.org/mailman/listinfo/networkmanager-list</a>.</p>
-	<p>Second, read the <a href="design_goals.html">Design Goals</a> of NetworkManager to get an idea of why things work the way they do.</p>
+	<p>Second, read the <a href="design_goals.html">Design Goals</a> of NetworkManager to get an idea of why things work the way they do, and check <a href="http://live.gnome.org/NetworkManager";>out the wiki</a> for more information on the architecture.</p>
 	<p>To checkout and build the latest, hottest sources of the core NetworkManager daemon from git:<br>
 	<code>
 		<kbd>git clone git://anongit.freedesktop.org/NetworkManager/NetworkManager.git</kbd><br>
diff --git a/projects.gnome.org/NetworkManager/index.html b/projects.gnome.org/NetworkManager/index.html
index e65a309..69dc9a9 100644
--- a/projects.gnome.org/NetworkManager/index.html
+++ b/projects.gnome.org/NetworkManager/index.html
@@ -34,7 +34,7 @@
 	<p>Using the awesome power and flexibility of <a href="http://www.freedesktop.org/Software/dbus";>dbus</a> and <a href="http://www.freedesktop.org/Software/hal";>hal</a>, NetworkManager provides facilities for other applications like browsers, email clients, or system services to be aware of the network's state and adjust their operation accordingly.  If you're not online, your computer shouldn't try to update itself, and when you're on a mobile broadband network, it probably shouldn't either.  With NetworkManager, software knows where it is, and how it's connected.</p>
 
 	<h2>More Information</h2>
-	<p>Read the NetworkManager <a href="http://mail.gnome.org/mailman/listinfo/networkmanager-list";>mailing list archives</a>, or subscribe to the NetworkManager mailing list.</p>
+	<p>Read the NetworkManager <a href="http://mail.gnome.org/mailman/listinfo/networkmanager-list";>mailing list archives</a>, or subscribe to the NetworkManager mailing list, or checkout the <a href="http://live.gnome.org/NetworkManager";>NetworkManager wiki</a>.</p>
 
 </div>
 <div id="copyright">
diff --git a/projects.gnome.org/NetworkManager/users/index.html b/projects.gnome.org/NetworkManager/users/index.html
index a7285a5..09ef318 100644
--- a/projects.gnome.org/NetworkManager/users/index.html
+++ b/projects.gnome.org/NetworkManager/users/index.html
@@ -16,30 +16,18 @@
 	</div>
 
 	<h2>Using NetworkManager</h2>
-	<p>Once the NetworkManager service is started (which should have been done automatically for you!), and the applet is running (which is also automatic when you log in), using NetworkManager is a piece of cake.  For information on how to get the service started, see the <a href="../admins/">administrators</a> page.  NetworkManager will scan for available network hardware and wireless networks.  To view the list of available network connections, simply click on the applet.</p> 
+	<p>Once the NetworkManager service is started (which should have been done automatically for you!), and the applet is running (which is also automatic when you log in), using NetworkManager is a piece of cake.  For information on how to get the service started, see the <a href="../admins/">administrators</a> page.  NetworkManager will scan for available network hardware and wireless networks.  To view the list of available network connections, simply click on the applet.</p>
 	<p>NetworkManager will automatically connect to networks you have connected to before, but you will need to manually connect at least the first time.  Simply select the network or device from the list, and NetworkManager will attempt to connect, asking you if more information is required.  If the connection fails, your keys or passphrases might be wrong, so NetworkManager will ask you for them again.  Make sure they are correct, and just hit "Connect..." again.</p>
 	<p>To switch network connections, simply choose another one from the applet's menu.</p>
 
 	<h2>Supported Wireless Hardware</h2>
 	<p>Drivers that are included in the upstream Linux kernel work best with NetworkManager, because they have been reviewed and vetted by many kernel developers.  If the driver isn't upstream, work with the provider of the driver to clean it up and submit it for inclusion into the kernel.  If the driver is not completely open-source (ex. ndiswrapper, madwifi, and Broadcom's wl.o), then driver bugs cannot be fixed quickly and easily, and NetworkManager cannot be guaranteed to work with it.  Make sure the driver your OS uses are top-quality.<p>
 
-	<h2>Bugs</h2>
-	<p>If you should find a bug, please <a href="http://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager";>report it to us in GNOME Bugzilla</a> so we know what to fix!  Your bug reports help us continually improve the quality of the product.</p>
+	<h2>Supported Mobile Broadband Hardware</h2>
+	<p>NetworkManager uses ModemManager for mobile broadband device support.  A partial listing of <a href="http://live.gnome.org/NetworkManager/MobileBroadband";>supported mobile broadband hardware</a> is on the wiki.  If your hardware is not on the list it's likely to be supported, but many devices first appear in a "fake driver CD" mode and must be changed to modem mode using a tool like <a href="http://www.draisberghof.de/usb_modeswitch/";>usb_modeswitch</a>.</p>
 
-	<p>If you have trouble connecting to a specific network, attaching logs to the bug report is a great way to get faster help.  Most distributions direct NetworkManager log output to /var/log/messages or /var/log/daemon.log; look in those two files for lines like:
-	<code><kbd>
-		NetworkManager: &lt;info&gt;  starting...<br>
-		NetworkManager: &lt;info&gt;  Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch<br>
-		NetworkManager: &lt;info&gt;  eth0: driver is 'e1000'.<br>
-		NetworkManager: &lt;info&gt;  Found new Ethernet device 'eth0'.<br>
-		NetworkManager: &lt;info&gt;  (eth0): exported as /org/freedesktop/Hal/devices/net_00_16_aa_bb_cc_dd<br>
-		NetworkManager: &lt;info&gt;  eth2: driver is 'ipw2200'.<br>
-		NetworkManager: &lt;info&gt;  eth2: driver supports SSID scans (scan_capa 0x21).<br>
-		NetworkManager: &lt;info&gt;  Found new 802.11 WiFi device 'eth2'.<br>
-		NetworkManager: &lt;info&gt;  (eth2): exported as /org/freedesktop/Hal/devices/net_00_16_dd_cc_bb_aa<br>
-	</code>
-	And attach the file to the bug report along with the time the problem ocurred, so that the developers can isolate the issue.</p>
-	<p>If you're familiar with <a href="http://w1.fi/wpa_supplicant/";>wpa_supplicant</a> configuration, a great way to debug wifi connection issues is to stop the NetworkManager service, kill wpa_supplicant, create a wpa_supplicant config that works with a network where NetworkManager does not, and attach that wpa_supplicant config file, along with the output of wpa_supplicant when launched with the "-dddt" flags, to the bug report.</p>
+	<h2>Bugs</h2>
+	<p>Should find a bug, please <a href="http://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager";>report it to us in GNOME Bugzilla</a> so we know what to fix!  To help get your bug fixed faster you can follow some of the <a href="http://live.gnome.org/NetworkManager/Debugging";>debugging tips</a> on the wiki. Your bug reports help us continually improve the quality of the product.</p>
 
 </div>
 <div id="copyright">
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]