Pfsense 2.0rc3 gateway offline
-
i have dualwan set to fail over(tier1&tier2) with separate browsing and gaming box and after modifying some forwarded port(and already revert back my old config but still opt1 was offline…already restarted my box) my opt1 gateway goes offline but dsl was online-gamers can connect and has an activity...what should be the problem?thanks
Uploaded with ImageShack.us
-
Curious, on system-routing-gateways then edit each do you have something in monitor ip or blank (default)? Anything under advanced? (all blank by default)
On system-routing-groups & edit your multiwan what is trigger level? (Default is member down)
Bill -
monitor ip is default.
triger level is member downwhat should be the problem?planning to reset my box to default if still cant fix it
-
Well you sure that alternate monitor IP you have set it valid and online? I can tell you I can ping your actual gateway IP, but that monitor IP is not answering ping.. So yeah your offline seems valid to me
C:\Windows\System32>ping 119.93.67.253
Pinging 119.93.67.253 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.Ping statistics for 119.93.67.253:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),C:\Windows\System32>ping 122.3.149.254
Pinging 122.3.149.254 with 32 bytes of data:
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238Ping statistics for 122.3.149.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 224ms, Maximum = 224ms, Average = 224msif you say you have nothing in the alternate monitoring IP, did you try putting in your actual gateway IP and see if that changes it, and then try unchecking to use alternate monitor IP.
-
I feel like I have a similar problem.
Here is my setup.
2xwans
wan and opt1
Both are in load balancign
if I unplug one and then plug it back in, pfsense still thinks it's offline sometimes.
I have to go to the routing page, hit edit on one of them ,and hit save and apply for it to refresh. -
Well you sure that alternate monitor IP you have set it valid and online? I can tell you I can ping your actual gateway IP, but that monitor IP is not answering ping.. So yeah your offline seems valid to me
C:\Windows\System32>ping 119.93.67.253
Pinging 119.93.67.253 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.Ping statistics for 119.93.67.253:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),C:\Windows\System32>ping 122.3.149.254
Pinging 122.3.149.254 with 32 bytes of data:
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238Ping statistics for 122.3.149.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 224ms, Maximum = 224ms, Average = 224msif you say you have nothing in the alternate monitoring IP, did you try putting in your actual gateway IP and see if that changes it, and then try unchecking to use alternate monitor IP.
noted sir try it later
-
Well you sure that alternate monitor IP you have set it valid and online? I can tell you I can ping your actual gateway IP, but that monitor IP is not answering ping.. So yeah your offline seems valid to me
C:\Windows\System32>ping 119.93.67.253
Pinging 119.93.67.253 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.Ping statistics for 119.93.67.253:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),C:\Windows\System32>ping 122.3.149.254
Pinging 122.3.149.254 with 32 bytes of data:
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238
Reply from 122.3.149.254: bytes=32 time=224ms TTL=238Ping statistics for 122.3.149.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 224ms, Maximum = 224ms, Average = 224msif you say you have nothing in the alternate monitoring IP, did you try putting in your actual gateway IP and see if that changes it, and then try unchecking to use alternate monitor IP.
noted sir try it later
fix thanks for pointing it out