Apinger is… not very good.
This is why we’ve gone to dpinger in pfSense software v2.3
> On Feb 24, 2016, at 7:27 PM, Joe Laffey wrote:
>
> Hi,
>
> I reported this on the forum a while back. Been having this issue since
> installing version 2.x
>
> We have a dual WAN setup. If I restart apin
Hi,
I reported this on the forum a while back. Been having this issue since
installing version 2.x
We have a dual WAN setup. If I restart apinger then the RTT latency times
are correct, and it seems to ping the selected hosts (one of which is an
alternate host, the other is the gateway). How
On Tue, Feb 23, 2016 at 9:01 PM, Jim Thompson wrote:
> Fun fact, this ’Netflix’ success is using the AES-GCM code that Netgate
> co-developed with the FreeBSD Foundation for use with IPsec.
>
> https://lists.freebsd.org/pipermail/freebsd-security/2014-November/008029.html
>
>
>
> Fun fact #2, a f
Reboots usually happen when irq is shared and/or memory.
On Wed, Feb 24, 2016, 20:17 Espen Johansen wrote:
> You might try to put the wlan card in another slot on the motherboard.
> Also use bios to disable stuff like sound card, unused usb ports, Lpt, com
> ports etc.
>
> On Wed, Feb 24, 2016,
You might try to put the wlan card in another slot on the motherboard. Also
use bios to disable stuff like sound card, unused usb ports, Lpt, com ports
etc.
On Wed, Feb 24, 2016, 20:15 Espen Johansen wrote:
> Remove the wlan card. Then remove config. It sounds like you might have a
> irq or othe
Remove the wlan card. Then remove config. It sounds like you might have a
irq or other resource allocation problem. But without any more details its
hard to say.
On Wed, Feb 24, 2016, 19:51 Sean Pohl wrote:
> Ok. Thank you very much. Any advice on how to get it out of the endless
> boot loop? Or
Ok. Thank you very much. Any advice on how to get it out of the endless
boot loop? Or will my path of least resistance be to simply do a fresh
install again? Many thanks.
On Feb 24, 2016 12:26, "Espen Johansen" wrote:
> Do not bridge and do not use same subnet. If you want lan and wlan to talk
>
Do not bridge and do not use same subnet. If you want lan and wlan to talk
add rules for the subnets to talk to each other.
On Wed, Feb 24, 2016, 19:12 Sean Pohl wrote:
> The problem is an endless boot-loop on my pfSense installation after I
> made one
> change to the WLAN interface.
>
> I have
The problem is an endless boot-loop on my pfSense installation after I made one
change to the WLAN interface.
I have an older x86 32 bit machine with three NICs:
1. On-board Ethernet
2. Ethernet card
3. WLAN 801.11g
I was able to configure the WAN & LAN interfaces just fine. When I enable
