Project

General

Profile

Actions

Bug #2383

closed

Firmware AutoUpdate preset url dropdown not showing on IPv6 only connection

Added by Seth Mos over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
Start date:
04/18/2012
Due date:
% Done:

0%

Estimated time:
0.50 h
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:

Description

On a IPv6 only connection the Preset URL drop down on system_firmware_settings.php is not showing.

It is possible to enter a custom url here, and auto update over v6 only with a custom url works.
I see that jQuery is supposed to fill in these URLs.

Actions #1

Updated by Seth Mos over 9 years ago

  • Status changed from New to Feedback

fetch returns a 404

[2.1-DEVELOPMENT][root@pfsense.localdomain]/root(14): /usr/bin/fetch -q -o /tmp/manifest http://updates.pfsense.com/manifest
fetch: http://updates.pfsense.com/manifest: Not Found
[2.1-DEVELOPMENT][root@pfsense.localdomain]/root(15): host updates.pfSense.com
updates.pfSense.com is an alias for updates.pfsense.org.
updates.pfsense.org has address 91.227.27.66
updates.pfsense.org has IPv6 address 2605:8000:d:1::249

I've checked the DNS and it appears we have a mismatch, v4 is pointing to files.nl.pfsense.org but the v6 is pointing at snapshots.pfsense.org

DNS needs a fixin?

Actions #2

Updated by Seth Mos over 9 years ago

v4 host contains
pfSense i386 stable updates http://updates.pfsense.org/_updaters
pfSense amd64 stable updates http://updates.pfsense.org/_updaters/amd64
pfSense i386 2.1 DEVELOPMENT snapshots http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_HEAD/.updaters
pfSense amd64 2.1 DEVELOPMENT snapshots http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_HEAD/.updaters

v6 host contains
pfSense i386 stable updates http://updates.pfsense.org/_updaters
pfSense amd64 stable updates http://updates.pfsense.org/_updaters/amd64

Actions #3

Updated by Jim Pingle over 9 years ago

  • Status changed from Feedback to Resolved

Manifest should be OK now. The v6 server was missing a ServerAlias entry for updates.pfsense.com - confirmed they show now on a v6 VM.

I also added the missing entries to the manifests on the v6 box.

Actions

Also available in: Atom PDF