Ah! Could we be homing in on the problem?
There is no line in the interfaces file dealing with a default gateway. Would that be 10.0.0.138 in my case (the address to my modem?). I've already posted it, but here is my current interfaces file (copied from Knoppix): Quote:
|
Your displayed interfaces file is for DHCP addressing not Static IP addresses...
It's difficult to help you if you are going to switch back and forth between static and dynamic addressing every other post.. Your displayed configuration is for Dynamic addressing on Both Ethernet interfaces. With Dynamic addressing your router or DHCP server would assign the Default gateway and DNS servers. your config should work fine for either interface you are using, and BOTH should not be plugged in at the same time. With Static addressing you need to specify every piece of address info yourself, from the IP address, to the Gateway and DNS Servers, etc.. Exactly HOW do you want this setup and working, Static addressing or DHCP ? Which interface do you plan to use ? There is no need to have an interface you are not using try to come up automatically it just slows down the boot process and doesn't get used anyway. |
Quote:
|
lets jump back to Page 1 of this thread then and look at the sample config i posted for you.. .
Code:
it-etch:/usr/src/linux# cat /etc/network/interfaces According to your earlier post (output of lspci) there are actually 2 physical network interfaces on your motherboard, so there should be 2 physical network jacks on the back of the PC. one of them will be eth1 and the other is eth2. so with this information in your /etc/network/interfaces file and the cable plugged into the appropriate physical network interface jack in the PC, your machine should have a Static IP address of 192.160.0.1 and the Other interfaces should be down (because the auto ethX lines are commented out for those interfaces.) It really shouldn't be any more complicated than that... It is really odd that your router is 192.168.0.138 and your PC is 192.168.0.1 those settings are backwards from the default configuration of most routers. Most routers are either 192.168.0.1 or 192.168.0.254. Most routers start handing out DHCP addresses in the range of 192.168.0.100 - 192.168.0.200 but if the information you provided is correct the configuration in this post should work. Another item that is odd is that every time you have DHCP enabled you are showing IP addresses in the 10.0.0.0 network, not 192.168.0.0 . Are you sure your network is configured for 192 address range ? You mentioned you had another PC on the network and it is working fine.. Just for sanity's sake could you post the IP setting of that workstation ? |
Thanks for all your help with this, farslayer. I'm a teacher, and I know how exasperating it can be when a student fails to understand, despite all your efforts! Actually, I've read through all the posts again and I can see that I've learned a lot since the beginning - so thanks once again. Now I need to go away and find some more information to clear this up:
Quote:
Quote:
Quote:
|
Following what I said in the post above, I've just found the following information on the web page of my Internet provider. I don't know if it helps, but here it is:
Primary DNS: 194.117.200.10 Secondary DNS: 194.117.200.15 SubnetMask: 255.255.255.0 Domain name: club-internet.fr On another page, they explain how they attribute the modem IP addresses. Here is my translation: Quote:
|
Do you have a broadband router hooked up between your Broadband modem and the computers ? if you do have a router it would typically assign addresses in the 192.168.0.0 Range.. from what I can see that functionality may be built into your modem...
I'm asking you a lot of questions so I can try and get a clear picture of what is going on and figure out exactly where our disconnect is so we can get you running.. Yes it can be frustrating and at time I wish I had a white board so I could draw a picture it would make explanations so much easier :) it looks like part of the problem is we have been trying to assign an address in the wrong IP range to get you online.. Code:
it-etch:/usr/src/linux# cat /etc/network/interfaces the second computer can then be 10.0.0.2 and so on.. If that works and the PC's are online... we can look at what it will take to make them talk to each other on you local network. |
Sorry, farlayer, that doesn't work!!!:cry: I've tried editing your file to disable eth2 and enable eth1, and I've also edited it to enable both. But as soon as we assign a static IP, the Internet comes down. I'm going to write to my Internet provider to see if there is anything funny about the modem. It'd surprise me, though, as it's very common - and as I said, the network did work under Windows. :mad:
Quote:
|
Great news, farslayer :p :p I've got the Internet working with a static IP! And I've managed to switch off eth1 and eth0! Simple solution - I knew it would be something dumb! The netmask was wrong! 255.0.0.0 and not 255.255.255.0! Next step, configuring the other computer. :D
|
OK, I've just tried configuring the second computer but the two computers don't see each other. I guess this problem will be much more straightforward than the last, though!
Here are the parametres I put in the second computer: Configuration: static IP address IP address: 10.0.0.2 Subnet mask: 255.0.0.0 Gateway address: 10.0.0.1 Host: james1 DNS servers: 10.0.0.1 Search domain: debian. I'm not at all sure about the last two. For this computer they were: DNS servers: debian; Search domain: Ian. Do I need to change these settings on the second computer to read the same as the first? |
I'm going away for a month, and I won't be able to look into this problem until I get back. I'll post a new thread then, as I still can't get these two computers to see each other.
Once again, thanks a lot for your help - I'd never have got this far without it. Cheers James |
All times are GMT -5. The time now is 10:17 AM. |