On Mon, 3 Nov 2014, Ermal Luçi wrote:
> Probably you forgot to clear the states!
I was under the impression that "state" applied to "keep state" i.e.
outgoing connections.
Nonetheless:
aneurin# pfctl -s state
No ALTQ support in kernel
ALTQ related functions disabled
aneurin# pf
On Mon, Nov 3, 2014 at 10:13 AM, Dave Horsfall wrote:
> On Mon, 3 Nov 2014, Ermal Luçi wrote:
>
> > Probably you forgot to clear the states!
>
> I was under the impression that "state" applied to "keep state" i.e.
> outgoing connections.
>
> Nonetheless:
>
> aneurin# pfctl -s state
> No A
On Mon, 3 Nov 2014, Ermal Luçi wrote:
> - Full ruleset if you can disclose
As attached - no secrets in it. It's somewhat loose because it's behind
another firewall (the ADSL modem) that just lets SMTP/HTTP/SSH-secret-port
through to it (I've masked the SSH port).
> - Make sure with output of
Further to this, it's behaving as though it's parsing the rules but not
actually honouring them. Ring any bells with anyone? If I had an OpenBSD
box to hand then I'd swap it in, but I don't.
--
Dave Horsfall (VK2KFU) "Bliss is a MacBook with a FreeBSD server."
http://www.horsfall.org/spam.ht
On Mon, 3 Nov 2014, Doug Hardie wrote:
> What happens when you run: pfctl -f /etc/pf.conf
aneurin# pfctl -f /etc/pf.conf
No ALTQ support in kernel
ALTQ related functions disabled
pfctl: DIOCSETSTATUSIF
> I suspect you have something in /etc/rc.conf giving a different file for
> the default pf
> On 3 November 2014, at 02:40, Dave Horsfall wrote:
>
> On Mon, 3 Nov 2014, Ermal Luçi wrote:
>
>> - Full ruleset if you can disclose
>
> As attached - no secrets in it. It's somewhat loose because it's behind
> another firewall (the ADSL modem) that just lets SMTP/HTTP/SSH-secret-port
> t
Do the rules show after that? I’ve never seen that last line before. I
suspect it indicates an error of some sort.
> On 3 November 2014, at 14:30, Dave Horsfall wrote:
>
> On Mon, 3 Nov 2014, Doug Hardie wrote:
>
>> What happens when you run: pfctl -f /etc/pf.conf
>
> aneurin# pfctl -f /e
The message " pfctl: DIOCSETSTATUSIF" indicates that pfctl is bombing out
before it actually loads the rules into the kernel. It's a rather unhelpful
message, since it does not point out the source of the problem, though.
A little web searching turned up that most likely your pf.conf references
Also I should have looked further to see this line:
set loginterface egress# Can't remember what this does
I think that statement needs a real interface name, which "egress" probably
isn't.
-Original Message-
From: David DeSimone
Sent: Monday, November 03, 2014 5:13 PM
To: 'Dave Ho
Meant to go to list; I was interrupted by a phone call at the crucial
moment...
--
Dave Horsfall (VK2KFU) "Bliss is a MacBook with a FreeBSD server."
http://www.horsfall.org/spam.html (and check the home page whilst you're there)
-- Forwarded message --
Date: Tue, 4 Nov 2014 11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
greetings,
I see, in list the issue appears from time to time but I was not able to
find the solution for my case, please help me to get working altq on my
igb(4) if it is possible at all
I was trying igb(4) original OS drivers and the one from Intel
11 matches
Mail list logo