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!
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.
Via an Ethernet cable, usually blue. If you really want to, you can make your own cables. Google 'ethernet cable crimping' or the like.
The plugs on an Ethernet cable are nearly the same as telephone (RJ-45?) plugs (at least in Australia), except wider.
Another benefit (you may call it an annoyance) is that the router will act as a basic firewall, only routing certain ports through to the LAN, and dropping the rest. This means, however, that if you want to let an outside computer connect to yours on a different port, you need to explicitly route that port to your PC. For example, I was setting up Remote Desktop on one of my PCs. It uses port 3389. So I had to login to my router (via the browser-based management, standard on almost all routers) and tell it to forward all traffic on public port 3389 to port 3389 on my PC (10.1.1.4).
As I understood it from Egag, the cable plugs into the telephone network at one end just like a modem (or a telephone or fax). But what kind of port does it plug into in the computer? A USB port or what?
|_| <-- Phone Jack
| <-- Phone Line
| ROUTER |
|\____Ethernet Jack (usually 4 of these)
|<-- Phone Line
| Ethernet Card (possibly inbuilt on motherboard)
| PC |
I apologise for my awful ASCII drawing. Basically You connect the modem to a phone jack, just like the one you put a phone in, and the other end of that cord into the router (it has one ports different from the rest, this is for the phone line). On the other side, one end of the Ethernet cable goes into one of (usually) 4 ports on the router, and the other end goes into a "Network Interface Card" (usually abbreviated to NIC) in a PCI slot in your PC. Sometimes this NIC is built into your motherboard and therefore the cable can just go straight into the appropriate connector.
Like I said earlier, this is a much better setup for the purposes of protection.
i just noticed one little problem with your drawing.
the cable going from your router to your ethernet card is ethernet cable not "phone line"
Also some routers have firewalls. not all have one you can buy one without it. you don't find many modem/router combos out there esp for $10. Usually what you do is you buy a router (linksys D-link are some popular brands) You set it up like this:
1)phone jack in wall
------ethernet cable(usually blue) plugged into the ethernet port labled "uplink" or something similar in back of router
------ethernet cable plugged into one of empty ports in back of router(not the uplink, thats for your modem)
4) your computer(via a network interface card) basicly a pci card witha ethernet port and 2 blinking lights for activity. again sometimes this is on your mother board
Okay, I've gone out and bought an ethernet router (which cost more than the operating system...) but I can't get it to work either. All the manuals tell me different things I ought or ought not to set up for it, while some other postings on this forum have said you don't really need to set anything up at all.
Now I'm completely confused. Following what seemed to be authoritative advice, I changed some of the settings to what appeared to be correct. Maybe I should have left well alone?
On the Suse/Novell forum on this site I have requested advice on configuring DHCP, but I'm no longer sure that's what I need. But I don't know where else to begin.
Anyone got any advice how I can begin to unscramble the situation?!
I've bought a Netgear DG632, which seems to be from Texas Instruments. I tried configuring the computer as the instructions told me - but they told me to configure different things in different ways. Hence the present muddle. ("They" are the router's instructions and manual, the Suse Linux manual and a Teach Yourself book on Linux.) A couple of people on other web forums gave me advice on how to un-muddle it, but it still hasn't got me connected.
I'm beginning to wonder if I'll have to uninstal Linux and start all over again. I hope it doesn't come to that. God only knows how many hours this has all taken me, if I include all the troubles I had with a hard disk breakdown and an apparently faulty Windows reload by the manufacturer (or was it a virus?) before this...
that modem has got good references.
i read : " installs itself...; very easy...; ...etc "
i think first you must setup the eth. conn. to your modem.
check with " # ifconfig " if you see an eth0 interface....
if so , try to ping your modem ( make sure it has power ) like " ping. <ip-adress-of-router/modem> "
Good references: well, the box looked convincing as I had to pay twenty pounds more for it than two others that were on offer. It has a well organised and comprehensive manual on a CD, which you can download in pdf format.
bash: syntax error near unexpected token 'newline'
By the way, I can get into the router with the 192.168.0.1 entry on the browser now. However, I didn't complete that task as I thought I'd made a mistake and I couldn't see how to backtrack to correct it. But now when I try to get back in and I put in my passwords, it says "Authentication failed". Do you know if there's anything I can do about that? Or is there another way round it?
Still, the fact I've got that far shows that I've made big progress since my rather bleak assessment earlier. It's great to have all this help around just when you need it most!