can not connect to www.freebsd.org or IP addr 8.8.178.110 port 80

Discussion:

(too old to reply)

Matthias Apitz

2016-08-01 18:41:52 UTC

Hello,

I have some FreeBSD CURRENT netbooks and one Ubuntu in my WLAN, the WAN
IP addr is 88.217.112.246 (as shown by http://myip.nl/ )

none of the WLAN workstations can reach www.freebsd.org at port 80;
the command

telnet www.freebsd.org 80

shows resolving to the IP addr 8.8.178.110, but does not connect; a
tcpdump shows only SYN pkg going out to 8.8.178.110 but no SYN answer
is coming in. This is as far as I can see the only side which is not
reachable, all other port 80, 443 and SSH 22 to anywhere is just fine;

Any ideas what could be wrong? I'm afraid, when I contact my ISP (a
German local telephone provider) they will ask me if I have the latest
Win7 patch installed ... :-)

matthias

--
Matthias Apitz, ✉ ***@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich auch keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989

Jörg Preiß

2016-08-01 18:47:41 UTC

Permalink

Hi,

we had a lot of problems accessing forums.freebsd.org and other pages.
The point there was, that we were blacklisted somehow.
With forums itself, the admin told us, we would have sent some some SMB
packages to the site.
On another page, it was a mail blacklisting service which prevented us
from accessing https pages. I still don't know how that works.

hth
JÃ¶rg

Cary

2016-08-01 19:36:47 UTC

Permalink

hello Matthias,

Today I also noticed, just after fetching ports with portsnap(8) ,
that 8.8.178.110 wasn't responding. It is back now afaict.

Cary

--
***@sdf.org
SDF Public Access UNIX System - http://sdf.org

------------------------------

Matthias Apitz

2016-08-01 19:53:44 UTC

Permalink

Post by Cary

Post by Matthias Apitz
none of the WLAN workstations can reach www.freebsd.org at port 80; the
command
telnet www.freebsd.org 80
shows resolving to the IP addr 8.8.178.110, but does not connect; a tcpdump
shows only SYN pkg going out to 8.8.178.110 but no SYN answer is coming in.
This is as far as I can see the only side which is not reachable, all other
port 80, 443 and SSH 22 to anywhere is just fine;
Any ideas what could be wrong? I'm afraid, when I contact my ISP (a German
local telephone provider) they will ask me if I have the latest Win7 patch
installed ... :-)
matthias

hello Matthias,
Today I also noticed, just after fetching ports with portsnap(8) ,
that 8.8.178.110 wasn't responding. It is back now afaict.

To make this clear: I was able at the same time to reach the IP
addr 8.8.178.110 from other points (for example from my mobile phone),
but not from my WAN addr 88.217.112.246; and I do not have a firewall
block for port 80 for FreeBSD.org; the only options I can think off are

a) a routing issue from 88.217.112.246 to 8.8.178.110
b) a block in FreeBSD.org based on the source addr 88.217.112.246

matthias

Eduardo Lemos de Sa

2016-08-01 19:30:46 UTC

Permalink

Dear Matthias

Post by Matthias Apitz
Hello,
I have some FreeBSD CURRENT netbooks and one Ubuntu in my WLAN, the WAN
IP addr is 88.217.112.246 (as shown by http://myip.nl/ )
none of the WLAN workstations can reach www.freebsd.org at port 80;
the command
telnet www.freebsd.org 80
shows resolving to the IP addr 8.8.178.110, but does not connect; a
tcpdump shows only SYN pkg going out to 8.8.178.110 but no SYN answer
is coming in. This is as far as I can see the only side which is not
reachable, all other port 80, 443 and SSH 22 to anywhere is just fine;
Any ideas what could be wrong? I'm afraid, when I contact my ISP (a
German local telephone provider) they will ask me if I have the latest
Win7 patch installed ... :-)
matthias
--
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich
auch keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "

I had the same problem last week, despite for all friends in Brazil was
everything ok. Some conclusions:

1) yes, the IP address is 8.8.178.110 (so, your DNS is ok)

2) Try http://isup.me/www.freebsd.org , so that you can check if the site
is working, or

3) http://www.isptools.com.br/caiu#www.freebsd.org , so that you can test
from which places are able to connect

Of course, the last one is on Brazil, but it is a test to be done

I didn't was able to solve the problem by myself. Someone, on my network (I
was on job) heard my complains and fixed it. My conclusion was that is was
caused by some bad configured firewall (ping was working, but not http).

Cheers

Eduardo

--
Eduardo Lemos de Sa
Associated Professor Level 4
Dep. Quimica da Universidade Federal do Paraná
fone: +55(41)3361-3300
fax: +55(41)3361-3186

Cary

2016-08-01 20:16:30 UTC

Permalink

Post by Matthias Apitz

Post by Cary

hello Matthias,
Today I also noticed, just after fetching ports with portsnap(8) ,
that 8.8.178.110 wasn't responding. It is back now afaict.

To make this clear: I was able at the same time to reach the IP
addr 8.8.178.110 from other points (for example from my mobile phone),
but not from my WAN addr 88.217.112.246; and I do not have a firewall
block for port 80 for FreeBSD.org; the only options I can think off are
a) a routing issue from 88.217.112.246 to 8.8.178.110
b) a block in FreeBSD.org based on the source addr 88.217.112.246
matthias

portsdb(1) failed for me, and after checking with ping(8) there was
no response trying to reach the same ip from my ISP in California.

--
***@sdf.org
SDF Public Access UNIX System - http://sdf.org

------------------------------