From: Marek Kierdelewicz <marek@piasta.pl>
To: Yavetskiy Yuriy <yavetskiy@kpi.ua>
Cc: Oguz Yilmaz <oguzyilmazlist@gmail.com>, netfilter@vger.kernel.org
Subject: Re: Transparent http filtering VLAN traffic without being a member of tagged VLANs
Date: Thu, 18 Feb 2010 23:15:28 +0100 [thread overview]
Message-ID: <20100218231528.697221fc@catlap> (raw)
In-Reply-To: <4B7D2461.7010703@kpi.ua>
>Hello.
Hello,
>And what is output of
>ip ro sho 91.93.179.88/29
>?
>If route already exist you must delete it before adding to br0.206.
Yuriy is right to sugest that check.
If "ip ro sho 91.93.179.88/29" won't show anything and you still
can't add route then there's something wrong with kernel or userspace ip
tools.
Best regards,
Marek
prev parent reply other threads:[~2010-02-18 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 20:16 Transparent http filtering VLAN traffic without being a member of tagged VLANs Oguz Yilmaz
2010-02-17 20:55 ` Marek Kierdelewicz
2010-02-18 7:23 ` Oguz Yilmaz
2010-02-18 10:36 ` Marek Kierdelewicz
2010-02-18 11:20 ` Oguz Yilmaz
2010-02-18 11:28 ` Yavetskiy Yuriy
2010-02-18 22:15 ` Marek Kierdelewicz [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=20100218231528.697221fc@catlap \
--to=marek@piasta.pl \
--cc=netfilter@vger.kernel.org \
--cc=oguzyilmazlist@gmail.com \
--cc=yavetskiy@kpi.ua \
/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