If you're using the 9front userspace you might want to throw the
9front kernel's port directory at 9vx and rebuild (I haven't tried
this). Not that that has anything to do with your current problem.
I wonder why it says DHCP failed instead of no success with DHCP.
Can't help you with the tun/tap
On 12/9/20, remyw...@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
Sorry, I should have quoted the errors more carefully.
> I wonder why it says DHCP failed instead of no success with DHCP.
You are right, it does say "no success with DHCP".
> If "0.0.0.0" is too short, the chances are "0.0.0.0/0" may be the valid form.
The exact error is "Invalid address len
"ip link ..." can optionally set or select the ethernet address, which
is indeed 48 bits (6 bytes) long. I can see how that may be linked to
the DHCP failure, but only as an educated guess.
Lucio.
On 12/9/20, remyw...@cs.washington.edu wrote:
> Sorry, I should have quoted the errors more carefu
