Re: Sending data to local port

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

From: Stanley Feng \(MSFT\) (sfeng_at_online.microsoft.com)
Date: 03/31/04

  • Next message: mikejpoole: "VPN Server Behind a Router"
    Date: Wed, 31 Mar 2004 10:54:38 -0800
    
    

    "Port" is a concept applies to TCP/UDP, so, if you want to send something to
    a "port", that has to go throught the network stack - at least the transport
    layer. (So, what you've described below is right conceptionally, as to
    detailed implementation, the packet may not necessarily need to go all the
    way to the bottom of the stack.).

    If you really care about performance, there are many other ways to do
    Inter-Process Communication (IPC), just look on google/MSDN for this topic.
    Thanks.

    -- 
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of included script samples (if any) are subject to the terms specified
    at http://www.microsoft.com/info/cpyright.htm"
    "Phil Wood" <anonymous@discussions.microsoft.com> wrote in message
    news:5276AC0C-CF5A-4952-9B95-D75AA6C7E56C@microsoft.com...
    > Because it says so in section 2.7 of "The Protocols, TCP/IP Illustrated,
    Volume 1"   :)
    >
    > Don't know if this is how it works in Win 2000
    >
    >      ----- Olaf van der Spek wrote: -----
    >
    >
    >      "Phil Wood" <anonymous@discussions.microsoft.com> schreef in bericht
    >      news:D4B5D457-6AD8-448F-8CF6-C8A740EA7291@microsoft.com...
    >      > Thanks for the input. My understanding is that in most stack
    >      implementations, when data is sent to the loopback interface (or to a
    host
    >      interface on the machine) the data must first go down through the
    transport
    >      and network layers of the stack. Having exited the bottom of the
    network
    >      layer, the loopback driver adds it to the incoming IP queue, and it
    >      gradually makes its way back up through the network layers. The data
    does
    >      not reach the ethernet. Is this how it works in Windows 2000? If so,
    is
    >      there a way of bypassing all this so that I can write data directly
    to a
    >      port without having to go down through the transport and network
    layers and
    >      back up again?
    >
    >      Why would 'most stack implementations' do that instead of delivering
    the
    >      data directly?
    >
    >
    >
    

  • Next message: mikejpoole: "VPN Server Behind a Router"

    Relevant Pages

    • RE: [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCPportsfrom the host TCP port space.
      ... PS_TCPportsfrom the host TCP port space. ... And actually RDMA stack exist and no one said it should be thrown away ... detail how RDMA (a network technology) is treated as bastard child by ...
      (Linux-Kernel)
    • Re: socket()
      ... of Tcp/Ip network use in Unix. ... The socket call causes ... binding activates the listener on a specific port. ... Socket call fills a struct in the stack and provides ...
      (microsoft.public.windows.server.security)
    • RE: Printing from Win9x clients stops
      ... > and make sure this software does not interfere with SBS Server. ... > clients, please disable it and try again. ... Create a local printer and redirect the port to the network server. ...
      (microsoft.public.windows.server.sbs)
    • RE: SBS 2003, ISA 2004
      ... ISA and IIS try listening on these two ports. ... by default the Web Proxy is listening on port 8080 ... of the local network adapter. ... Microsoft CSS Online Newsgroup Support ...
      (microsoft.public.windows.server.sbs)
    • Re: ERS 8600, simple setup, IP, VLANs, etc.
      ... management port is just used to hang an IP address to. ... associated with an interface, such as a VLAN. ... fairly functionally homogenous network), but something that is ... or OS virtuallization - except that networks have been doing this kind of ...
      (comp.dcom.sys.nortel)