Project

General

Profile

Actions

Bug #2728

closed

PPP WAN types do not obtain DNS servers properly in 2.0.2-RELEASE

Added by Jim Pingle over 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
PPP Interfaces
Target version:
-
Start date:
12/21/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.x
Affected Architecture:

Description

[Note: This has already been resolved in 5feadf7fca75866582af73834c8d2ab14edca456 - Putting an entry here for others to find]

In 2.0.2-RELEASE, PPP type WANs, such as PPPoE, do not obtain DNS servers properly. By consequence, if a user has defined no custom DNS servers, they can end up without functional DNS.

This is due to an issue in the ppp-linkup script not properly parsing the parameters passed to it by mpd.

Workaround 1:
Add DNS servers under System > General. If you do not know your DNS servers, use common public DNS servers like 8.8.8.8 / 8.8.4.4 or 208.67.222.222 / 208.67.220.220

Workaround 2:
Install the System Patches Package

Add a new patch and fetch/apply it:
Name: ppp_dns_fix
URL: https://github.com/bsdperimeter/pfsense/commit/5feadf7fca75866582af73834c8d2ab14edca456
Path Strip Count: 1
Base: /
Ignore Whitespace: [X]

Actions #1

Updated by Jim Pingle over 11 years ago

  • Description updated (diff)
Actions #2

Updated by Jim Pingle over 11 years ago

  • Description updated (diff)
Actions #3

Updated by Hartmut W about 11 years ago

mount root filesystem rw (on embedded systems) using

/etc/rc.conf_mount_rw

before applying the patch. This can be done either using the exec.php from the webinterface or console login.

Actions #4

Updated by Anonymous almost 11 years ago

Fixed in 2.0.3-RELEASE. Ticket can be close.

Actions

Also available in: Atom PDF