Project

General

Profile

Actions
Copy link

Bug #3610

closed

Network Connection Problem

Added by Florian Asche over 11 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
04/18/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Hi,

i installed PFSense Version 2.1.2, amd64.

I have 4 interfaces:
WAN: IPv4 Internet
WAN3G IPv4 Backup Internet
WANIPv6 IPv6 GIF HE.Net Tunnel
LAN Local Network

Routing:
WAN3G
WAN Default
WANIPv6 Default
HexaBus (Some other IPv6, with Routing, Special Network)

Gateway Group:
WAN
WAN3G

With this Setup PFSense can't Check for Updates. DynDNS Update, Packet Installation and some other things didnt work too.

Actions
Copy link
 #1

Updated by Chris Buechler over 11 years ago

  • Status changed from New to Rejected

Nothing mentioned here appears to be a bug, rather you have some configuration issues you need to correct. Please utilize one of our support options (forum, mailing list, etc.) for further assistance. More info at https://pfsense.org/support

Actions
Copy link
 #2

Updated by Florian Asche over 11 years ago

Hi,

i think i found the Problem.

I Think its 50% a configuration problem and 50% a bug.

I Configured the DNS-Forwarder to listen only on LAN. In General Setup i configured my Router as first DNS-Server. Not 127.0.0.1, but the pfsense Firewall try to get the IP from DNS on 127.0.0.1. There is a Timeout then, and the Pfsense Update check is configured on Timeout 5 Seconds.

Yeah i know, i can set "Do not use the DNS Forwarder as a DNS server for the firewall"
By default localhost (127.0.0.1) will be used as the first DNS server where the DNS forwarder is enabled, so system can use the DNS forwarder to perform lookups. Checking this box omits localhost from the list of DNS servers.

But i think there should be somewhere a warning or information.

Actions
Copy link

Also available in: Atom PDF