PF issue since 11.2-RELEASE

ASV asv at inhio.net
Thu Jan 31 20:44:15 UTC 2019


On Thu, 2019-01-31 at 12:22 +0100, Kristof Provost wrote:
> What does pflog show?
00:00:00.000000 rule 25/0(match): pass in on lagg0: 212.83.XXX.XXX.5441 > 100.100.10.XXX.5060: SIP: REGISTER sip:100.100.10.[!sip]
00:00:48.499578 rule 25/0(match): pass in on lagg0: 212.83.XXX.XXX.5457 > 100.100.10.XXX.5060: SIP: REGISTER sip:100.100.10.[!sip]
00:00:48.182323 rule 25/0(match): pass in on lagg0: 212.83.XXX.XXX.5449 > 100.100.10.XXX.5060: SIP: REGISTER sip:100.100.10.[!sip]
00:00:47.866652 rule 25/0(match): pass in on lagg0: 212.83.XXX.XXX.5477 > 100.100.10.XXX.5060: SIP: REGISTER sip:100.100.10.[!sip]
00:00:47.801770 rule 25/0(match): pass in on lagg0: 212.83.XXX.XXX.5484 > 100.100.10.XXX.5060: SIP: REGISTER sip:100.100.10.[!sip]
00:00:48.091841 rule 25/0(match): pass in on lagg0: 212.83.XXX.XXX.5594 > 100.100.10.XXX.5060: SIP: REGISTER sip:100.100.10.[!sip]

By the way, among my tests I've discovered that connectivity issues re-
occur as soon as I mix network ranges and IP addresses within the same
table (not even pf restart seems to make it work properly again). I
used to have a script to populate a separate table with the spammers
and from time to time I was adding network ranges when multiple (many)
IP addresses within the same range were bombing me so I know it worked
pretty well .... even when IP addresses were overlapping already
specified ranges.

Ex.
120.30.0.0/24
213.156.32.2
.........
.........

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20190131/ba93c2b7/attachment.sig>


More information about the freebsd-questions mailing list