Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1451

Two network-cards with different metric, wrong IP-Address lookup

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 2.0.16.Final
    • API
    • None
    • Hide

      Setup: 1 PC 2 Network cards.

      Set metric of Network-adapter1 to "1" using ip 123.123.123.123
      Set metric of Network-adapter2 to "2" using ip 222.222.222.222

      Open powershell and execute

      ping (hostname) -4

      You will get a 123.123.123.123.

      Now start jboss using param -Djboss.bind.address=<hostname>.

      JBoss will bind to address 222.222.222.222 !

      This is a bug, the 123.123.123.123 has a lower metric and must be preferred.

      Show
      Setup: 1 PC 2 Network cards. Set metric of Network-adapter1 to "1" using ip 123.123.123.123 Set metric of Network-adapter2 to "2" using ip 222.222.222.222 Open powershell and execute ping (hostname) -4 You will get a 123.123.123.123. Now start jboss using param -Djboss.bind.address=<hostname>. JBoss will bind to address 222.222.222.222 ! This is a bug, the 123.123.123.123 has a lower metric and must be preferred.
    • Workaround Exists
    • Hide

      Do not bind to hostname, always bind to IP-Address.

      Show
      Do not bind to hostname, always bind to IP-Address.

      In windows we can have one hostname.
      Furthermore we can have two Network Interfaces.
      The Network Interfaces can have different IP-Addresses.
      This means one hostname can have two different IP addresses!
      What IP Address is preferred is defined by the "metric". Lower metrics must be preferred.

      Bug: JBoss ignores the metric.

              rhn-cservice-bbaranow Bartosz Baranowski
              gr1m_jira Peter Rader (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 2 days
                  2d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified