| lupi | hi guys. I need help on configuring netplan. my vm's network suddenly went down after restarting. i was trying the troubleshooting section in netplan.io and generate does not seem to "generate" the files? /run/netplan does not exist | 14:13 |
|---|---|---|
| schopin | lupi: does `netplan get` return your config? | 14:14 |
| lupi | yes | 14:15 |
| lupi | it is similar to the first example here: https://netplan.io/examples/ | 14:15 |
| slyon | lupi: /run/netplan is not supposed to exist. The generated files should be in /run/systemd/network and/or /run/NetworkManager/ | 14:16 |
| lupi | slyon: I see. so it is there. I wonder why I can't get an ip from dhcp though | 14:16 |
| slyon | lupi: could you share/pastebin your netplan config? | 14:27 |
| slyon | does static IP work (i.e. is the DHCP server working correctly)? is there another dhcp-client running in the background? ... those are all common scenarios for the issue you describe | 14:28 |
| lupi | slyon: another dhcp client? none afaik. dhcp server is the same as the one I am currently on (host). vm is guest on this host and has its network bridged to it. maybe I should try static ip again. | 14:31 |
| lupi | https://0bin.net/paste/ulxfgK5k#1mJhLa7WRtk4hL+DZBJdOQrsRpssGOYtjjjpgQpnPeC line 4 is the config file | 14:31 |
| slyon | Thanks! This is a very basic config using systemd-networkd. and networkctl tells us that the enp0s3 interface is still configuring... | 14:33 |
| slyon | could you try "networkctl reconfigure enp0s3" and "networkctl forcerenew enp0s3" ? and also check "journalctl -u systemd-networkd" if there is anything interesting in there? | 14:34 |
| lupi | oh gimme a sec. currently trying static config if that works | 14:35 |
| slyon | the config is very simple and should work... are you sure your bridge is working as expected? | 14:35 |
| lupi | yeah that's what i am wondering right now. this was working before btw. it suddenly went bad when I restarted it. | 14:35 |
| lupi | slyon: so static ip does not seem to work. it has an ip but I cant ping the gateway itself (192.168.1.1). | 14:42 |
| lupi | the host <-> vm can ping each other thou | 14:43 |
| lupi | thanks btw. seems like the problem is virtualbox itself. tried a fresh install of ubuntu and rocky and they all cant get an ip for some reason | 16:42 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!