[Gllug] simple lan

[Leigh Mason]

finally sorted!


when i read the output from 'dmesg', the 'eepro100' driver loaded and
detected the hardware but it said that the 'PCI BIOS' has not enabled the
device! so i went into the bios and discovered that the primary IDE adapter
had its 32 bit i/o disabled!

it feels so good to be able to configure something finally and get it
loading  and  working properly! as you might have noticed i'm a linux newbie
and i've   struggled/struggling with many aspects of the os, but i can see
how much this practice helps people to understand and appreciate the
details of what's going on in their system. i'm hooked!


thanks for all the help everyone

leigh



 

> From: Kieran Barry <kieran at esperi.demon.co.uk>
> Reply-To: gllug at linux.co.uk
> Date: Tue, 18 Sep 2001 19:29:24 +0100 (BST)
> To: gllug at linux.co.uk
> Subject: Re: [Gllug] simple lan
> 
> On Tue, 18 Sep 2001, Leigh Mason wrote:
> 
>> hi
>> 
>> i can't cut 'n' paste because i have no method of placing the data onto
>> another medium. (no internet conn' due to winmodem (and i cannot access
>> linux partition via msDOS)). so, i've manually typed the output from the
>> files you mentioned:
>> 
>> ifconfig -a
>> 
>> eth0  link encap:Ethernet HWaddr 08:00:46:07:56:AA
>> inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:11 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:12 errors:0 dropped:0 overruns:0 frame:0
> 
> This says that this interface is recognised, and has sent 12 packets,
> and received 11. This is promising...
> 
> I presume, you pinged this from the Mac?

> Could you type /sbin/arp -a to see if the MAC address on the Mac is in
> there?
> 
>> collisions:0 txqueuelan:100
>> Interupt:9 Base address:0xfcc0
>> 
>> lo   Link encap:Local Loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> UP BROADCAST RUNNING  MTU:3924 Metric:1
>> RX packets:50 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:50 errors:0 dropped:0 overruns:0 frame:0
>> collisions:0 txqueuelan:0
>> 
>> 
>> netstat -rn 
>> 
>> Dest        gateway     genmask         flags   mss    window  irtt   iface
>> 10.0.0.0    0.0.0.0     255.255.255.0   U       0      0        0     eth0
>> 127.0.0.0   0.0.0.0     255.0.0.0       U       0      0        0     lo
>> 
> This means that networking has come up correctly, so the most likely
> suspects now are the cable, or one of the cards working at 10Mb and the
> other at 100Mb. I don't have experience debugging that.
> 
> Does anyone on the list know if it's possible for windows drivers to
> notice a patch cable instead of a crossover, and transmit accordingly?
>> 
>> the mac has web sharing enabled. in the tcp/ip control pannel the connection
>> method is ethernet configured manually - with an ip addr :10.0.0.2 and a
>> mask:255.255.255.0.
>> 
>> the nic is a:
>> intel 8255x-based pci 10/100
>> 
>> i guess that the card is being detected because i have an hardware address
>> appear in the ifconfig output??
> 
> Correct.
>> 
>> Q. do i have to have any network services running on linnux (inetd.d) for a
>> icmp to respond?
>> 
> No
> 
>> thanks 
>> 
> No problem. I'm impressed with you typing that stuff out...
> 
> regards
> 
> Kieran
> 
> 
> -- 
> Gllug mailing list  -  Gllug at linux.co.uk
> http://list.ftech.net/mailman/listinfo/gllug


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug