PfSense-Full-Update-1.2.3-20090528-2026.gz
-
Strange but not fatal errors after firmware upgrade.
Status -> Load Balancer :
wan Delay: , Loss:
opt2 Delay: , Loss:Diagnostics -> ARP Tables:
xxx.xxx.xxx.xxx 00:0a:b7:c3:62:70 WAN
xxx.xxx.xxx.xxx 00:17:31:60:5d:2e LANStatus -> Interfaces:
WAN interface (xl0)
Status up
MAC address 00:50:da:4b:2e:3d
IP address xxx.xxx.xxx.xxx
Subnet mask 255.255.255.252
Gateway xxx.xxx.xxx.xxx
ISP DNS servers 83.234.20.30 195.82.134.6 213.80.138.12 217.150.34.129
Media 100baseTX <full-duplex>In/out packets 3075/2453 (1.96 MB/292 KB)
In/out errors 0/0
Collisions 0- never previously been messages in firewall log about LAN interfaceÆ
…block out on bge0:</full-duplex>
- never previously been messages in firewall log about LAN interfaceÆ
-
There is some work being done on the load balancing, I believe. Some improvements from 2.0 are being backported to resolve issues being seen by many people. There may still be something out there that isn't quite finished.
As for the ARP Tables and Interfaces output you pasted, perhaps it's really early and I'm still asleep, but I don't see anything wrong in the output you pasted. Was there supposed to be an error in there somewhere?
-
As you can see : WAN is Offline. But must be ONLINE :
$ arp -an | grep ISP-Gateway-Adress
? (ISP-Gateway-Adress) at 00:0a:b7:c3:62:70 on xl0 [ethernet]Ping output:
PING ISP-Gateway-Adress from MY-PUBLIC-IP: 56 data bytes
64 bytes from ISP-Gateway-Adress: icmp_seq=0 ttl=255 time=2.595 ms
64 bytes from ISP-Gateway-Adress: icmp_seq=1 ttl=255 time=3.502 ms
64 bytes from ISP-Gateway-Adress: icmp_seq=2 ttl=255 time=2.801 ms–- ISP-Gateway-Adress ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.595/2.966/3.502/0.388 msRebooting does not help.
Waiting for next update. Report post-test. -
Something must not have come through in what you pasted, because I didn't get that your WAN appeared offline from what you showed.
It's may just be the status page being misreported/misinterpreted since the backend changed, and not a real failure.
-
Back to a previous update : 20090527-0135.gz
Accurately ascertained : WAN ONLINE in Load Balancer and in Status -> (System=DashBoard 0.7.7)… !
Again updated to 20090528-2026.gz
Convinced - All just as I wrote above.
Now I am sure - In version 20090528-2026.gz is something wrong.Waiting for next update !!!
-
So to clarify, does it show the status incorrectly on the Staus > Load Balancer screen as well as the Dashboard, or is it incorrect in only one of those places?
I know the Dashboard hasn't been updated to take the new apinger code into account, but I can't say for certain about the other status pages.
-
If observed, the status indicated in the warning wan .. but in deskripsinya explain that there is no loss of load balancing, Failover, exp ;;; "" Warning " Delay: 29.964ms, Loss: 0.0%. "
I do not see the awkwardness in connection with the internet's on the Dashboard. -
Please try this again with an update from today. I've been told that there may have been a missing binary that was critical to load balancing on last night's snapshots.
-
That and there was a typo in the code which set the latency low watermark to 10 ms which was incorrect.
Current 1.2 snapshots should now work correct.
-
Yes - working correctly.
But this is not all of the improvements - in my opinion :
Dashboard appeared without rebooting !? (Status -> System…)This is not all the changes, improvements ?
There are a major changes in Firewall log... ? (diag_dns, easyrule)
