Announcement

Collapse

NextGen (Mirth) Connect 3.10.0 Released!

NextGen (Mirth) Connect 3.10.0 is now available as an appliance update and on our GitHub page. This release includes better SQL Server database support, security improvements through fixes and library updates, and improvements for the Advanced Clustering plugin with a focus on improving performance of many of the tasks that are carried out on a frequent interval. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Mirth appears to be running in IPv6 ??

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mirth appears to be running in IPv6 ??

    This looks a little suspect to me:
    Code:
    [email protected]:~$ netstat -an 
    
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State      
    
    tcp        0      0 127.0.0.1:8001          0.0.0.0:*               LISTEN     
    
    tcp        0      0 127.0.0.1:8002          0.0.0.0:*               LISTEN     
    
    tcp        0      0 127.0.0.1:8003          0.0.0.0:*               LISTEN     
    
    tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN     
    
    tcp        0      0 127.0.0.1:5038          0.0.0.0:*               LISTEN     
    
    tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN     
    
    tcp        0      0 0.0.0.0:2000            0.0.0.0:*               LISTEN     
    
    tcp6       0      0 :::6661                 :::*                    LISTEN     
    
    tcp6       0      0 :::1099                 :::*                    LISTEN     
    
    tcp6       0      0 :::8080                 :::*                    LISTEN     
    
    tcp6       0      0 :::43093                :::*                    LISTEN     
    
    tcp6       0      0 :::22                   :::*                    LISTEN     
    
    tcp6       0      0 :::8443                 :::*                    LISTEN     
    
    tcp6       0      0 ::ffff:172.25.12.5:6661 ::ffff:172.25.131.:2121 ESTABLISHED
    
    tcp6       0    256 ::ffff:172.25.12.53:22  ::ffff:172.25.11.:35844 ESTABLISHED
    
    udp        0      0 0.0.0.0:2727            0.0.0.0:*                          
    
    udp        0      0 0.0.0.0:4520            0.0.0.0:*                          
    
    udp        0      0 172.25.12.53:5060       0.0.0.0:*                          
    
    udp        0      0 0.0.0.0:68              0.0.0.0:*                          
    
    udp        0      0 0.0.0.0:4569            0.0.0.0:*

    It?s only listening in tcp6 (IPv6 I ?spose) and not IPv4.



    When I do an nmap from outside the box I get:


    Code:
    [email protected] ~ $ nmap development
    
    Starting Nmap 4.20 ( http://insecure.org ) at 2007-07-09 15:25 EDT
    
    Interesting ports on extension.corp.tripractix.com (172.25.12.53):
    
    Not shown: 1692 closed ports
    
    PORT     STATE SERVICE
    
    22/tcp   open  ssh
    
    80/tcp   open  http
    
    2000/tcp open  callbook
    
    8080/tcp open  http-proxy
    
    8443/tcp open  https-alt
    
     
    
    Nmap finished: 1 IP address (1 host up) scanned in 0.192 seconds
    No 6661? Got any ideas? If we're reading this right its running in IPv6 and not accessible from IPv4.

    This is Mirth 1.4 on Ubuntu Fawn and Sun Java 1.5 (maybe 1.6).
    Jon Bartels

    Zen is hiring!!!!
    http://consultzen.com/careers/
    Talented healthcare IT professionals wanted. Engineers to sales to management.
    Good benefits, great working environment, genuinely interesting work.

  • #2
    Re:Mirth appears to be running in IPv6 ??

    I passed this on to our network operations team so they can investigate.

    Thanks!
    Chris Lang

    Comment


    • #3
      Re:Mirth appears to be running in IPv6 ??

      chrisl wrote:
      I passed this on to our network operations team so they can investigate.

      Thanks!
      Quick take it back!

      It turns out its a bit of a bug or misunderstanding of sorts in Ubuntu or netstat.

      If you look a few lines down you can see that the same line appears for port 8080. I can connect to 8080. So whats happening is that for whatever reason listening ports show up as being IPv6 even though they may be on an IPv4 interface.
      Jon Bartels

      Zen is hiring!!!!
      http://consultzen.com/careers/
      Talented healthcare IT professionals wanted. Engineers to sales to management.
      Good benefits, great working environment, genuinely interesting work.

      Comment

      Working...
      X