Timeline for How to properly set up network interface
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 2, 2018 at 8:58 | vote | accept | OldTimeRambler | ||
Oct 2, 2018 at 8:58 | answer | added | OldTimeRambler | timeline score: 0 | |
Sep 6, 2018 at 13:55 | comment | added | OldTimeRambler | Yes I can ping 8.8.8.8. When I type ping -I eth1 google.com, I get the same error. I defined the eth1 interface in OVM's web interface, but the problem still persists. nmcli is not installed and I cannot install it, because I don't have access outside my own network. One thing to mention: When I plug the lan cable in the build-in box, I can access the internet. | |
S Sep 6, 2018 at 9:11 | history | suggested | Dirk | CC BY-SA 4.0 |
clarify OMV
|
Sep 6, 2018 at 1:20 | comment | added | Ingo | From where do you ping? From the DHCP subnet behind eth0, or from subnet 192.168.0.0/24 behind eth1? Can you ping 8.8.8.8? | |
Sep 6, 2018 at 0:36 | comment | added | RubberStamp |
After installing OMV and playing around a bit, it looks like the network configuration is manageable through the web interface which should be available at the unit's IP address in your favorite browser. ping raspberrypi.local should respond with the unit's IPv4 address. The underlying default networking is performed via Network Manager... there's a command line interface nmcli and here's how to setup a static address using nmcli
|
|
Sep 5, 2018 at 22:29 | comment | added | RubberStamp |
You're probably missing nameservers ... cat /etc/resolv.conf ... There are numerous methods of assigning namesevers. I'm unfamiliar with OMV's default networking behavior. However, from the image file it looks like they may be using network manager.
|
|
Sep 5, 2018 at 21:43 | review | Suggested edits | |||
S Sep 6, 2018 at 9:11 | |||||
Sep 5, 2018 at 21:40 | review | First posts | |||
Sep 5, 2018 at 21:44 | |||||
Sep 5, 2018 at 21:35 | history | asked | OldTimeRambler | CC BY-SA 4.0 |