> > Install the package tcpdump, and run `tcpdump -i eth0` to get a view of
the
> > packets being sent/received on the eth0 interface. ..
> >
> Thanks for the advice. This time it really shows something!
> The IP setting on computer has no problem. Below is the
> output of 'tcpdump -i eht0':
On Apr 25, Kevin Traas wrote:
>
> Install the package tcpdump, and run `tcpdump -i eth0` to get a view of the
> packets being sent/received on the eth0 interface. ..
>
Thanks for the advice. This time it really shows something!
The IP setting on computer has no problem. Below is the
output
On Jun 6, [EMAIL PROTECTED] wrote
: On Jun 6, Nathan E Norman wrote:
: >
: > ps. Between dmesg, ifconfig, and the proc filesystem you can poke
: > around and get a good idea of what Linux thinks is going on, and how
: > that meshes with what's supposed to be going on.
: >
: Thanks for the suggest
> Can anybody tell me what is the problem if the computer cannot
> receive packets from other computer? I set all the configuration
> file and IP address, hostname seems ok. I can 'ping' myself,
> but not other computers, also I can not ping from other computer
> to mine. I am sure the physical co
On Jun 6, Nathan E Norman wrote:
>
> . oving the NIC to
> IRQ 10 or something, or remove the serial port (this is not always
> possible).
>
On Jun 6, Nils Rennebarth wrote:
> Does ifconfig shows errors? What media does it use (or try to use?)
> AUI, BNC, 10BaseT? This should be printed at load
-BEGIN PGP SIGNED MESSAGE-
On Fri, 6 Jun 1997 [EMAIL PROTECTED] wrote:
>I have disabled the IRQ 3 from bios. this is what I saw in /proc/interrupts
> 3: 455 : NE2000
>Is this correct?
Apparently it receives interrupts. This is ok. A typical sign of a BIOS
robbing the interrup
On Fri, 6 Jun 1997 [EMAIL PROTECTED] wrote:
:On Jun 6, Nathan E Norman wrote:
:>
:> ps. Between dmesg, ifconfig, and the proc filesystem you can poke
:> around and get a good idea of what Linux thinks is going on, and how
:> that meshes with what's supposed to be going on.
:>
:Thanks for the su
On Jun 6, Nils Rennebarth wrote:
>
> Another one to test is
> cat /proc/interrupts
> Often, PnP BIOS'es need to be told to reserve certain IRQ's for non PnP
> cards, otherwise they won't ever see an interrupt coming in.
>
I have disabled the IRQ 3 from bios. this is what I saw in /proc/interrupt
-BEGIN PGP SIGNED MESSAGE-
On Fri, 6 Jun 1997 [EMAIL PROTECTED] wrote:
>On Jun 6, Nathan E Norman wrote:
>>
>> ps. Between dmesg, ifconfig, and the proc filesystem you can poke
>> around and get a good idea of what Linux thinks is going on, and how
>> that meshes with what's supposed to
On Jun 6, Nathan E Norman wrote:
>
> ps. Between dmesg, ifconfig, and the proc filesystem you can poke
> around and get a good idea of what Linux thinks is going on, and how
> that meshes with what's supposed to be going on.
>
Thanks for the suggestions. I check with all these commands.
Here is t
IS the driver for the NIC actually working? Use ifconfig to see if
you're getting packet errors, or if the device is even configured. 0 RX
packets usually means something is bolloxed up in your configuration -
either the driver can't talk to the card because of a hardware conflict,
or it's making
Hi,
Can anybody tell me what is the problem if the computer cannot
receive packets from other computer? I set all the configuration
file and IP address, hostname seems ok. I can 'ping' myself,
but not other computers, also I can not ping from other computer
to mine. I am sure the physical connec
12 matches
Mail list logo
