From: Lucian Cristian <luci@powerneth.ro>
To: wireguard@lists.zx2c4.com
Subject: IS-IS routing protocol
Date: Mon, 12 Aug 2019 19:53:24 +0300 [thread overview]
Message-ID: <37fac6bc-b751-02b3-06f5-61b4823b2a17@powerneth.ro> (raw)
Has anyone managed to configure IS-IS routing with wireguard interfaces ?
I've added multicast address to AllowedIPs (AllowedIPs=224.0.0.0/24) but
when I activate ip router isis on the wireguard interface, tcpdump only
shows: unknown ip 8
expecting to see something like L1 Lan IIH, hlen: 27, v: 1, pdu-v: 1,
sys-id-len: 6 (0), max-area: 3 (0)
or
L2 Lan IIH, hlen: 27, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0)
OSPF, RIP, EIGRP are working fine
Thanks!
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-08-12 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 16:53 Lucian Cristian [this message]
2019-08-12 19:01 ` IS-IS routing protocol Rouven Czerwinski
2019-08-12 19:40 ` Lucian Cristian
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=37fac6bc-b751-02b3-06f5-61b4823b2a17@powerneth.ro \
--to=luci@powerneth.ro \
--cc=wireguard@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).