Hi I couldn't reproduce the problem at all on my links version. Then, I tried to download links-2.3 package from Debian and the bug was there - it can't connect to any ipv4 address specified numerically.
It is actually Debian that broke this thing, specifically their "ipv6.diff" patch. So it is up to them to fix it. I'm adding Debian Links maintainer "Axel Beckert" to CC. Mikulas On Mon, 17 Oct 2011, e-mail samk-01 wrote: > Hi Mikulas, > > On 17 October 2011 02:27, Mikulas Patocka > <miku...@artax.karlin.mff.cuni.cz> wrote: > > > > I have no clue what cause that. I could not reproduce it on my network. > > > > Please run strace with the old (working) and new (non-working) links > > version and send me the traces. > > > > For example "strace -o log.1 links http://hostname:1234/";. > > > As requested, strace logs of two different versions of LInks are > attached. The older version works OK the newer version consistently > fails. In case it might help with the diagnosis I have also included > strace logs from other browsers which all work OK. > > Since notifying you of the issue I have also raised a bug report with Debian. > > Do let me know if you require any further information. > > Regards > SamK > > attached: strace-browser-logs.tgz > > > > > > On Sat, 8 Oct 2011, e-mail samk-01 wrote: > > > >> Bug Report: > >> Links2 Version=2.3 > >> Repository=Debian Testing > >> Distro=antiX-M11 > >> > >> Loading a specified IP address and port number on a LAN consistently > >> fails. For example 192.168.2.104:808 or http://192.168.2.104:8080 > >> produces the following error message: > >> "Error loading 192.1698.2.104:8080/: > >> Cannot assign address" > >> > >> A previous version of Links (2.3pre1) does this successfully and > >> reliably, as do a range of other browsers. > >> > >> > >> SamK > >> > > >
