Hello He,

If you grep records.config for the ports you have listed, you'll find something 
like:
----------
-bash-3.00$ egrep '8083|8084|8088' records.config
CONFIG proxy.config.cluster.rsport INT 8088
CONFIG proxy.config.admin.autoconf_port INT 8083
CONFIG proxy.config.process_manager.mgmt_port INT 8084
----------
http://trafficserver.apache.org/docs/v2/admin/files.htm will describe what each 
setting does, but to answer your question I don't believe you can bind the 
listed ports to a particular IP.  A jira ticket has already been opened to 
provide this feature at a later time:  
https://issues.apache.org/jira/browse/TS-448

-- Adam

On 10/19/10 11:49 PM, "he" <[email protected]> wrote:

Hello there, I'm a new user of traffic server. I have a server having network 
interface like this

/sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:15:17:9E:F9:B8
          BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0x3020 Memory:b8820000-b8840000
eth1      Link encap:Ethernet  HWaddr 00:15:17:9E:F9:B9
          inet addr:10.161.29.89  Bcast:10.161.29.127  Mask:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:550248719 errors:0 dropped:0 overruns:0 frame:0
          TX packets:909757737 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:323265851447 (308290.3 Mb)  TX bytes:1169575972530 
(1115394.5 Mb)
          Base address:0x3000 Memory:b8800000-b8820000

I modified ../etc/trafficserver/records.config and add 2 lines

LOCAL proxy.local.incoming_ip_to_bind STRING 10.161.29.89
CONFIG proxy.config.cluster.ethernet_interface STRING eth1

after TS starts up, I notice it's listening on 4 port like this

netstat -tnlp | grep traff
tcp        0      0 10.161.29.89:8080       0.0.0.0:*               LISTEN      
31464/traffic_manag

tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN      
31464/traffic_manag

tcp        0      0 10.161.29.89:8084       0.0.0.0:*               LISTEN      
31474/traffic_serve

tcp        0      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      
31464/traffic_manag


For some reason I'd like TS not to listen on ip 0.0.0.0. How can I set traffic 
manager to bind on specific ip (10.161.29.89:8083/8088) instead of 0.0.0.0 ?


Reply via email to