Snapshot server down?
I can't reach the server with ipv4. With ipv6 i can ping it but get no response from webserver.
I tried it from 2 different locations so i think my isp should not have a problem.
Somebody else with the same problem?
I just started an update of a 2GB nanoBSD Alix, and the snapshot server was found.
I did now some more tests and it is getting more and more strange.
I get to http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/ but not to http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/
Perhaps you are suffering from this? http://forum.pfsense.org/index.php/topic,64418.0.html
Maybe i found the problem.
On a site with only ipv4 i can get to snapshots with dualstack on the other side i can't.
So i think there is a problem with ipv6 and snapshots.
Ok on a server with only ipv4 i can get to the url also on same site where i have the problems. IPv6 is ok and i have no problem with all sites i know they have ipv6 only with snapshots there is a problem.
I did today manual update and have still the same problem.
Any ideas how to solve the problem?
Why does the pfSense show me that there are updates available and also which update but can't download the updates. Its getting more and more strange.
What i have testet:
pfsense –> ipv4 snapshots.pfsense.org --> no answer
pfsense --> ipv6 snapshots.pfsense.org --> answer
server dualstack --> ipv4 snapshots.pfsense.org --> no answer
server dualstack --> ipv6 snapshots.pfsense.org --> answer
server ipv4 --> ipv4 snapshots.pfsense.org --> no answer
client dualstack without proxy –> http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/ --> ok
client dualstack without proxy --> http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/ --> error
server ipv4 --> http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/ --> ok
server ipv4 --> http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/ --> ok
client dualstack with proxy --> http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/ --> ok
client dualstack with proxy --> http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/ --> ok
But now i have no ideas where i should debug. Maybe somebody has an idea what i should try. This behavior could not be normal.
In each of those cases, which IP address does snapshots.pfsense.org resolve to for you?
Also have you cleared your browser cache? Or are you testing some other way?
I'm running dual stack with no proxy and it loads fine for me…
snapshots.pfsense.org has address 18.104.22.168
snapshots.pfsense.org has IPv6 address 2610:1c0:1:25::51
Yes brower cache is cleared. I tried it also with lynx on some servers. I also see that i can't reach snapshots.pfsense.org but i can see http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/
It is very odd especially because that's on the same server, the same web server software, and there really isn't anything different about that URL except that it has some HTML on it where the others do not. It's just two different directories sitting next to each other, and nobody else seems to have an issue loading them.
If i try port test to port 80 with pfsense from diagnostics i got also with ipv6 success.
Do you have any ideas where i should try to search/debug?
curl -v -I -H "Testing: Test header so you see this works" http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/updates/pfSense-2.1-RC0-4g-amd64-nanobsd_vga-upgrade-20130717-2242.img.gz * About to connect() to snapshots.pfsense.org port 80 (#0) * Trying 2610:1c0:1:25::51... * connected * Connected to snapshots.pfsense.org (2610:1c0:1:25::51) port 80 (#0) > HEAD /FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/updates/pfSense-2.1-RC0-4g-amd64-nanobsd_vga-upgrade-20130717-2242.img.gz HTTP/1.1 > User-Agent: curl/7.26.0 > Host: snapshots.pfsense.org > Accept: */* > Testing: Test header so you see this works > * additional stuff not fine transfer.c:1037: 0 0 * HTTP 1.1 or later with persistent connection, pipelining supported < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Thu, 18 Jul 2013 21:27:06 GMT Date: Thu, 18 Jul 2013 21:27:06 GMT < Server: Apache/2.2.21 (FreeBSD) mod_ssl/2.2.24 OpenSSL/0.9.8q DAV/2 Server: Apache/2.2.21 (FreeBSD) mod_ssl/2.2.24 OpenSSL/0.9.8q DAV/2 < Last-Modified: Thu, 18 Jul 2013 04:37:59 GMT Last-Modified: Thu, 18 Jul 2013 04:37:59 GMT < ETag: "f38a9e-5c5fb63-4e1c1c65157c0" ETag: "f38a9e-5c5fb63-4e1c1c65157c0" < Accept-Ranges: bytes Accept-Ranges: bytes < Content-Length: 96861027 Content-Length: 96861027 < Content-Type: application/x-gzip Content-Type: application/x-gzip < * Connection #0 to host snapshots.pfsense.org left intact * Closing connection #0
If i try download with curl i get the filesize so there is a connect but the download does not start.
AhnHEL last edited by
Do you have any settings entered in the GUI for System: Advanced: Miscellaneous under Proxy Support?
No pfsense is working as proxy and has direct access to internet.
The last idea i have is to resetup this server maybe there is some problem because of the update from 2.0 to 2.1
I reinstalled pfsense and still the same situation.
I can download the sha and md5 files but not the image files. wtf?
I was reading this thread and just wondering…
Can you test other servers with files with the .tgz file extension?
Maybe the .tgz extension is blocked by your ISP somehow?
Can you download img.gz extensions files from the pfsense snapshot server?
If somebody can tell me a server with IPv6 and tgz files on it…
I tried img.gz to download the same problem.
I don't think that my ISP is blocking this only on ipv6 and not on ipv4. This makes no sense.
I tried it now with tar.gz files from www.apache.org and www.tcpdump.org which have both an IPv6 address - no problem
I tried tgz files from http://lxml.de/files/ - no problem
Anything in firewall logs when trying to download the tgz files from snapshots.pfsense.org? (Yeah, I have a reason to ask.)
No nothing in the logs. I also added a rule to allow the whole ipv6 traffic out for testing.
As i see nobody has an idea how to solve it.
Could there be any problems in the configuration i mean maybe there happened something on update to 2.1?
Maybe i could resetup with no config and adding all objects new.
Is it possible to create lagg interface at setup? If not it would be very nice if someone could implement that. I think a lot of users use lagg interfaces.
An other idea is to override the hosts file that i only get an ipv4 address for snapshots.pfsense.org.
What do you guys think?
Given that you can access the server but not a specific url on that server, I doubt it's anything in your firewall config. Nothing in the firewall (aside from a proxy!) would be seeing that far inside the packets.
To confirm that you could configure a PC up with the correct IP info and try the request directly with no firewall involved, if you can.
I will try this today. The firewall has now no proxy anymore. I removed the packages to check if the proxy is the problem but its the same problem.
Here is a packetcapture:
As i see the redmine.pfsense.org has now also a IPv6 adress. On this server i have the same problem.
I think there is some problem with ipv6 to the pfsense servers. With enough other servers i have no problems only with pfsense.
This was wrong redmine is still working.
Today i talked with my ISP maybe they can find a solution.
Can you guys search in the server logs if you find something from 2001:858:5:2c00::/56?
Maybe there is something in the logs which helps me debugging this.
Btw looks like that this is a similar problem: http://forum.pfsense.org/index.php/topic,65397.0.html
I am having the same issue. I am downloading the new snapshot for today and we will see if i can connect after a manual update. I am not using ipv6 at all on my network. I have been trying to do an auto update several times and i never can connect. I have been using 2.1-RC1 (amd64)
built on Thu Aug 1 19:39:40 EDT 2013
I am not using ipv6 at all on my network.
env ip6addrctl_enable="yes" ip6addrctl_policy="prefer_ipv4" /etc/rc.d/ip6addrctl start
and try again.