Timeline for Network unreachable while tftp on a virtual machine. What config should I add?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7, 2022 at 8:00 | vote | accept | Chan Kim | ||
| Jul 7, 2022 at 8:02 | |||||
| Apr 5, 2022 at 8:25 | answer | added | Chan Kim | timeline score: 0 | |
| Mar 25, 2022 at 14:51 | comment | added | Chan Kim | @dirkt Thanks for helping. I added some in my post (ADD2) . | |
| Mar 25, 2022 at 14:50 | history | edited | Chan Kim | CC BY-SA 4.0 | added 401 characters in body |
| Mar 25, 2022 at 12:51 | comment | added | dirkt | I would have expected the -device e1000 to show up as eth0 or similar, and it doesn't. Did you include the driverstack for this device in your kernel? What does dmesg say? | |
| Mar 25, 2022 at 9:42 | comment | added | Chris Davies | Network is unreachable is a typical routing error. Do you have a route to 129.254.32.30? | |
| Mar 25, 2022 at 9:18 | comment | added | Chan Kim | I've added some information. Thanks! | |
| Mar 25, 2022 at 9:18 | history | edited | Chan Kim | CC BY-SA 4.0 | added 724 characters in body |
| Mar 25, 2022 at 8:18 | comment | added | dirkt | Do you have static IPs on both VM and host, or DHCP client on VM and DHCP server on host working? Is your kernel complete enough you can log into the VM and debug? If yes, what does ip addr and ip route get my_ip_addr say? | |
| Mar 25, 2022 at 8:11 | history | edited | Chan Kim | CC BY-SA 4.0 | added 439 characters in body |
| Mar 25, 2022 at 2:01 | history | edited | Chan Kim | CC BY-SA 4.0 | added 783 characters in body |
| Mar 24, 2022 at 22:42 | history | asked | Chan Kim | CC BY-SA 4.0 |