My current set of interfaces:

em1       Link encap:Ethernet  HWaddr 84:2B:2B:FA:E0:31
          inet addr:192.168.6.154  Bcast:192.168.6.255  Mask:255.255.255.0
          inet6 addr: fe80::862b:2bff:fefa:e031/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1624328 errors:0 dropped:0 overruns:0 frame:0
          TX packets:340690 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:714724681 (681.6 MiB)  TX bytes:45910373 (43.7 MiB)
          Interrupt:36 Memory:d6000000-d6012800

em2       Link encap:Ethernet  HWaddr 84:2B:2B:FA:E0:33
          inet addr:10.11.34.89  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::862b:2bff:fefa:e033/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5010349 errors:0 dropped:0 overruns:0 frame:0
          TX packets:107216 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:794599927 (757.7 MiB)  TX bytes:39703207 (37.8 MiB)
          Interrupt:48 Memory:d8000000-d8012800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5531414 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5531414 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1076933522 (1.0 GiB)  TX bytes:1076933522 (1.0 GiB)



On Tue, Jun 12, 2012 at 12:26 PM, Ivan Kelly <[email protected]> wrote:

> Thats why I asked about the net.ipv6.bindv6only value. That seems ok
> though. I would expect -Djava.net.preferIPv4Stack=true to make java
> use the ipv4 stack though. It's strange.
>
> @Gabriel, do these machines have an ipv4 stack?
>
> -Ivan
>

Reply via email to