IPfilter
[Top] [All Lists]

RE: ipfilter bug on tunnel interface?

To: <ipfilter@coombs.anu.edu.au>
Subject: RE: ipfilter bug on tunnel interface?
From: "Xu, Chun Gang \(Titan\)" <cxu@alcatel-lucent.com>
Date: Thu, 8 Mar 2007 10:29:29 +0800
Delivered-to: sp-com-lists@consult.net
Delivered-to: ipfilter-list@securepoint.com
In-reply-to: <96C5020C866B5948A698DBF0F3208E4F0FADFB@CNEXC1U01.bj.lucent.com>
References: <6D185254B06A254782931A6D23662908A00CF9@CNEXC1U01.bj.lucent.com> <96C5020C866B5948A698DBF0F3208E4F0FADFB@CNEXC1U01.bj.lucent.com>
Sender: owner-ipfilter@coombs.anu.edu.au
Thread-index: AcdfwILo4haGGXMhTAS+/0x8jXVA8AAAU4rQADJXTrAAJ5WUIA==
Thread-topic: ipfilter bug on tunnel interface?
Hi,

I want to use ipfilter on tunnel interface and run into one strange
issue below.
--------------------------------
System configuration: ipf4.1.10, pfil2.1.7 on SPARC Solaris 9.

Tunnel interface is as below:
ip.tun5: flags=10008d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,IPv4> mtu
1480 index 8
        inet tunnel src 172.16.47.254 tunnel dst 172.16.32.5
        tunnel security settings  esp (aes-cbc/<any-none>)
        tunnel hop limit 60 
        inet 1.1.1.1 --> 2.2.2.1 netmask fffffffc

Rules: 
pass in quick on ip.tun5 proto icmp from 2.2.2.1/32 to 1.1.1.1/32
icmp-type echo keep state
block in log all
----------------------------------

After pushing pfil module into ip.tun5, the first rule works well. Ping
traffic is allowed from 2.2.2.1 to 1.1.1.1.
But after I executed "ifconfig ip.tun5 modlist" or "ifconfig -a"
command, Ping traffic will get down about 20 seconds, then recovers.
And I checked the syslog (syslog was configured before), it's not
blocked by the second rule.

Does anyone have the similar problem or know the reason?
Any suggestions are welcome.

Thanks,


<Prev in Thread] Current Thread [Next in Thread>