Re: ipf Kernel Panic log.. w/ Vonage linksys RT31P2, 5.4 Stable, IPF + IPNAT

2005-06-13 Thread Vladimir Botka
Hello, if your Vonage linksys RT31P2 talks H323 try /usr/ports/net/gatekeeper in proxy mode. Cheers, Vladimir Botka On Sun, 12 Jun 2005, Damon Hopkins wrote: I can reproduce this very easily.. I pick up my phone and make a call Current Setup Cable Modem---FreeBSD 5.4 Stable---HUB--Machines

Re: ipf Kernel Panic log.. w/ Vonage linksys RT31P2, 5.4 Stable, IPF + IPNAT

2005-06-13 Thread Louis Mamakos
The Vonage RT31P2 does not talk H.323, and it's not necessary to do anything other than plain vanilla NAT to have it work through a firewall. That is, no port forwarding, no SIP payload re-writing, etc. Just plain vanilla NAT for both the SIP signaling and the RTP payload will be all that's

ipf Kernel Panic log.. w/ Vonage linksys RT31P2, 5.4 Stable, IPF + IPNAT

2005-06-12 Thread Damon Hopkins
I can reproduce this very easily.. I pick up my phone and make a call Current Setup Cable Modem---FreeBSD 5.4 Stable---HUB--Machines \--Vonage Linksys RT31P2 I've tried various nap rules and ipf filter settings.. here are the current mappings and

Re: ipf Kernel Panic log.. w/ Vonage linksys RT31P2, 5.4 Stable, IPF + IPNAT

2005-06-12 Thread Tilman Linneweh
Hi Damon, Am 12.06.2005 um 23:02 schrieb Damon Hopkins: Tracing pid 27 tid 100021 td 0xc15a4180 mcopydata(c17fa400,0,38,c193abc0,0) at m_copydata+0x28 ipllog(0,d3d46bc8,d3d46b50,d3d46b48,d3d46b40) at ipllog+0x1f1 ipflog(105819,c17fa450,d3d46bc8,c17fa400,0) at ipflog+0x18f