Karthikdasari0423 commented on issue #10660:
URL: 
https://github.com/apache/trafficserver/issues/10660#issuecomment-1840546370

   @bryancall i dont think that is the issue 
   
   i added ipv6 to /opt/ats/etc/trafficserver/records.yaml 
   
   ```
   
   ---
   ts:
     http:
       server_ports: 8080 8080:ipv6 4443:ssl 4443:quic 4443:ipv6
   ---
   ```
   and restarted the ats but still it is not getting opened on tcp6 and udp6 
   
   ```
   root@ubuntu:~# /opt/ats/bin/trafficserver ?
   Usage: /etc/init.d/trafficserver {start|stop|status|restart}
   root@ubuntu:~# /opt/ats/bin/trafficserver restart
    * Restarting Apache Traffic Server trafficserver                            
                                                   [ OK ]
   root@ubuntu:~# /opt/ats/bin/trafficserver status
    * traffic_server is running
   root@ubuntu:~#
   
   ```
   
   root@ubuntu:~#
   root@ubuntu:~# netstat -alpn | grep traffic
   tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN   
   255623/traffic_serv
   tcp        0      0 0.0.0.0:4443            0.0.0.0:*               LISTEN   
   255623/traffic_serv
   udp        0      0 127.0.0.1:59163         127.0.0.53:53           
ESTABLISHED 255623/traffic_serv
   udp        0      0 0.0.0.0:4443            0.0.0.0:*                        
   255623/traffic_serv
   unix  2      [ ACC ]     STREAM     LISTENING     2514844  
255623/traffic_serv  /opt/ats/var/trafficserver/jsonrpc20.sock
   unix  2      [ ]         DGRAM      CONNECTED     2514837  
255623/traffic_serv
   unix  3      [ ]         STREAM     CONNECTED     2514839  
255625/traffic_cras
   unix  3      [ ]         STREAM     CONNECTED     2514838  
255623/traffic_serv
   root@ubuntu:~#
   root@ubuntu:~#
   
   ```
    


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to