MEPIS 8 Network Assistant

From MEPIS Documentation Wiki

Jump to: navigation, search

Configure your network access with MEPIS Network Assistant (command line: mnetwork), by clicking KMenu --> Internet --> Connection --> MEPIS Network Assistant. The interface has five tabs. Be sure to click Apply when you make a change on any tab (you will see a warning if you don't).


General tab

  • Interface status. This panel at the top of the screen displays the active interfaces and indicates their status following an obvious color code. If you hover your cursor over any interface you will see details on its current state.
  • Interface Configuration Mode:
    • The automatic mode using KnetworkManager may work on some systems, and is preferable for laptops that often switch access points. Click the Automatic radio button, then click Apply. Remember to start the KNetworkmanager application after choosing this option by clicking Kmenu --> Internet --> Network Manager. For details, see Networkmanager.
    • The manual mode works better for many users, especially when using the same access point all the time. Click that radio button to activate it and, if necessary, then Apply. If the Knetworkmanager icon is in the system tray of the Panel at the
    bottom right of the screen, right-click it to quit so that it does not interfere with the manual mode.
  • Ndiswrapper and Broadcom Preference:
    • On the use of Ndiswrapper to allow the use of Windows drivers in Linux, see Using Ndiswrapper
    • Select the Broadcom wl driver for newer cards with the chipset BCM4310 to 4312, BCM 4322, and BCM4328.
    • Select the Broadcom b43 and b44 kernel drivers for older chipsets such as BCM4306.
  • Configure Domain Name Service Source: allows you to adjust how DNS is set.
  • Network Control: permits restarting the network when changes have been made. In some cases, you may have to reboot for the changes to take effect.

Wireless tab

  • If you are using wireless for internet access, note which interface (e.g. wlan0) you're using.
  • Enter the name of your network (SSID), if you know it; you can also try any or default. To see what networks are available, click Scan Access Points. All found will show up in the SSID box along with an indication of their strength, and you can select the one you want. Rarely you may need to adjust the frequency (channel) in order to avoid conflict with other devices using the 2.4 GHz band.
  • Select your encryption mode (see WEP and WPA), if any, and enter the key. Click Apply.

Interfaces tab

  • Use the pull-down menu to get to your interface, then click Start at boot. If you don't know which interface name you should use, open a terminal, become root, and type:
  • Uncheck Start at boot for any other interfaces you will not be using.
  • Check the Start/Restart on Apply box and then Apply at the bottom to quickly restart the interface.
  • If you need to, you can configure static IP settings.
  • Click Apply then OK. You may have to reboot for the changes to take effect, though usually that is not necessary. On the LiveCD, go back instead to the General tab and click Stop Network, then Re/Start Network.

Troubleshooting tab

  • Hardware Clicking on Scan hardware will return a detailed description of your network cards and chipsets. Be sure to report this information when seeking help.
  • Associated drivers
    • Linux drivers. Any drivers associated with your wireless hardware will be listed here.
    • Windows drivers. This panel allows you to see associated Windows drivers for use with Ndiswrapper, as well as to add or remove a driver, or even to blacklist Ndiswrapper if it is interfering with a Linux driver you want to use.

Diagnosis tab

This tab provides easy access to network diagnostic problems using well-established tools.

  • Ping is used to send small data packets to another network host as a basic test for connectivity. It will test your connection to any IP address or hostname you give it; try something like to see how it works. Ten packets is often enough, but you can select any number by using the arrows. Consult Ping on how to read and use the output.
  • Traceroute shows you the route over the network between two systems, listing all the intermediate routers a connection must pass through ("hops") to get to its destination. It can help you determine why your connections to a given server might be poor, and can often help you figure out where exactly the problem is. Try something like to see how it works. Ten hops is often enough, but you can select any number by using the arrows. Consult Traceroute on how to read and use the output.
Personal tools