First off, I want to point out that I am pretty new to linux.. I can find my way around but some specifics are a little blurry. Now, with that said, onto the problem. I recently migrated my Windows gameserver over to Debian linux, since a test run of it ran MUCH better than Windows. After getting everything setup, it seemed to be running pretty well. Recently I've been noticing some weird lag issues, but didn't get to look into the server as much as I would have liked. While I was checking into another problem, I noticed something strange in ifconfig:
Albeit this is just after a server restart, you can still catch the drift of the problem: receiving traffic is fine (the gameservers get all the traffic incoming onto the correct IP's) but outgoing traffic is ALL going through eth0! I uninstalled firestarter and tried to flush the iptables, but that did nothing. I looked around at several different iptables scripts, but they were almost all directed at NAT or masquerading, as this seems to be a common issue. But I have two cards, no NAT at all. I just want to allow a few ports to both cards and have them transmit on their respective cards! Can anyone help me out on this? I'm really quite stumped at this point as to why it's transmitting only on eth0.

Hi TBKDan,

can you dump your routing table (try route -n at the command line)

Dylan

*yawns and then runs to take a shower to make class*

Hi TBKDan,

The routing table tells me that your default route is out through eth0 via the gateway 129.21.112.126.

This means that all traffic not for the local network will be sent out through eth0, regardless of which interface it came in on, unless you can find a way to bind a process to a specific interface.



It also looks to me like all three of your network interfaces are on the same network - is there any reason for this?

Dylan

Yeah, I was just looking at it now that I woke up and saw that it was all going through eth0. I'm on a college network and the more network cards, the more bandwidth Is there any way I can get it to receive and send on their respective interfaces?

Am I right in thinking you're in college accomodation, and you've plugged all three network interfaces into an ethernet switch that is plugged into a single wall port for the college network? Or do you have multiple wall ports in your room?
If the former is the case then the bandwidth will be limited to that supplied to the wall port (I'd estimate that at 100Mb/s).
Also worth knowing is the speed of the backbone in the switch (if you have one), and what is the speed of the link that the college supplies to your building?

Usually the way to achieve more bandwidth is to bond (or aggregate) multiple interfaces together - but that has to be done at both ends, and I doubt the IT staff at the college will agree to bonding, or even if your network cards will support it! (usually an advanced feature).

Also worth asking is - can your pc handle the bandwidth? A lot of machines don't utilise all the bandwidth simply because either the server or client of the ethernet link is slower than the network.

Have you checked your network traffic to see if you're even using what you've got? Try running MRTG or Cacti and look at the graphs to see how busy your network interfaces are.

If you've got a 100-Base-Tx card then that is usually enough for all but the most powerful servers.

Saying all that, there may be a project for load balancing network traffic available for linux - try freshmeat or sourceforge.

HTH

Dylan

My college, although it has assloads of bandwidth, only gives roughly 100kb/s per IP, hence why I have the multiple NIC. I'm nowhere near the card nor switches capacity (12 port into one wall jack), but I'm probably pushing the limit that the school allows me I need to get out of the residence halls... WiFi and other places I've uploaded at 3mb/s lol. But that's why I have so many NIC though. Mainly two are used at this time, used to be more but I changed things around.

Ok, I understand what is happening (the traffic is coming in on the right addresses, but it is leaving through one because route tells it to. And the fact that they are both connected to the same gateway is probably going to be a bitch So.. are there any ways to tell route to route it so that, say if it came in on eth1 it will leave on eth1?

Maybe this would be better off being moved to the Networking section? I started out thinking that it was going to be a firewall/iptables issue, now it seems like routing :P

EDIT: I made a new topic in the networking section so it will get the exposure it needs http://www.linuxquestions.org/questi...60#post2001160 Thanks for the help you have given me so far.