NDIS passthru packet redirection

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello,

I want to redirect tcp packets to different destination. For that, I
modified the passthru example from the Win2003 DDK and changed the
destination ip address in MPSendPackets (allocate my own packet and
buffers).

But the packet is routed somewhere else.

In Ethereal the old destination address is showing. I don't know why.

The request always times out.

I disabled task offloading at all (
NdisSetPacketPoolProtocolId(pAdapt->SendPacketPoolHandle,
NDIS_PROTOCOL_ID_DEFAULT); in PBindAdapter
and
Status = NDIS_STATUS_NOT_SUPPORTED in MPQueryInformation)
and calculate the ip header checksum. Do I need to calculate the tcp
checksum or pseudo-header checksum too?

Does anyone know, why Ethereal shows the original destination ip address?
What can I do to make the redirection working?

--
Best regards,
Mathias



.

Relevant Pages

  • Re: UDP error handling
    ... >> the checksum of a UDP packet that was received corrupt because it didn't ... > know the application protocol. ... as source or destination in some cases) or it make 'recognize' the protocol ... > of a received packet before doing the header rewrite. ...
    (comp.unix.programmer)
  • RE: Transfer a sending packet to upper TCP/IP protocol layer in IM
    ... source and destination MAC addresses are the same for both IP versions. ... the destination NIC of IPv6 packet is the same as the destination NIC of my ... encapped IPv4 packet. ...
    (microsoft.public.development.device.drivers)
  • Re: TOE brain dump
    ... primarily over ATMish core networks. ... "if you can't find header address ... the flow, if you can find a VC from cache, send the packet there" ... destination node address selector bits in header, ...
    (Linux-Kernel)
  • Problem Modifing the NDIS packet
    ... I am trying to modify the NDIS packet. ... Calculate the Checksum. ... Modify the Destination MAC address. ...
    (microsoft.public.development.device.drivers)
  • Re: site to site vpn with internal NAT
    ... :interface. ... :192.168.1.101 tries to contact a peer on the remote side, ... so the *destination* IP 192.168.49.x will be changed to the destination ... and since there is a match, the packet will go out over the VPN. ...
    (comp.dcom.sys.cisco)