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.
I can get it to work so long as I plug the ethernet cable into my laptop then ssh into the desktop then plug the router in the middle. I cant directly ssh into the desktop via the router without first doing it directly.
Is this to with DHCP ?
The belkin router is a FD1401 v1 (Not a router supported by dd-wrt)
I have tried to access the admin page by connecting the router to my laptop and going to 192.168.2.1 which is the adress the manual suggests.
what are you doing to make the systems work directly? Where is the IP addressing coming from? you're applying it manually? Are you not doing anythign at all? I'm not sure how much stuff might happen by magic these days via NetworkManager, are you put on a 169.254 IP address? (ifconfig -a when connected will show you) If all clients are configured to use DHCP, which would be default, and the router IS prodividing a DHCP service, which would be a default again, then eveything should just work. Make sure you can ping the router IP from each device first though before trying to go between two machines. That'll highlight which connection has the issue, if it's only one.
Why are you plugging and unplugging the laptop's nic device? Are you really saying that you can't share files with a desktop computer, from the laptop when using the wireless device? The router may have wireless isolation enabled by default. If so, you simply need to disable it in the web interface. You may need to look up the default user and password for the router. If this was changed by the previous owner, you may need to factory reset the router.
What is the IP address of the desktop, with the wired connection? The first 3 octets of the router's web interface will probably be the same. So if the desktop has an IP address of 192.168.1.100, the router is probably at 192.168.1.1.
A first choice would be to see if you can get documentation on that particular Belkin device. You're saying that you have tried to access the admin page for the Belkin, so that encourages me in seeing that you have some understanding of network awareness and network configuration.
I'd try and default that Belkin to it's factory defaults. You say you inherited it, but who knows how it's configured, I didn't even look it up, but some things that are striking my mind are MAC address security, or other forms of security, or even the fact that DHCP have been disabled. Perhaps the former user of that equipment used it in a static address configuration and hence they disabled assignment of network address assignment.
OK, I didn't want to be dismissive/unkind and so I googled for FD1401, it looks like a wireless router. I'd definitely default it so that it will be unsecured for now and then later configure it once you get it working properly. If they have firmware updates, I'd recommend that too.
The other short of it is:
- ifconfig on Linux will show you the IP address information for your system. eth0 is likely the port you'd be looking at. "lo" will be the local loopback and is not what you will be interested in. Here's an example of my ifconfig, where I happen to have two network adapters and I recommend that you try this with only one adapter in the machine until you figure out these problems.
If you're seeing the self assigned address or something, then there's a fundamental problem getting an address assigned for your machine and you need to look at the router to figure out what it's doing.
Cheers for all the support. Iv needed some time to work on your suggestions and come up with a reply.
I still have no idea how to get the router web interface. Iv tried putting the router ip 220.127.116.11 which the manual suggests, into my browser.
ifconfig was a useful command. Iv connected the desktop into the router and then into my laptop and ifconfig gave the eth0 as 192.168.... Which I was not expecting and cant seem to ssh into. I the connected the desktop to the laptop and ifconfig gave 10.42.... Which I can ssh into and survives restarts of both laptop and the desktop.
If I conect the router after ifconfig shows the desktop eth0 as 10.42.. it stays a 10.42... and works fine.
I want to know what causes this and how to prevent it in the future.
Find out how to access the router, maybe a reset somewhere on it will bring it back to default settings. Then look at how each puter is set up. Everything needs to be using DHCP or assign everything a fixed IP. Read the links above.
If you can't find the routers address, You should be able to find what's on the subnet with example (Use your own IP range)
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
There should be a hole somewhere where you can poke a paperclip or similar to reset the router to factory defaults: http://www.dslreports.com/faq/13631
There's not much point messing around with the IP configuration on your laptop and PC until you've got your router in a known-good state where you can access the configuration page on it.