From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] limit of if per batman
Date: Tue, 24 Jan 2017 14:39:10 +0100 [thread overview]
Message-ID: <2809895.eiDvevZ9tY@bentobox> (raw)
In-Reply-To: <98a77a75-ac8e-455a-6060-343b9020cd27@viisauksena.de>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Montag, 23. Januar 2017 18:26:59 CET jens wrote:
> somebody told me that for gre there is a limit of 255 per kernel,
> does this also aply for gretap
I've already used over 500 (sry, not 9000) gretap tunnels. And I've just did
the same on Linux 4.9 with gre to test the 255 limit for L3.
for i in `seq 1 255`; do
echo $i
ip link add gre$i type gre local 192.168.2.227 remote 192.168.3.$i ttl 255 dev enp0s31f6
ip link set up dev gre$i
ip link add grex$i type gre local 192.168.2.227 remote 192.168.4.$i ttl 255 dev enp0s31f6
ip link set up dev grex$i
done
At least my Linux kernel was not generating any error messages. Maybe this
limit was removed already?
> and mainly - is there a limit for if i can add to bat0 - since every
> gretap is a "if"
There is no artificial limit added by batman-adv. But transmitting a lot of
broadcasts over 255 virtual links sharing the same physical link
might get interesting (independent of batman-adv).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-24 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 17:26 [B.A.T.M.A.N.] limit of if per batman jens
2017-01-24 13:39 ` Sven Eckelmann [this message]
2017-01-25 2:21 ` jens
2017-01-25 3:02 ` Andrew Lunn
[not found] ` <ba5c036e-e34b-2b43-4df2-bc1c8883eedd@viisauksena.de>
2017-01-25 7:15 ` Sven Eckelmann
2017-12-26 14:19 ` Sven Eckelmann
2018-01-23 12:33 ` Sven Eckelmann
2018-02-03 7:41 ` Sven Eckelmann
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=2809895.eiDvevZ9tY@bentobox \
--to=sven@narfation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox