Ethernet Bridge development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: linux@arcoscom.com
Cc: lartc@mailman.ds9a.nl, netfilter-devel@lists.netfilter.org,
	netfilter@lists.netfilter.org, bridge@osdl.org
Subject: Re: [Bridge] Multilink + bridge + nat problem
Date: Thu, 22 Mar 2007 12:11:54 +0100	[thread overview]
Message-ID: <4602647A.1030202@trash.net> (raw)
In-Reply-To: <55003.195.55.244.106.1174552139.squirrel@www.arcoscom.com>

ArcosCom Linux User wrote:
> Any help please?

Please attach your scripts, your mailer wrapped the lines which
makes them pretty unreadable.

  reply	other threads:[~2007-03-22 11:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 22:57 [Bridge] Multilink + bridge + nat problem ArcosCom Linux User
2007-03-22  8:28 ` ArcosCom Linux User
2007-03-22 11:11   ` Patrick McHardy [this message]
2007-03-22 22:24   ` [Bridge] Multilink + bridge + nat problem [with attached txt files] ArcosCom Linux User
2007-03-25 22:55     ` [Bridge] [LARTC] " ArcosCom Linux User

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=4602647A.1030202@trash.net \
    --to=kaber@trash.net \
    --cc=bridge@osdl.org \
    --cc=lartc@mailman.ds9a.nl \
    --cc=linux@arcoscom.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --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