The new release gives the chance to fix important stuff libpcap-0.8.3 suffers. The fresh release of 0.9.3 prevented me filing a bug for 0.8.3 which is the current stable and ONLY avialable version of libpcap in portage and know it is a good opportunity to fix current issues. Precisely, the drop of the "inbound" "outbound" keywords for the ppp protocol in version 0.8.3 is a real pain. If you are a modem/ISDN user for which is no flatrate / traffic volume paid online access available and get a dynamic IP from your provider, DoD is nearly impossible since no reliable idle detection of the link is possible. Todays dial-in pools are flooded with p2p traffic and if you get the ip of a former busy node in the p2p net, huge amounts of requests hit the host. With a dynamically assigned IP, there is NO WAY to install a "active-filter" for the ppp link which considers only wanted traffic to keep the link up without the "inbound" "outbound" keywords, because you can never predict your dynamic ip which is assigned via ppp handshake to construct a filter expression which considers only leaving packets as link activity. I
The new release gives the chance to fix important stuff libpcap-0.8.3 suffers. The fresh release of 0.9.3 prevented me filing a bug for 0.8.3 which is the current stable and ONLY avialable version of libpcap in portage and know it is a good opportunity to fix current issues. Precisely, the drop of the "inbound" "outbound" keywords for the ppp protocol in version 0.8.3 is a real pain. If you are a modem/ISDN user for which is no flatrate / traffic volume paid online access available and get a dynamic IP from your provider, DoD is nearly impossible since no reliable idle detection of the link is possible. Todays dial-in pools are flooded with p2p traffic and if you get the ip of a former busy node in the p2p net, huge amounts of requests hit the host. With a dynamically assigned IP, there is NO WAY to install a "active-filter" for the ppp link which considers only wanted traffic to keep the link up without the "inbound" "outbound" keywords, because you can never predict your dynamic ip which is assigned via ppp handshake to construct a filter expression which considers only leaving packets as link activity. I´ve heard the post 0.8.3-release cvs version of libpcap already got back support for those keywords, I estimate that 0.9.3 has it as well... However, it should be made shure and tested that the new version supports this and if needed patched in. Reproducible: Always Steps to Reproduce: 1. configure a ppp link with "active filter" expression containing "inbound/outbound" keywords 2. pppd could not establish filter because of lacking support for ppp protocol in libpcap 0.8.x Actual Results: no reliable dial on demand for ppp links with dynamically assigned IP Expected Results: reliable line activity detection via active filter expression for ppp links
I've bumped libpcap to 0.9.3. Test it and if that bug persists, submit a separate bug. Thanks.
