Maybe something is awry in my aliasing.  I'm human, maybe I forgot 
something when I created them.

netstat -an|grep 27015 produces this:

tcp        0      0 74.208.167.224:27015        
0.0.0.0:*                   LISTEN
udp        0      0 0.0.0.0:27015               0.0.0.0:*

ifconfig produces:

eth0      Link encap:Ethernet  HWaddr 00:19:99:44:57:42
          inet addr:74.208.167.224  Bcast:74.208.167.224  
Mask:255.255.255.255
          inet6 addr: fe80::219:99ff:fe44:5742/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:160534 errors:0 dropped:0 overruns:0 frame:0
          TX packets:182778 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11926761 (11.3 MiB)  TX bytes:68233167 (65.0 MiB)
          Interrupt:20

eth0:0    Link encap:Ethernet  HWaddr 00:19:99:44:57:42
          inet addr:74.208.147.254  Bcast:74.208.147.254  
Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:20

eth0:1    Link encap:Ethernet  HWaddr 00:19:99:44:57:42
          inet addr:74.208.147.253  Bcast:74.208.147.253  
Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:20

eth0:2    Link encap:Ethernet  HWaddr 00:19:99:44:57:42
          inet addr:74.208.148.69  Bcast:74.208.148.69  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:20

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1546 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1546 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:324012 (316.4 KiB)  TX bytes:324012 (316.4 KiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

>
> Message: 1
> Date: Tue, 24 Mar 2009 09:13:41 -0400
> From: "David A. Parker" <dpar...@utica.edu>
> Subject: Re: [hlds_linux] Multihomed Port Issues
> To: Half-Life dedicated Linux server mailing list
>       <hlds_linux@list.valvesoftware.com>
> Message-ID: <49c8dc85.7080...@utica.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Yeah, this works fine for me in both Debian and CentOS.  I really think 
> the cause of the OP's problem is a simple -ip vs. +ip issue.  I was 
> using -ip to specify the IP at one point and I had the exact same 
> problem: the first instance of srcds I started would get port 27015, but 
> the second would get 27016, the next would get 27017, etc.  I changed my 
> startup scripts to use +ip and the problem was solved.
>
>      - Dave
>
> f0rkz wrote:
>   
>> Yeah, I have multiple ips over the same interface in debian and it  
>> works fine as well.
>>
>> f0rkz
>>
>> On Mar 24, 2009, at 9:03 AM, David A. Parker wrote:
>>
>>     
>>> What?  I have a box with 1 physical interface and 4 IP addresses and
>>> this works just fine:
>>>
>>> gamesrv1:~# ifconfig -a
>>> eth0      Link encap:Ethernet  HWaddr 00:1f:29:50:02:e7
>>>           inet addr:72.237.4.30  Bcast:72.237.4.127  Mask: 
>>> 255.255.255.128
>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>           RX packets:76902609 errors:0 dropped:0 overruns:0 frame:0
>>>           TX packets:85135888 errors:0 dropped:0 overruns:0 carrier:0
>>>           collisions:0 txqueuelen:1000
>>>           RX bytes:7705813491 (7.1 GiB)  TX bytes:14536877789 (13.5  
>>> GiB)
>>>           Memory:f0180000-f01a0000
>>>
>>> eth0:1    Link encap:Ethernet  HWaddr 00:1f:29:50:02:e7
>>>           inet addr:72.237.4.31  Bcast:72.237.4.127  Mask: 
>>> 255.255.255.128
>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>           Memory:f0180000-f01a0000
>>>
>>> eth0:2    Link encap:Ethernet  HWaddr 00:1f:29:50:02:e7
>>>           inet addr:72.237.4.32  Bcast:72.237.4.127  Mask: 
>>> 255.255.255.128
>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>           Memory:f0180000-f01a0000
>>>
>>> eth0:3    Link encap:Ethernet  HWaddr 00:1f:29:50:02:e7
>>>           inet addr:72.237.4.34  Bcast:72.237.4.127  Mask: 
>>> 255.255.255.128
>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>           Memory:f0180000-f01a0000
>>>
>>> lo        Link encap:Local Loopback
>>>           inet addr:127.0.0.1  Mask:255.0.0.0
>>>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>>           RX packets:77 errors:0 dropped:0 overruns:0 frame:0
>>>           TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
>>>           collisions:0 txqueuelen:0
>>>           RX bytes:10036 (9.8 KiB)  TX bytes:10036 (9.8 KiB)
>>>
>>> gamesrv1:~# netstat -an | grep 27015
>>> tcp        0      0 72.237.4.30:27015       0.0.0.0:*                
>>> LISTEN
>>> tcp        0      0 72.237.4.31:27015       0.0.0.0:*                
>>> LISTEN
>>> udp        0      0 72.237.4.34:27015       0.0.0.0:*
>>> udp        0      0 72.237.4.32:27015       0.0.0.0:*
>>> udp        0      0 72.237.4.30:27015       0.0.0.0:*
>>> udp        0      0 72.237.4.31:27015       0.0.0.0:*
>>>
>>> DreamDemon, make sure you are uisng +ip (with a "+") to specify the IP
>>> for srcds when you start it, not -ip (with a "-").
>>>
>>>     - Dave
>>>
>>> Bj?rn Rohl?n wrote:
>>>       
>>>> You do not load up a second tcp/ip-stack just because you alias your
>>>> interface, since you are using ONE stack, you will get one port per
>>>> protocol used. The only reason this works so well on services, is due
>>>> to the ip-header containing the calling domain/ip and apache/sendmail
>>>> applying rulesets based on this. In short, you can not use same port
>>>> on a virtual device if that port is already used on either another
>>>> virtual device (due to them not really existing, just responding to
>>>> another arp-request) or in use on the actual adapter. Since this is
>>>> not really "multihomed", but rather one adapter, with one stack and a
>>>> "poisoned" arp/routing-table, it will not work.
>>>>
>>>> -TheG
>>>>
>>>> On Tue, Mar 24, 2009 at 6:58 AM, [-DSR-][TA]DreamDemon
>>>> <dreamde...@dsrclan.com> wrote:
>>>>         
>>>>> I'm having some major issues with source based games. We currently  
>>>>> have
>>>>> a root server with Cent5 x86_64 running.  This machine has 1 nic  
>>>>> but has
>>>>> multiple ip's.  Even with games seperated by ip, the default port  
>>>>> 27015
>>>>> is incrementing and not able to be set to that for the default on  
>>>>> other
>>>>> ip addresses.  I will use class c addressing to illustrate.
>>>>>
>>>>> ie:
>>>>> DODS - 192.168.2.100:27015 - eth0
>>>>> TF2     - 192.168.2.101:27016(auto-incremented) - eth0:0
>>>>>
>>>>> So how can I resolve this?  The aliases are set proper but the  
>>>>> source
>>>>> games are still detecting the port in use.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> To unsubscribe, edit your list preferences, or view the list  
>>>>> archives, please visit:
>>>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>>>>
>>>>>           
>>>> _______________________________________________
>>>> To unsubscribe, edit your list preferences, or view the list  
>>>> archives, please visit:
>>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>>>
>>>>         
>>> -- 
>>>
>>> Dave Parker
>>> Utica College
>>> Integrated Information Technology Services
>>> (315) 792-3229
>>> Registered Linux User #408177
>>>
>>>
>>> _______________________________________________
>>> To unsubscribe, edit your list preferences, or view the list  
>>> archives, please visit:
>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>>       
>>
>>
>> _______________________________________________
>> To unsubscribe, edit your list preferences, or view the list archives, 
>> please visit:
>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>
>>     
>
>   


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to