Did absolutely everything you said except for getting a hub and new cable.
Stranger things happen now. Instead of getting some ping results, I get almost none
from both computers. Running arp now doesn't display anything, it just sits there
stalling. I changed all my IP's from 192.168.0.* to 192.168.1.* (no reason, just
wanted to see if it worked)
Even stranger is that when I try to ping myself using the IP and not the loop back,
it works fine, but if I add the -v flag into ping it doesn't work at all. this is
what happens sometimes(from 192.168.1.1 to itself) Ignore the -f flag, the same
thing happens without it. It's the -v flag that's important (though it shouldn't be)
Nmagination:~# ping -f -v 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
.64 bytes from 192.168.1.1: Echo Request
.98 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst Data
4 5 00 4600 155c 0 0000 40 11 a144 192.168.1.1 216.70.64.1
UDP: from port 1024, to port 53 (decimal)
98 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst Data
4 5 00 4600 175c 0 0000 40 11 9f44 192.168.1.1 216.70.64.1
UDP: from port 1024, to port 53 (decimal)
216.70.64.1 is a DNS server for my isp located in /etc/resolv.conf
this ip is not on the routing table at all so I don't know how it could be trying to
send data there. I have no idea why this happens. Any more ideas? I'm thinking it
could be the cables or the network card. However, when I was running windows the
network card worked fine (could even play Warcraft 2 on IPX) although sometimes it
was a bit flaky (sometimes the computers couldn't see each other until I rebooted
both of them) , but the important thing is that they worked at all. So I think the
cables work ok, but the network card or drivers could be the problem. But your
wisdom in this matter is always appreciated. However if I have to I will try to get
new cables and a hub, but I plan to replace my NIC before doing that.
Tri
Dave Brooks wrote:
> Hmm, something sounds really borked here, but I'm still not quite convinced
> that it's the card. I'll tell you one thing: I don't trust crossover ethernet
> cables. See if you know anyone that might have a hub and a few straight-through
> cables you could hook up. I know that I had some wacko problems like this when
> I tried to use a crossover -- I just ended up buying a $35 hub and a few pieces
> of cable, fixed everything. However, let's verify your current config:
>
> >Nmagination:~# ifconfig
> >eth0 Link encap:Ethernet HWaddr 00:A0:CC:3D:10:CA
> > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:255 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:318 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:5 Base address:0xb000
>
> Hmm. Are you sure you aren't having an IRQ conflict? IRQ 5 is often used
> by soundcards. I like IRQ 9 or 10 for ethernet cards.
>
> >Nmagination:~# route
> >Kernel IP routing table
> >Destination Gateway Genmask Flags Metric Ref Use
> >Iface
> >127.0.0.1 * 255.255.255.255 UH 0 0 0
> >lo
> >192.168.0.0 * 255.255.255.0 U 0 0 0
> >eth0
> >192.168.0.0 * 255.255.255.0 U 0 0 0
> >eth0
> >
>
> Why are there two network routes to the same network? (Was this a typo?)
> If it wasnt (I cant ever say I've ever seen that happen), try removing one.
> Also, add a default route.
>
> >Nmagination:/etc/init.d# less network
> >#! /bin/sh
> >ifconfig lo 127.0.0.1
> >route add -host 127.0.0.1 lo
> >ifconfig eth0 192.168.0.1 netmask 255.255.255.0
> >route add -net 192.168.0.0 netmask 255.255.255.0 eth0
> >
>
> Try adding a host route to yourself (the ethernet address, not loopback).
> Netmask on this will be /32, although it's not really necessary to define
> the netmasks when adding a route. Also, try adding that default route.
>
> >Nmagination:/etc/init.d# arp
> >Address HWtype HWaddress Flags
> >Mask Iface
> >darthpenguin ether 00:A0:CC:3B:22:5E
> >CM eth0
> >
>
> Hmm. Looks like this computer has no problem seeing the other. Does this
> computer show up in the arp table of the other machine, too?
>
> -Dave
--
To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.