IP aliasing and open ports

[ricain]

Hello everyone,
First of all le me wish a happy new year to all of you linux lovers out there !

Now, time for my problem I'm currently hosting a couple of gameservers on one of my machines (Quad Core, 4G RAM, Debian Etch, 2.6.22-cks1, 1GB Switch) and I'm running into lag issues, let me explain my network config:

eth0

Lien encap:Ethernet HWaddr 00:30:48:97:62:CC
inet adr:93.184.36.228 Bcast:93.184.36.255 Masque:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3071778 errors:0 dropped:0 overruns:0 frame:0
TX packets:35611800 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:204166163 (194.7 MiB) TX bytes:435472927 (415.2 MiB)
Adresse de base:0x4000 Mémoire:d0100000-d0120000

eth0:1

Lien encap:Ethernet HWaddr 00:30:48:97:62:CC
inet adr:93.184.38.236 Bcast:93.184.39.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Adresse de base:0x4000 Mémoire:d0100000-d0120000

eth0:2

Lien encap:Ethernet HWaddr 00:30:48:97:62:CC
inet adr:93.184.38.237 Bcast:93.184.38.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Adresse de base:0x4000 Mémoire:d0100000-d0120000

eth0:3

Lien encap:Ethernet HWaddr 00:30:48:97:62:CC
inet adr:93.184.38.238 Bcast:93.184.38.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Adresse de base:0x4000 Mémoire:d0100000-d0120000

eth0:4

Lien encap:Ethernet HWaddr 00:30:48:97:62:CC
inet adr:93.184.38.239 Bcast:93.184.38.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Adresse de base:0x4000 Mémoire:d0100000-d0120000

eth1

Lien encap:Ethernet HWaddr 00:30:48:97:62:CD
inet adr:192.168.0.35 Bcast:192.168.0.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27616304 errors:0 dropped:0 overruns:0 frame:0
TX packets:927336 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:3083749833 (2.8 GiB) TX bytes:216007251 (206.0 MiB)
Adresse de base:0x5000 Mémoire:d0200000-d0220000

lo

Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7732 errors:0 dropped:0 overruns:0 frame:0
TX packets:7732 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:140360 (137.0 KiB) TX bytes:140360 (137.0 KiB)

The thing is, my gameservers all use port 27015 (eth0:1, eth0:2, eth0:3 and eth0:4), eth0 is my main IP (used to access the machine from the net by ssh) and eth1 is my internal network used for file transfers to and from a filer (yes my machine has two integrated ethernet ports).

My question is, can the fact that they all use port 27015 cause a problem (like lags and freezes during gameplay) ? Is there another way to acheive this with better results or do I simply need to have a different port for each gameservers/eth0:1-4 ?

Thanks in advance for the time taken to read and answer
Kind Regards to everyone,
Ricain

[Lazydog]

One of your bottlenecks is going to be your provider.

What does vmstat show?

[ricain]

Hi !

ns34:~# vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
1 0 0 3198708 116088 241664 0 0 0 1 18 19 1 0 99 0

I get my traffic from equinix / cogent, as I said I've got 1GB connexion and never go above 2Mb / machine average ...

Thanks a lot for the help

PS: this might be more helpfull: the gameservers on each eth: constantly send info back to the filer in the console.
So basically, I launch a gameserver on the machine from an nfsv4 mount on the filer (this works with eth1), when a user connects to the gameserver, he uses the eth: alias and the gameserver sends back info through the eth1 interface to the filer but through the eth: alias to the user.

[Lazydog]

I get my traffic from equinix / cogent, as I said I've got 1GB connexion and never go above 2Mb / machine average ...

I don't believe you have a 1Gig internet connection. That might be the connection from your box to your local network but not to your Internet provider.
This is what you need to find out, what is the true connection to the internet.