Re: [9fans] Raw ethernet on 9vx
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 stuff. Maybe at that layer everything is working properly and you just need to do a manual ipconfig(8) inside 9vx. Stuart -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T84b4492f91f2abb6-M44fd4534663000107988045d Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] Raw ethernet on 9vx
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 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
Re: [9fans] Raw ethernet on 9vx
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 length 4 - must be 6 bytes". I tried a few others including 0.0.0.0 but none of them worked. Not specifying this argument however doesn't trigger any complaints. Perhaps it's time to peruse the man pages for ip! But I have to put this down for now and will come back to it this weekend. -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T84b4492f91f2abb6-M6e8f58d18be9957c0e897fb1 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] Raw ethernet on 9vx
"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 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 length 4 - must be 6 bytes". I tried a > few others including 0.0.0.0 but none of them worked. Not specifying this > argument however doesn't trigger any complaints. > > Perhaps it's time to peruse the man pages for ip! But I have to put this > down for now and will come back to it this weekend. -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 71 471 3694 Cell: +27 83 251 5824 -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T84b4492f91f2abb6-M5944f2b488b0b9bec54d4290 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
