On Fri, Jun 19, 2009 at 5:29 PM, Tom Eastep wrote:
> Tom Eastep wrote:
> > Mikael Kermorgant wrote:
> >
> >> Would anyone have an idea about why this happens ? Is this something
> >> inherent to bridges I have not understood ? Or should I better look at
> >> the switches ?
> >
> > As described in
Tom Eastep wrote:
> Mikael Kermorgant wrote:
>
>> Would anyone have an idea about why this happens ? Is this something
>> inherent to bridges I have not understood ? Or should I better look at
>> the switches ?
>
> As described in Shorewall FAQ 17, you simply need to set the 'routeback'
> option
Mikael Kermorgant wrote:
>
> Would anyone have an idea about why this happens ? Is this something
> inherent to bridges I have not understood ? Or should I better look at
> the switches ?
As described in Shorewall FAQ 17, you simply need to set the 'routeback'
option on br2 in /etc/shorewall/int
> Where can we read your original post? It apparently was not sent to this
> list.
Here it is (was moderated because of attachment) :
Hello,
I this is not a problem with my shorewall configuration but strange
logs that I'd like to understand, so sorry for being a little
offtopic.
I have setup a
Mikael Kermorgant wrote:
>
>
> On Thu, Jun 18, 2009 at 7:10 PM, Mikael Kermorgant
> mailto:mikael.kermorg...@gmail.com>> wrote:
>
>
>
> Would anyone have an idea about why this happens ? Is this something
> inherent to bridges I have not understood ? Or should I better look at
> th
On Thu, Jun 18, 2009 at 7:10 PM, Mikael Kermorgant <
mikael.kermorg...@gmail.com> wrote:
>
>
> Would anyone have an idea about why this happens ? Is this something
> inherent to bridges I have not understood ? Or should I better look at
> the switches ?
>
I just found this in the FAQ which seems