Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Francis GASCHET <fg@numlog.fr>
To: SBlaze <dagent.geo@yahoo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Filtering PPP traffic
Date: Sat, 19 Apr 2003 17:38:58 +0200	[thread overview]
Message-ID: <3EA16D92.2060309@numlog.fr> (raw)
In-Reply-To: <20030418193058.17530.qmail@web40202.mail.yahoo.com>

Yes, but netfilter looks ignoring these packets.

I sniffed them using ethereal. But I've to set manually the "interface" 
to nas0. Ethereal doesn't show it in its list. May be something not 
standard or missing in the eth emulation of this kind of device...
But if I enter "nas0" manually in the "interface" ethereal is able to 
record the data and decodes it.

I think I missed something in iptables working.
I begin to feel that the packets flowing through nas0 disturb iptables 
because they have a 6+2 bytes pppOE header between Ethernet header and 
IP header...
May be a hack is needed in netfilter / iptables...

Any clue ?

F. GASCHET



SBlaze wrote:

>Have you tried filtering on the nas0 device?
>
>--- Francis GASCHET <fg@numlog.fr> wrote:
>  
>
>>Hello,
>>
>>The bridge we use is the kernel patch provided by 
>>http://bridge.sourceforge.net
>>On the card side, we use Ethernet over ATM bridging (RFC 1483/2684 
>>kernel module). It emulates an "Ethernet like" device : nas0.
>>The pppOE daemon sits in the VM where it reads and writes ppp frames on 
>>a virtual eth device created with TAP (http://Vtun.sourceforge.net).
>>The official address is carried by this virtual eth device.
>>The bridge forwards pppOE packets between the nas0 and the tap0 devices.
>>The goal is to use a bridged firewall. That means : a FireWall which is 
>>not visible from the external network.
>>
>>The problem is to be able to filter the pppOE packets that flow across 
>>the bridge.
>>    
>>




      reply	other threads:[~2003-04-19 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 17:53 Filtering PPP traffic Francis GASCHET
2003-04-17 19:55 ` SBlaze
2003-04-18 15:25   ` Francis GASCHET
2003-04-18 19:30     ` SBlaze
2003-04-19 15:38       ` Francis GASCHET [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EA16D92.2060309@numlog.fr \
    --to=fg@numlog.fr \
    --cc=dagent.geo@yahoo.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox