An earnest appeal - please do fix APINGER in 2.2
-
I attached gateway logs to my last post. :)
Also, I was just adding a monitor to the lan IP just to see what it did, I am certain I'm not having a wan problem. It is odd that all gateways are being flagged down at the same time.
-
Multi-wan with static IPs and different gateways within each wan subnets are stable at least in my tests, but I use pppoe connections and we get the same gateway IP allmost all the times, so we have to set at least one monitor IP outside the wan subnet, and this line with outside monitor ip allways gets offline as the apinger reported, but the connection functional as normal.
If there is another to monitor the gatwway, that really helps.
I don't know if this is already known but I suspect this is where the issue exists for alot of people. I get the same problem and it only happens when the upstream gateways set by the ISP are the same. My ISP round-robin's two gateways when you establish a PPPOE connection. When I get differing gateways on connection it works right as rain.
When the same gateway is assigned to both connections the second WAN link will drop with the apinger issue. I can't even see how loadbalancing would be working in this situation either, as the routing table shows all connections just going out the default gateway. -
In my case it's a pure static configuration. Static IP for the fw, static IP for the gateway, no load balancing.
-
In my case it's a pure static configuration. Static IP for the fw, static IP for the gateway, no load balancing.
I'm in the same boat…static all around. Are you running pfSense virtualized or physical? If virtual, what hypervisor are you using? I'm curious if it's something related to Hyper-V or not. I want to move to ESX but haven't had a chance to do it quite yet.
I'm in a situation where I use it as a home router and host a monitoring server on the same box, so I have to do some type of virtualized solution.
-
In my case it's a pure static configuration. Static IP for the fw, static IP for the gateway, no load balancing.
I'm in the same boat…static all around. Are you running pfSense virtualized or physical?
My installation is physical, no virtualization.
-
My installation is physical, no virtualization.
Well so much for that idea…I was really hoping it was a hyper-v issue.
-
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
-
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
You must be new to a support role ;D
People are utterly fantastic at complaining about this, that and the other thing. The moment that they have to wiggle their little finger to help themselves, though, suddenly their problem is not quite so urgent or they just never quite get around to it. But they keep complaining…
-
@ermal:
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
This is a production unit. While I followed the 2.1 beta series, I haven't yet moved to 2.2 beta.
-
@KOM:
You must be new to a support role ;D
People are utterly fantastic at complaining about this, that and the other thing. The moment that they have to wiggle their little finger to help themselves, though, suddenly their problem is not quite so urgent or they just never quite get around to it. But they keep complaining…
Dude.
-
@ermal:
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
I attached my logs on reply 54, then when you asked for them in reply 55, I replied in reply 56 that they were attached to my previous post. You didn't respond asking for anything else, I do not know what else you want…
The gateway logs are on post 54. If you need other logs let me know and I will be glad to provide.
-
i need to see at least two logs since so many people complain about it.
That will give clues for the proper problem here. -
test
Why cant I copy/paste anything into this…
I write test and get no server error, but copy the log and I get unavailable/Nginx error.
-
The website cannot display the page
HTTP 500
Most likely causes:
•The website is under maintenance.
•The website has a programming error.What you can try:
Refresh the page.
Go back to the previous page.
More information More information
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.
For more information about HTTP errors, see Help.
-
Put it on gist.github.com and post the link?
-
https://gist.github.com/anonymous/7f15078fbe6c76e91502
-
i do not see issues from the log do you really have issues?
-
are you sure your system time is on sync and not running backward?
-
I also put a fix on apinger to recover from strange delay values on new snapshots.
-
Yes. It starts to show latency and packetloss. Then I manually restart the Apinger service and it runs again no issues.
It gets worse when the alarms are triggered and after a restart then no problem again for some time.
