From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Raw ethernet on 9vx
Date: Wed, 9 Dec 2020 16:35:44 +0200 [thread overview]
Message-ID: <CAJQ9t7hb5y+w5HUHOJz5U6K0mdsZ9F2HNSD-FmfmtwbdyJAEjQ@mail.gmail.com> (raw)
In-Reply-To: <16074972350.fF34.73931@composer.9fans.topicbox.com>
On 12/9/20, remywang@cs.washington.edu <remywang@cs.washington.edu> wrote:
>
> [ ... ]
You're brave!
> And several details:
> 1. I had to hard-code the tap device name "tap5" because `ip tuntap ...`
> doesn't return the interface name.
> 2. I have no idea what 0.0.0.0 is, or where to pass it in. (tried `ip link
> set tap5 up address 0.0.0.0` but it complained the address was too short).
>
Even if the interface name is not returned (which usually means the
powers that be have found a more sensible, but totally novel way to
make it available), you should really set
iface=tap5
or even
export iface=tap5
and save a lot of editing later.
If "0.0.0.0" is too short, the chances are "0.0.0.0/0" may be the valid form.
0.0.0.0[/0] is more a place holder (a bit like NULL) than a real IP address.
That said, I am still trying to get my head around creating tap
devices for VMs, in the new lingo (or in the old) even though my
TCP/IP experience goes back to 1990. But then I think the RFCs at that
stage were still below one thousand.
Lucio.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T84b4492f91f2abb6-M77f8e210b7e9e2a9fbbf2e2d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2020-12-09 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 6:26 remywang
2020-12-07 23:38 ` Devon H. O'Dell
2020-12-08 5:55 ` remywang
2020-12-08 7:12 ` Devon H. O'Dell
2020-12-08 7:45 ` Lucio De Re
2020-12-08 9:06 ` Devon H. O'Dell
2020-12-08 9:20 ` David du Colombier
2020-12-08 13:00 ` hiro
2020-12-09 0:34 ` remywang
2020-12-09 7:00 ` remywang
2020-12-09 12:46 ` Stuart Morrow
2020-12-09 14:35 ` Lucio De Re [this message]
2020-12-09 15:29 ` remywang
2020-12-09 19:03 ` Lucio De Re
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=CAJQ9t7hb5y+w5HUHOJz5U6K0mdsZ9F2HNSD-FmfmtwbdyJAEjQ@mail.gmail.com \
--to=lucio.dere@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).