Hi,
I have some questions about IP/ATM client ( atmarpc.sys) driver which
implemented Windows 98SE and 2K.
- It is a protocol driver or intermediate driver ?
- According to my research (used “dumpbin.exe” utility to check NDIS
functions imported in atmarpc.sys)
It is a protocol driver. But Microsoft documentation nowhere mention
about what type of driver it is.
- If it is protocol driver the following statements are valid ?
- Every IP packets from TCPIP.SYS driver goes through atmarpc.sys
client.
- Protocol drivers bind each other.
- How atmarpc.sys determine there is a new IP address so need to get ATM
Address and create a new VC.
Thanks in advance.
Regards,
Jey Armugam.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> 1. It is a protocol driver or intermediate driver ?
- According to my research (used “dumpbin.exe” utility to check NDIS
functions imported in atmarpc.sys)
It is a protocol driver. But Microsoft documentation nowhere mention
about what type of driver it is.
It is linked to NDIS as a protocol driver and as a “custom ARP” to tcpip.sys
- Every IP packets from TCPIP.SYS driver goes through atmarpc.sys
client.
- Protocol drivers bind each other.
tcpip.sys and atmarpc.sys communicate by using the undocumented interface of
“custom ARPs”.
atmarpc.sys is an add-on for tcpip.sys which implements the ARP
functionality (mapping IP addresses to ATM ones) over ATM.
- How atmarpc.sys determine there is a new IP address so need to get ATM
Address and create a new VC.
IIRC atmarpc.sys also needs a server part running somewhere on the ATM
network. Looks like the protocol of their interaction is described in the
ATM world.
Max
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com