Snapshot server down?

hec

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.

edit:
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

doktornotor

Anything in firewall logs when trying to download the tgz files from snapshots.pfsense.org? (Yeah, I have a reason to ask.)

hec

No nothing in the logs. I also added a rule to allow the whole ipv6 traffic out for testing.

hec

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?

jimp

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.

hec

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:

packetcapture.txt

hec

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.

hec

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

rodymcamp

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

doktornotor

@rodymcamp:

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.

rodymcamp

no change.

thanks though.
rody

@doktornotor:

@rodymcamp:

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.