This site covers Linux networking specific topics. It does not cover general networking questions, these are covered under the more general Wikipedia Computer Networks . See the External Links section for other useful resources.
Device Performance Enhancements
To learn more about Asaba Group Holdings  or our portfolio companies , please call us. Alternatively, please visit any portfolio company website . Visit our Portfolio Companies page for links to each company's website.
Asaba Group Holdings
220 North Main Street
Natick, MA 01760
+1 (508) 655-8100 Telephone
+1 (508) 655-1955 Fax
Hi, I'm working with Nanomind in Eclipse and I have some problems .Currently I added the libraries Nanomind and libraries Arm, but the errors continue. These are the errors that I have currently. You have any idea what library I should add or do to make it work.
List of errors:
Please provide me link for netem download
i hope this is the right place to ask....
i'm try to use bridge on kernel 2.6.30 for the following reason:
i need to realize a litle beat complex network interconnecting a few linux embedded box on wich only one ethernet interface is available for each box. The unique eth is phisically connectd with one port of embedde 5 port switch that is used only to provide multiple phisical port for connection.
Join the kernel backports mailing list:
Introduce yourself there and express your interest if you like. You can either chime in with your own ideas or pick one of the ones below.
We're on Freenode:
Rami Rosen website 
The wiki moved to:
XIMETA (ndas) support 
at ximeta.com there are ancient linux driver files for ndas technology. ndas are network enclosures/HD that connect your harddrives to the network via ethernet. they do not use tcp/ip and have their own protocol (lpx) that ximeta owns. ximeta is not willing to update the drivers on the website. I have digged around for months trying to help people stuck with ndas devices. most of them are dual booting with windows to get around the problem but why should us mighty linux users have to settle for this work around?
Here are the latest test results with different chipsets on the alx/atl1c Ethernet driver.
Kernel 3.3.0+ / alx
We strongly encourage all hardware vendors to make their programming guides and register specifications publicly available. The following documentation is available for free public download.
alx Ethernet driver
This is the home page of the Linux Qualcomm Atheros alx Ethernet driver.
Updated on March 05, 2013:
Linux Kernel Ethernet
This page documents Ethernet drivers on the Linux kernel. Typically Ethernet drivers are documented through the Documentation/ section of the kernel. This page is for those drivers that choose to document themselves through a wiki rather than plain text ASCII files. This follows the tradition of documentation followed by the wireless subsystem .
Here is the list of our wiki-documented Ethernet drivers. alx - Qualcomm Atheros (QCA) Ethernet driver.
RPM commands 
RPM package is a powerful utility to manage the software in all major Linux distributions. RPMs can be used to,
- Install packages
- Remove packages
- Upgrade packages
- Verify packages
Here are some useful command to manage RPM packages,
1. Getting detailed information about the package httpd
rpm -qi httpd
/etc/net is a new way to configure networks. It is designed to let you use all modern Linux network technologies in a convenient way. The best way to learn /etc/net is to look at examples, which I will try to provide for most technologies mentioned at LinuxNet pages.
You can find more information at the project's home page  and freshmeat page .
I created a bridge that include eth0 and the bridge in preparation to setup Qemu with a bridged interace to the network.
ifconfig eth0 0.0.0.0 promisc up
brctl addbr br
ifconfig br 172.16.2.1 netmask 255.255.255.0 up
I have echoed 1 in /proc/sys/net/ipv4/conf/eth0/proxy_arp
I finish setting this up and evrything is fine. I ping the default gateway of the machine in the network attached to the eth0 interface and I get excellent replies.
Here is the problem, I vnc to 172.16.2.1 and once I do that, I loose communication with 172.16.2.1.