It seems to have been solved.
-my setting now:
kernel:
vfs.read_max=128
kern.ipc.somaxconn=4096
kern.ipc.soacceptqueue=4096
kern.ipc.nmbclusters=100
squid:
quick_abort_min 0 KB
quick_abort_max 0 KB
log_icp_queries off
client_db off
buffered_logs on
half_closed_clients off
memory_pools off
Thanks for the clarification.
The issue I was referring to is AVR-54 in that same spec update. "System May
Experience Inability to Boot or May Cease Operation” I didn’t see a way a BIOS
update could resolve that issue! But I’m really glad to read that my box
doesn’t use the LPC bus at all. That
One more time: there is only so much I can say about the issue. Richard
Relph's message is inaccurate, but I can not describe why or how.
Specific to the subject of this thread: The coreboot (it's not really a
BIOS, and yes, I'm splitting hairs) update addresses a Intel-issued
"specification cl
Google “cisco intel atom issue” for some of the coverage of the problem. The
symptom appears to be that on a reboot (power on? cold reset? warm reset?) the
Atom may not generate LPC clocks… kinda fatal. But it seemingly doesn’t happen
in the course of normal operation.
Richard
> On Mar 21, 201
Time to do a pcap, and see what's actually happening. Look in the SIP
session description (SDP) and see what IP addresses the client is
telling the other side to communicate with. Divide and conquer.
On 3/21/2017 5:42 AM, Martin Fuchs wrote:
what really irritates me is the fact (tried it
Note despite the thread subject, the affected models are:
SG-2220
SG-2440
SG-4860
SG-8860
SG-4860-1U
SG-8860-1U
However, what is the symptom? We have a handful of these in service at various
clients but have not noticed any issues that we're aware of.
--
Steve Yates
ITS, Inc.
-Or
Topic: SG-2440 bios upgrade:
https://forum.pfsense.org/index.php?topic=127418.msg703237#msg703237
On Mon, 2017-03-20 at 19:49 -0500, Richard A. Relph wrote:
> OK, now you guys have me curious…
>
> I have a Netgate SG-2440 purchased directly from Netgate. I’ve
> received no emails. I don’t fre
what really irritates me is the fact (tried it just now) that using it over
OpenVPN instead of IKEv2 it works...
any idea ?
i'm gonna look over it again...
Von: List im Auftrag von Martin Fuchs
Gesendet: Dienstag, 21. März 2017 10:45:34
An: pfSense Support an
no change with sipproxd installed...
very strange...
Von: List im Auftrag von Martin Fuchs
Gesendet: Dienstag, 21. März 2017 10:44:36
An: pfSense Support and Discussion Mailing List
Betreff: Re: [pfSense] SIP through IKEv2-tunnel
since it's only one client i did
I think so, too, that's what confuses me.
Internet -> Router -> (NAT: IPSec, OpenVPN) pfSense
so the SIP-Clients would tunnel trough the the router, terminate with the
pfSense and the unencrypted packets are sent back to the router (which hosts
the PBX).
In my opitnion it should work, too..
since it's only one client i did not think about it but it's worth a try...
Von: List im Auftrag von Eero Volotinen
Gesendet: Montag, 20. März 2017 11:10:56
An: pfSense Support and Discussion Mailing List
Betreff: Re: [pfSense] SIP through IKEv2-tunnel
maybe yo
Hi !
No possibility to disable STUN on the SIP client.
Von: List im Auftrag von Rosen Iliev
Gesendet: Montag, 20. März 2017 19:51:26
An: pfSense Support and Discussion Mailing List
Betreff: Re: [pfSense] SIP through IKEv2-tunnel
Hi,
Have you try to disable th
12 matches
Mail list logo