From: Bjoern Franke <bjo@nord-west.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Connecting through Batman advanced interface
Date: Tue, 01 Feb 2011 13:12:55 +0100 [thread overview]
Message-ID: <1296562375.26635.5.camel@ostrea> (raw)
In-Reply-To: <201101311933.01581.clemens-john@gmx.de>
Hi,
> > I don't think the VPN is the problem here but the fact that you can't
> > bridge an interface running in adhoc mode. Ad-hoc is "lacks" a field in
> > the wifi header which makes bridging impossible.
> > However, I agree with your proposed solution - another router connected to
> > the Ethernet of the wrt54g can solve the issue.
>
> This is not possible in this case (I don´t have another router).
Does Franco have another router which he could connect to the wrt54g?
> Is there onother (maybe harder) way or a hack to do get the same result like
> when bridging two interfaces? Maybe with iptables?
I think this would break our setup.
> Or does anyone know what the status of multiple ssid on wrt54g with kernel 2.6
> is?
Maybe we should ask here:
http://wireless.kernel.org/en/users/Drivers/b43#support
I have no experience with brcm-chips due to I have only a brcm4318 in my
laptop.
regards
Bjoern
--
jabber: bjo@schafweide.org
bjo.nord-west.org | nord-west.org | freifunk-ol.de
prev parent reply other threads:[~2011-02-01 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 22:46 [B.A.T.M.A.N.] Connecting through Batman advanced interface Clemens John
2011-01-29 17:45 ` Bjoern Franke
2011-01-29 18:00 ` Marek Lindner
2011-01-31 18:32 ` Clemens John
2011-02-01 5:49 ` wayne
2011-02-01 10:51 ` Kevin Steen
2011-02-04 15:38 ` Clemens John
2011-02-06 22:18 ` Kevin Steen
2011-02-08 23:37 ` Clemens John
2011-02-01 12:12 ` Bjoern Franke [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=1296562375.26635.5.camel@ostrea \
--to=bjo@nord-west.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.