78
edits
Router - PFSense: Difference between revisions
→Fix the Gateway monitoring problems
|
=== Fix the Gateway monitoring problems ===
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).
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 apinger the routable address it will use the local link address as the source, meaning you will never get the response...
So it is necessary to change /etc/inc/gwlb.inc with these two fixes and then it will work. These fixes have been submitted to the pfSense team but in the meantime they are described here: https://forum.pfsense.org/index.php?topic=69533.msg411732#msg411732
Once this is done, you will just have to go in "System->Routing" and then edit the WAN_DHCP6 gateway settings to make them as follow:
[[File: WAN_DHCP6_Gateway_settings.png|800px]]
If successful in the script and settings changes you will then get a Gateway Status screen similar to this:
[[File: Status_-_Gateways.png|800px]]
Note: Sometimes, after link failure, the script will still fail to setup apinger properly (especially for [[IPv6]]. IPv4 will typically be ok). This seems to be caused by some timing issues whereby pfSense calls the script too early. Fixing this will probably require a more serious rework of that area in pfSense.
[[Category:IPv6]] [[Category:Router]]
| |||