Bug 175267

Summary: [pf] [tap] pf + tap keep state problem
Product: Base System Reporter: Nikita <cnik87>
Component: kernAssignee: freebsd-pf (Nobody) <pf>
Status: Open ---    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Nikita 2013-01-13 19:10:01 UTC 
I have problem with PF and tap interface, pf not correctly work with keep state rule.


after opening ssh connection to ip routed to tap in /var/log/messages show this messages:

Jan 14 01:03:03 platforma kernel: pf: loose state match: TCP in wire: 10.6.0.30:44862 192.168.7.11:22 stack: - [lo=1659601007 high=1659599728 win=4326 modulator=0] [lo=0 high=4326 win=1 modulator=0] 2:0 A seq=1659601007 (1659601007) ack=0 len=0 ackskew=0 pkts=12:1 dir=in,fwd
Jan 14 01:03:03 platforma kernel: pf: loose state match: TCP out wire: 192.168.7.11:22 10.6.0.30:44862 stack: - [lo=1659601007 high=1659599728 win=4326 modulator=0] [lo=0 high=4326 win=1 modulator=0] 2:0 A seq=1659601007 (1659601007) ack=0 len=0 ackskew=0 pkts=12:0 dir=out,fwd
Jan 14 01:03:03 platforma kernel: pf: BAD ICMP 5:1 10.6.0.1 -> 10.6.0.30 state: TCP in wire: 10.6.0.30:44862 192.168.7.11:22 stack: - [lo=1659601007 high=1659599728 win=4326 modulator=0] [lo=0 high=4326 win=1 modulator=0] 2:0 seq=1659601007
Jan 14 01:03:05 platforma kernel: pf: OK ICMP 5:1 10.6.0.1 -> 10.6.0.30 state: TCP in wire: 10.6.0.30:44892 192.168.7.11:22 stack: - [lo=3982164082 high=3982164084 win=2048 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=3982164082


pfctl -ss | grep 192.168.7.11
all tcp 192.168.7.11:22 <- 10.6.0.30:44892       CLOSED:SYN_SENT
all tcp 10.6.0.30:44892 -> 192.168.7.11:22       SYN_SENT:CLOSED



and connection with ssh closed after ~ 60 sec

How-To-Repeat: in pf.conf:
vpn_if = "tap0"


block on $vpn_if from any to any
pass  on $vpn_if from any to any  keep state
pass out on $vpn_if all keep state

route cmd:
route add 192.168.0.0/16 10.6.0.2

from 10.6.0.30 open TCP connection to 192.168.7.11:ssh
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-01-14 08:44:16 UTC 
Responsible Changed
From-To: freebsd-amd64->freebsd-net

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:47:30 UTC 
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.