Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Also "does not seem to work" is a bit vague ... what actually happens? Does the interface come up, but still get a DHCP IP address? Does it not come up at all? Does it come up with the correct IP but is not able to communicate?
I'll say it again. Look at the differences between the lo and the eth0. You are missing a line. From my minecraft server.
Code:
jason@debian75:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0 # could also be auto eth0
iface eth0 inet static
address 10.0.1.176
netmask 255.255.255.0
gateway 10.0.1.1
dns-nameservers 8.8.8.8 8.8.4.4
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.20.1
nameserver 127.0.1.1
search Home
# OpenDNS Fallback (configured by Linux Mint in /etc/resolvconf/resolv.conf.d/tail).
nameserver 208.67.222.222
nameserver 208.67.220.220
# OpenDNS Fallback (configured by Linux Mint in /etc/resolvconf/resolv.conf.d/tail).
If this is a desktop linux mint install then you need to undo all of this in the /etc/network/interfaces file and use the gui network configuration. Stuff directly in the /etc/network/interfaces can't be managed by the mint networking tool.
If this is a desktop linux mint install then you need to undo all of this in the /etc/network/interfaces file and use the gui network configuration. Stuff directly in the /etc/network/interfaces can't be managed by the mint networking tool.
That or stuff like NetworkManager / Wicd might be managing the device. Use these or the /etc/network interface, one or other but not both
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.