squeeze : in case you have no network connection with java apps ...

almatic · 12-27-2009, 05:00 PM

... here is the solution.

open file /etc/sysctl.d/bindv6only.conf and set net.ipv6.bindv6only=0, then restart the procfs with invoke-rc.d procps restart

here are the corresponding bugs

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560238
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056

This wasted quiet some time for me, so I thought I'd warn you.
It happens if you update package netbase to 4.40 and it can affect other apps too, especially if they are not from the debian repos.
A real debian special ...

AleLinuxBSD · 12-28-2009, 03:38 AM

Sorry i reply on the wrong place.

Zolex · 12-28-2009, 04:52 PM

Thank you very much for this solution.
It solved my issue.

Tister · 12-29-2009, 08:08 AM

This problem was driving me nuts!
Thank you very much for sharing this information!

guikubivan · 01-12-2010, 08:42 AM

I wasted like 3 days installing different versions of java and it was just this silly line in the bindv6only.conf?

BTW, I am suing the icedtea plugin for mozilla firefox, it works great so far ( i mostly need java for Juniper Network Connect)

Bah! Thanks very much!

antoniusEde · 03-01-2010, 07:32 AM

I had a problem with iceweasel hanging when loading java applets. Turned out I had not loaded the module "ipv6".
Thanks for clearing this out.

bichare · 03-07-2010, 09:58 AM

Hi,all
this solouthion work for me too,with java app client!
but i have this problem with firefox yet!
my browser can't connect to server on all chat room's on web!
any idea?

renato_pacheco · 03-30-2010, 09:41 PM

Oh, man! You saved my life!

I'm from Brazil and I registered in this forum only to thank you a lot!

Bye!

alan99 · 04-07-2010, 06:15 PM

I had the same problem but solved it on my own. I noticed an extra line at boot, something about setting systctl using a bindv6only file. I tinkered around and changed the configuration file and then the java applets worked. I had a similar problem with Swat. It wouldn't run because it was only listening on ip6 and not ipv4. I changed tcp to tcp4 in /etc/inetd.conf

DraZtiK · 04-25-2010, 04:26 PM

Quote:

Originally Posted by almatic

... here is the solution.

open file /etc/sysctl.d/bindv6only.conf and set net.ipv6.bindv6only=0, then restart the procfs with invoke-rc.d procps restart

here are the corresponding bugs

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560238
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056

This wasted quiet some time for me, so I thought I'd warn you.
It happens if you update package netbase to 4.40 and it can affect other apps too, especially if they are not from the debian repos.
A real debian special ...

Thanks! this worked for me.

megaprog · 05-01-2010, 05:01 PM

Worked like a charm!

thecarpy · 05-10-2010, 07:05 PM

Thanks, this helped me as well!

switzel · 03-04-2011, 06:38 PM

Thanks a lot!

Pap · 05-03-2011, 03:04 AM

I was another victim of this bug, and your post saved my day from trying different tricks again and again, to solve the problem. Thank you!

HamRadio · 05-26-2011, 02:50 AM

Quote:

Originally Posted by almatic

... here is the solution.

open file /etc/sysctl.d/bindv6only.conf and set net.ipv6.bindv6only=0, then restart the procfs with invoke-rc.d procps restart

It worked for me too.
Thank you very much indeed!