Receiving problem in Realtek RTL8139D(L) network card driver implementation

I am a newbie to the device driver developement in Linux. I am using
Redhat9( linux kernel 2.4.20). I hav written a driver for Realtek
rtl8139D network card. I am able to activate the device by following
command.

# ifconfig rtl up

However i am setting IP address of network interface 'rtl' outside the
code by using # ifconfig rtl 192.168.0.30 -netmask 255.255.255.0

After this, when i ping a host, driver saying transmission of ICMP
packet was successful which I checked by TransmissionOK bit in
Interrupt Status Register of device( which prints text "TxOk" for
successfull transmission in interrupt handler) and also incrementing
transmitted packets counter in interrupt handler. But it is giving
error "DESTINATION HOST UNREACHABLE" as follows

# ping 192.168.0.70
icmp packet 1: DESTINATION HOST UNREACHABLE
TxOk
icmp packet 2: DESTINATION HOST UNREACHABLE
TxOk
and giving number of receiving packets counter is zero ( 100% loss in
PING)

as far as receiving code in interrupt handler is concerned, i think
interrupt handler is OK...
Plz point out the problem as i hav been struggling here since 10 days


is it recieving code problem? or setting ip address externally by
ifconfig command ? or any thing else?

.

Relevant Pages

  • Receiving problem in Realtek RTL8139D(L) network card driver implementation
    ... I am a newbie to the device driver developement in Linux. ... After this, when i ping a host, driver saying transmission of ICMP ... successfull transmission in interrupt handler) and also incrementing ... icmp packet 1: DESTINATION HOST UNREACHABLE ...
    (comp.os.linux.development.system)
  • Receiving problem in Realtek RTL8139D(L) network card driver implementation in Redhat Environment
    ... I am a newbie to the device driver developement in Linux. ... After this, when i ping a host, driver saying transmission of ICMP ... successfull transmission in interrupt handler) and also incrementing ... icmp packet 1: DESTINATION HOST UNREACHABLE ...
    (linux.redhat.misc)
  • Re: Changes in the network interface queueing handoff model
    ... bouncing around for some time is a restructuring of the network interface packet transmission API to reduce the number of locking operations and allow network device drivers increased control of the queueing behavior. ... to "start" output by the driver. ... encapsulation and wrapping, and notifies the hardware. ... The ifnet layer send queue is becoming decreasingly useful over time. ...
    (freebsd-arch)
  • Re: Changes in the network interface queueing handoff model
    ... bouncing around for some time is a restructuring of the network interface packet transmission API to reduce the number of locking operations and allow network device drivers increased control of the queueing behavior. ... to "start" output by the driver. ... encapsulation and wrapping, and notifies the hardware. ... The ifnet layer send queue is becoming decreasingly useful over time. ...
    (freebsd-net)
  • PATCH: Remove file riowinif.h from rio driver (unused file)
    ... -/* The RUP (Remote Unit Port) structure relates to the Remote Terminal Adapters ... - CONFIG is sent from the driver to configure an already opened port. ... - Packet structure is same as OPEN. ... - of the specified port's RTA address space. ...
    (Linux-Kernel)