Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

Router - PFSense: Difference between revisions

Content deleted Content added
Adsb (talk | contribs)
m PPPoE
Tags: Mobile edit Mobile web edit
Adsb (talk | contribs)
m PPPoE
Tags: Mobile edit Mobile web edit
 
(One intermediate revision by the same user not shown)
Line 151: Line 151:




=== Fix the PPoE DNS problem ===
=== Fix the PPPoE DNS problem ===


The problem is that the PPoE stuff is still a bit flaky in 2.1.2, and although the PPoE negotiation itself is fine, it seems pfSense will often lose the ISP DNS settings (this seems to be a timing related issue of some kind, so sometimes it works and sometimes it does not. You can even get into situations where the DNS setting is there and then it suddenly disappear!).
The problem is that the PPPoE stuff is still a bit flaky in 2.1.2, and although the PPPoE negotiation itself is fine, it seems pfSense will often lose the ISP DNS settings (this seems to be a timing related issue of some kind, so sometimes it works and sometimes it does not. You can even get into situations where the DNS setting is there and then it suddenly disappear!).


Arghhhh!!!!!
Arghhhh!!!!!
Line 160: Line 160:


[[File:System - General setup.png|800px]]
[[File:System - General setup.png|800px]]



=== Testing internet access ===
=== Testing internet access ===
Line 171: Line 170:
Although you can now go on the internet fine, If you look at the RRD graphs or consult the gateway status page you will notice the status is either marked as offline or unknown.
Although you can now go on the internet fine, If you look at the RRD graphs or consult the gateway status page you will notice the status is either marked as offline or unknown.


This is a case because the script currently configuring apinger (the process that monitors the gateways) is buggy and currently does not cope very well with PPoE (when it used to be perfectly fine in pfSense 2.0.x).
This is a case because the script currently configuring apinger (the process that monitors the gateways) is buggy and currently does not cope very well with PPPoE (when it used to be perfectly fine in pfSense 2.0.x).


Another problem is that for [[IPv6]] the AAISP gateway will currently not reply to pings on its local link address (and it is the one used for routing the traffic, so it is reachable!). So you have to manually set the monitor address to be 2001:8b0:0:81::51bb:51bb (which is the [[IPv6]] address of clueless.aa.net.uk). But even that won't initially work because even if you set the routable address, apinger is told to use the local link address as the source, meaning you will never get the response...
Another problem is that for [[IPv6]] the AAISP gateway will currently not reply to pings on its local link address (and it is the one used for routing the traffic, so it is reachable!). So you have to manually set the monitor address to be 2001:8b0:0:81::51bb:51bb (which is the [[IPv6]] address of clueless.aa.net.uk). But even that won't initially work because even if you set the routable address, apinger is told to use the local link address as the source, meaning you will never get the response...