Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
i'm having a problem with both, arch/bluestar and opensuse 42.2. I'm trying to set up a LAN, having a Raspberry Pi and my Laptop. I also bought a Hub/Switch, connected it.
It says now in the NetworkManager that the network adress is being resolved and ends up in an error message like: the ip-configuration is not available (hopefully rightly translated).
looking at dhcpcd it says, "sending commands to master dhcpcd process. I'm having WiFi and my modem to the internet (enp0s18f2u1u3) connected, too - working without problems.
when doing ifconfig i'm not having any eth0 but an eno0. Is this the same?
when doing ifconfig i'm not having any eth0 but an eno0. Is this the same?
No. Unless you are using one as "alias" to the other.
Quote:
Is my router working proberbly?
You said above that your router/connection is working without problems. Now you ask if the same is working properly.
Let me give you these networking tutorials, they provide a better answer to your questionings. It is better to get acquainted to networking methods and configuration first; from there you can address the forum with a more feasible question. Let me invite you to understand also the basic concept of the OSI model, the internet protocol packet. Possessing this knowledge you will find networking more entertaining. Then download this linux administration tutorial in pdf, turning to page 23 you will find plenty of hints how to tackle your current connectivity problem.
as malekmustaq mentioned i've read all the stuff and used a lot of search engines. Status now is: IP assignment works fine, connection is stable, DNS assigned, now I have probs with NFS:
installed on opensuse the NFS-Server, should work. On the Raspberry Pi i tried to mount and get "Connection timed out". When i try it vice versa, access dinied by the server. What to do?
Device IDs like eno0 do occur for onboard ethernet devices. They are the equivalent of enp names for network cards on the pci bus. See here for example.
edit Oopps, hazel provided a link to this all already, dooh.
To expand a bit on hazel's comment. "eth0 but an eno0. Is this the same"
Linux distro's are converting over to the BSD/QNX style naming convention to help admins more easily identify devices. The old named eth0 could have been any nic in the box where as the newer eno0 is a specific model and location. "Predictable Network Interface Device Names" ethernet onboard 0
For computers on a hub/switch lan connection should be set to static on both unless you wish to run dhcp on OpenSuse to provide Pi an address.
installed on opensuse the NFS-Server, should work. On the Raspberry Pi i tried to mount and get "Connection timed out". When i try it vice versa, access dinied by the server. What to do?
turned off firewall on opensuse but still getting the authorization-error. tried it vice versa (RPi as NFS server, notebook as client), getting
mount.nfs: requested NFS version or transport protocol is not supported
what is strange: when I plug out the network cable, wifi is working. when plugged in, i-net doesn't work.
what is concerned with the eno0 at bluestar linux i thought i've understood. but here it seems to refer to the qualcomm atheros wifi driver (i think kernel modul ath9,) i'm quite sure arch is not understanding my network card (pci). tried to get a driver, but it's written that it should be recognized by the kernel. so arch is out of configuring a network.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.