Hi Luís Antonio Pereira, that was very well explained and I am sure its gona help many. Great help from you guys. But the example in my reply is working exactly as I wanted. Ofcourse I am going to change it to the way you suggested and see if that too works same way. Btw noted a small typo in the last where 8080 must be 8081 , please dont mind me pointing it out, as I am sure its just a silly typo.
Many thanks once again, you guys makes this mailing list very friendly towards noobs like me regards Babu On Fri, Aug 8, 2014 at 1:53 AM, Luís Antonio Pereira < [email protected]> wrote: > Hi Babu > > ip-in=[addr] - Bind inbound IP address (listen for client) > ip-out=[addr] - Bind outbound IP address (connect to origin server). > > on addr > ipv4 - Use IPv4 (default) > ipv6 - Use IPv6 > > tr-in - Transparent inbound > tr-out - Transparent outbound > tr-full - Fully transparent (inbound and outbound) > tr-pass - Transparently Pass-through non-HTTP traffic (in conjuction with > tr-in) > ssl - SSL terminated port > > > You accept connections from your clients on http protocol on address > 192.168.0.252 port 8080 > ip-in=192.168.0.252:8080:ipv4 > > You accept connections from your clients on http protocol on all > address port 8080 your server > ip-in=8080:ipv4 > > You accept connections from your clients and using redirect filter on > address 192.168.0.252 port 8080 > ip-in:8080:192.168.0.252:8080:ipv4:tr-in > > You accept connections from your clients and using TPROXY filter on > address 192.168.0.252 port 8080 > ip-in:8080:192.168.0.252:8080:ipv4:tr-out > > You accept connections from your clients on http protocol on address > 192.168.0.252 port 8080 and connect on origin server on 200.200.0.1 > from port 9090 > ip-in=192.168.0.252:8080:ipv4 ip-out=200.200.0.1:9090:ipv4 > > You accept connections from your clients on HTTPS protocol on address > 192.168.0.252 port 8081 > ip-in=192.168.0.252:8080:ssl:ipv4 > > > Regards > > Luís Antonio Pereira > > > 2014-08-07 1:00 GMT-04:00 Babu Chaliyath <[email protected]>: > > Alan, > > Many thanks for that help, that link was still confusing but I did some > > trials and found the way to get out of this mess. I am just putting it > below > > as I am sure thats gona help many people out there. > > sorry for the little late reply > > > > CONFIG proxy.config.http.server_ports STRING ipv4:80:ip-in=192.168.1.1 > > ipv4:80:ip-in=172.16.0.1 ip4v:443:ssl::ip-in=172.16.0.1 > > > > The above example binds ATS port 80 to ip addresses 192.168.1.1 and > > 172.16.0.1 also port 443 to ip address 172.16.0.1 > > > > Hope that help someone too > > > > With many thanks to Alan > > Regards > > Babu > > > > > > On Thu, Aug 7, 2014 at 12:05 AM, Alan M. Carroll > > <[email protected]> wrote: > >> > >> Babu, > >> > >> [Resending because it didn't seem to go through] > >> > >> See here [1]. When you define the server ports, you can specify a local > >> address to bind for each port individually. The option you mention is > then > >> used for each port for which you don't define a local address (that is, > it > >> specifies the default binding address). > >> > >> [1] > >> > https://docs.trafficserver.apache.org/en/latest/reference/configuration/records.config.en.html#proxy-config-http-server-ports > >> > >> Tuesday, August 5, 2014, 1:39:35 PM, you wrote: > >> > >> > >> Hi, > >> I tried looking for any info on binding ATS to multiple IP addresses , > but > >> couldn't find anything which would help to solve my issue. I wanted to > bind > >> the ATS to 2 of my external IP addresses, but with provided option > >> proxy.local.incoming_ip_to_bind allow me to bind ATS to only one, or > all of > >> them but not 2. Any suggestions to resolve this issue? > >> > >> thanks & regards > >> Babu Chaliyath > >> > > >
