Static IP on WAN
-
I have tried to reconfigure my WAN connection IP details to 'static' (for diagnostic reasons) but this option seems to have disappeared from pfsense 2.
Can somebody advise please if static WAN / ISP addressing is possible in 2 and how to do it?
-
usally you do get your ip from your service provider. even if static, in most cases you then get always the same adress, but from your provider. which connection type do you use for wan access?
-
I can use either but I am trying to diagnose an apinger error that is becoming a real irritation, it is cluttering my logs with spurious reports that are simply wrong and nobody seems prepared to accept this. I do not have a connectivity problem and I am getting more than a little tired of apinger telling me that I do regardless of how I configure 'routing/advanced' settings. I know that a lot of work is going on in the routing / load balancing stuff currently so am trying to pinpoint why I am seeing spurious errors (and prove that they ARE spurious).
I have confirmed via my ISP that there is no issue, my ISP has confirmed with the 'wholesaler' (the telecoms provider) that there is no issue.
As part of the diagnostic process I have identified a potential behaviour that may be an issue - my gateway IP is changing, not very often and not at a predictable frequency, my ISP believe that this is happening because of a DHCP refresh being issued by pfsense (maybe as a result of apingers spurious fault detection) although this is not getting recorded in system logs. The gateway details that my ISP issue are apparently decided based on a whole bunch of stuff such as fastest response, maintenance and some 'load' statistics from any one of a number of potential gateways. My ISP suggested that I fix the IP details for a period to see if there is some other issue that they aren't aware of changing my gateway IP.
I therefore want to 'fix' the IP details but the ability to do so seems to have been removed.
-
Static IP is there, it's in the drop-down menu for "type" on any Interface screen, where it's always been. Not sure why it wouldn't show up for you there, especially if you're on DHCP that should be working.
-
Static is in the type list but then you can not use PPPoE as the user and PW disappear, I need to fix the IP details for the PPPoE connection.
-
Ah, well that has never been possible to set a manual IP on PPPoE.
You said DHCP previously, not PPPoE. There shouldn't be any kind of a "refresh" after login on PPPoE that I'm aware of, not unless it's actually dropping the link and reconnecting.
Even so, if that did happen, it should be logged I thought.
-
Thats what I am trying to test, my uptime isn't dropping back to 0 but the gateway occasionally changes after an apinger error and I can't tell if the gateway change instigated the apinger error or vica versa or even what triggers the gateway change. My ISP reckon it only changes on login, DHCP request or gateway failure but changing it is. If I could fix the gateway IP I reckon I could find out which end of the connection causes the change because I could eliminate DHCP at least.
I am going to drop back to my Draytek for a while because it will allow me to fix the WAN IP details and do some more latency tests over the next 24 hours to see what happens.
How long would you expect the link to go down for before the uptime counter dropped to zero?
