DebianThis forum is for the discussion of Debian Linux.
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'm trying to set up a local network between one computer running on Debian Etch and another on Ubuntu Dapper. This should be easy enough to do, but neither computer sees the other. Here is the procedure I followed, did I miss something?
In the Debian machine I did system --> networking and changed the properties on eth0 to the following:
IP address: 192.168.0.1
Subnet mask: 255.255.255.0
I validated this and then set up the Ubuntu machine as follows:
I don't know if this is of importance, but when the Debian computer boots in verbose mode, I get a message that DHPDISCOVER is looking at eth1 on 255.255.255.255 on various ports, and fails to find anything. Shouldn't it look on 255.255.255.0? Incidentally, I don't know if this is of importance but before I attempted to set up the network, I got the same message, but rather than looking at eth1 it looked at eth0.
Perhaps I should add that I had managed to establish this connection when both computers were Windows, and I also managed it between Windows and Linux, but since I got rid of Windows I have never been able to connect these two computers.
This problem seems very simple to me, but I haven't found a solution to it by Googling around or by looking at the previous threads on this forum.
Thanks in advance for your help
Firstly the DHPDISCOVER problem shouldn't matter, as you have no DHCP server and you are using static ip addresses.
What happens when you ping the Ubuntu machine towards the Debian machine?
Do you have a firewall that is blocking the packets?
It's very strange this business about eth2. I have never (as far as I know) tried to configure eth2, unless by mistake, and in any case when I do system --> networking, eth2 is listed as being unconfigured.
The two computers are simply connected via a crossover lead.
As for DHCPDISCOVER, if it's not needed, is there a way of stopping Debian from looking for it on boot up? It at least doubles the start up time.
I'll tell you the whole story! I had a few problems when I was installing Debian, as it asked me questions I found difficult to answer about the network. I'm not sure I got them all right as I'm very weak in this area. Also, I had a funny business with the Internet connection not coming on automatically on start up. I played around with it for a while until I got it working. Perhaps I made a mess of everything - it wouldn't be the first time!
As for the Ethernet card business, this has always struck me as odd. As far as I know, there are only two Ethernet cards in this machine. Well, there were last time I looked! But where on earth does eth2 come from? And Debian isn't alone in flagging up eth2 - I also had it on Mandriva and, I think the other distros I've tried on this machine.
My apologies, farslayer, I didn't see your commands at the bottom of your post. Guess that's what comes of my doing too many things at once. Well, here's the Ispci command. I don't know what it all means!
00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS645DX Host & Memory & AGP Controller (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL Media IO] (rev 14)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440-SE] (rev a3)
And here is the result of cat /var/log/dmesg | grep eth:
debian:/home/james# cat /var/log/dmesg | grep eth
eth0: RealTek RTL8139 at 0xdc00, 00:30:bd:bb:43:19, IRQ 169
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth1: RealTek RTL8139 at 0xd800, 00:20:ed:8f:21:36, IRQ 177
eth1: Identified 8139 chip type 'RTL-8100B/8139D'
eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
eth1: link down
ADDRCONF(NETDEV_UP): eth1: link is not ready
Hm, it would appear that eth1 is down. I wasn't expecting that!