Missing eth0 when changing type of networking under VirtualBox
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There has been a modification to change the naming convention of the ethernet ports to differentiate between on-board and PCI NICS. P2P1 stands for p<slot#>p<port#> (for PCI NICS), and ethX has benn changed to emX for on board NICS. You can change this back to ethX by removing the package biosdevname and reconfigiguring the /etc/udev/rules.d/70-persistent-net.rules (Red Hat - Fedora may be a little different) to say ethX rather than p2p1. I believe a restart is required for this change to take effect...at minimum, a service netowrk restart. I have read that you can alos override this by adding biosdevname=0 to the grub.conf, but I have not tested this myself. Here is a link to the WIKI regarding these changes:
Well, the reason that they will not currently talk to one another is that they are in two different networks, and if they do not hava gateway, they do not how to get out of or back into their own networks. If these machines are running on the same host, I woulod suggest putting them in the same network unless they are in seperate networks for a reason. If you want either of these machines to access the internet, they will need their own individual gateways set. By the IP address, they LOOK like they are in the same network, but the subnet mask tells what networks they are REALLY in.
UBUNTU - 255.255.254.0 (this is a /23 subnet)
Fedora - 255.0.0.0 (this is a /8 subnet)
If you give both machines the same subnet mask, they will talk to each other. They will not talk to the DNS (or internet) without a gateway.
If you give both machines a gateway, they will talk to each other and the internet, even though they are in different networks (different subnet masks).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.