jb.lernout

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: TDI ip and bindings changes notifications #5929
    jb.lernout
    Participant

      Well it seems that I get the “????????” string as a device name for the NDIS_WAN_LINE_UP

      But the NDIS_WAN_LINE_UP allows me to easily associate the ip address to the NDIS WAN adapters but how can I do witht the others adapters ?

      If I use the TDI notification, I have to make the association between the interface guid received in the TDI notification and the adapter in NDIS.

      If I use the RequestCompleteHandler :
      The OID_GEN_NETWORK_LAYER_ADDRESSES is not supported by all adapters.

      The OID_PNP_ADD_WAKE_UP_PATTERN seems to be used when the OID_GEN_NETWORK_LAYER_ADDRESSES is not supported and notify for new ip address on an adapter but the OID_PNP_REMOVE_WAKE_UP_PATTERN don’t notify the removal of alternate adress IP, only the main one. As we can have several ip address for the same adapter.

      So, is there a way to associate the interfaces saw in TDI to the adapters in NDIS, or is there a way to obtain the ip address of the adapters directly in NDIS ?

      any answer ? 🙂

      in reply to: TDI ip and bindings changes notifications #5928
      jb.lernout
      Participant

        thanks for your help, I will try to find out a way with the wan line up

        in reply to: TDI ip and bindings changes notifications #5926
        jb.lernout
        Participant

          Does the device name specified in the NDIS_WAN_LINE_UP structure will be the same as the one seen in the ClientPnPAddNetAddress callback function registered to TdiRegisterPnPHandlers ?

          in reply to: TDI ip and bindings changes notifications #5924
          jb.lernout
          Participant

            Correct me if I’m wrong but when you open a connection using an xDSL or ISDN modem, you see a new interface at TDI level.
            But this interface is managed by NDISWAN which makes the translation from Ethernet packets to ppp. So you don’t see any new adapter which is bound to the TCPIP protocol when you open this kind of connection as the packets go to NDISWAN which then transfer the packets to the good miniport.

            So the only adapter opened by TCP/IP when you use multiple WAN connections is NDISWAN and there is no way in NDIS layer to associate the adapters intercepted in NdisOpenAdapter to the interfaces at TDI level.

            in reply to: TDI ip and bindings changes notifications #5922
            jb.lernout
            Participant

              NdisOpenAdapter and NdisCloseAdapter are only called for adapters, it doesn’t work for NDISWAN. So when you add a new interface which uses NDISWAN you don’t see anything in the NDIS layer.

            Viewing 5 posts - 1 through 5 (of 5 total)