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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello,
I know that there are different styles of networks. I'm considering attempting to put in a very basic, simple, and small local area home network... which style or type should I use and what points should I watch out for in putting one in? Also what kind of hardware and software do I need to install on it?
Thank you
a simple approach would be to just use the 4port / wifi router that your ISP gave you.
- plug any Desktops into some of those ethernet ports,
- connect the other things via the wifi connection.
the Windows based ones will detect each other & connect in a simple network.
- Linux ones should not need very much configuration, to get them networked, as well.
if you have a wifi connected printer, then connect that via usb to one desktop,
and use it's wifi connection for the rest of the devices.
Almost everyone uses tcp/ip. It is almost defacto standard on common OS's. The hardware is almost always built into the home computers. So, you only need some way to attach the computers.
I use homeplugs but many people use wireless or dedicated wires.
If all your computers have ethernet. And are younger than 2008. You just need ethernet cables to connect two computers. And potentially multiple NICs or a multiport hub if you have more than two computers. Before 2008 the MDI-X standard wasn't well adopted or didn't exist and you might need a cross-over cable to connect two computers directly. Otherwise cables and something like an asus rt-n12 should get you a basic home network. It's also nice in client bridge mode to act as a wifi dongle that you attach to with ethernet.
There's basically three things to be familiar with as any one that is not setup or setup in a non-productive state can prevent your network from working. You have your interface, a route, and a firewall.
# ifconfig -a
(without the -a it only lists configured interfaces)
# route -n
(there's also netstat -r)
# iptables-save
(it doesn't actually save, but lists the current rules as they would appear in the save file)
# ifconfig -a
(without the -a it only lists configured interfaces)
# route -n
(there's also netstat -r)
Sorry to nitpick, and it might be off-topic. I agree that these are the most important commands, but the venerable 30 years old ifconfig, route and netstat are on the way to retirement. As an example, Centos/Redhat 7 doesn't have ifconfig anymore. Instead use
Code:
# ip addr
# ip route
The first lists your network interfaces, their status and MAC and IP addresses.
The second lists your network routes.
The replacement for netstat is ss (socket status); not sure if it has a -r option.
Last edited by berndbausch; 07-12-2015 at 09:31 PM.
I use homeplugs but many people use wireless or dedicated wires.
It may be worthwhile pointing out that wireless doesn't work well in some homes, and some people report health issues (I used to laugh about it, but a medical doctor friend of mine who is not so easily fooled by new-age assertments has exactly this problem). If you can't pull cables through your house, Powerline (or Homeplug as you call it) can be an excellent alternative. You can even use all of these technologies at once.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.