public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: axel <axel@notmail.org>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] freifunk-batman-de (0.73 "vampimated")
Date: Fri, 12 Jan 2007 22:10:31 +0100	[thread overview]
Message-ID: <200701122210.31995.axel@notmail.org> (raw)
In-Reply-To: <BAY123-F16148B561C214A87986E31C9B00@phx.gbl>

Hi,

I also believe hard coded address ranges should not be, but despite that I 
would like to ask whether it would be possible for you to move over to the 
105 address range. This would also help to once link the clouds together.

Another point is, that there is also a batman-experimental project in 
development which comes up with some new features to measure link quality and 
apply strange routing metrics and I thought that in case it would ever be 
employed it could use the 103 address range to avoid routing conflicts.

best regards,
axel

On Friday, 12. January 2007 18:27, Felix Bolte wrote:
> but the output of "ip route" is still hardcoded to an 105.* address range
>
> can you fix this in the next version? we use 103.* ... you should already
> know ... but in general it is better to make the fiilter dynamic, referred
> to the used network

  reply	other threads:[~2007-01-12 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  6:40 [B.A.T.M.A.N.] freifunk-batman-de (0.73 "vampimated") Lui
2007-01-12 17:27 ` Felix Bolte
2007-01-12 21:10   ` axel [this message]
2007-03-31  4:49 ` [B.A.T.M.A.N.] Relaese: freifunk-batman_0.83.ipk Lui
2007-03-31  8:43   ` bh
2007-04-06 15:18     ` BlaXwan
2007-03-31 15:15   ` Lemonde

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=200701122210.31995.axel@notmail.org \
    --to=axel@notmail.org \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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