TCPIP Binding-Hardware or Software

PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
edited January 2007 in Science & Tech
Hello ya'll. In one of the current threads, the user was informed by Linksys that he'd "lost TCPIP binding" on his wireless (USB) NIC and that he'd need to take it (his computer) in to a computer repair svc. for repair. :rolleyes2

I've been searching the I'net on the topic - it would appear that info. on TCPIP binding is scarce at best - at least on the web. I did finally happen upon an article that explained it to some degree - at least w/ respect to DHCP.

What I couldn't assertain from this article was whether the binding is handled by hardware (the NIC) or software (the OS). The article referred to "the client" a no. of times but never got more specific than that.

HERE is the article. It's actually pretty interesting. But I still need that bit of information. (hardware vs software)

Oh yes, HERE is the thread I mentioned.

I'd be greatful for feedback from one o' ya'll networking gurus.

TIA! :smiles:

Comments

  • zero-counterzero-counter Linux Lubber San Antonio Member
    edited January 2007
    Bindings occur at the software level, as a means for the hardware drivers to interpret the instructions provided by the protocol, allowing for utilization of the specific functions/features it was created for.

    It was believed by many that the killernic offered a form of H/S hybrid meshing, due to it having an embedded linux kernel on a NIC, but that was squashed... as the tcp/ip protocol still needs to be bound in order to use its functionality.
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited January 2007
    zero.counter wrote:
    Bindings occur at the software level, as a means for the hardware drivers to interpret the instructions provided by the protocol, allowing for utilization of the specific functions/features it was created for.

    It was believed by many that the killernic offered a form of H/S hybrid meshing, due to it having an embedded linux kernel on a NIC, but that was squashed... as the tcp/ip protocol still needs to be bound in order to use its functionality.
    Thankyou ZC. By software level do you mean drivers or OS?
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited January 2007
    Both. Both things play a hand in TCP/IP binding.
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited January 2007
    Thrax wrote:
    Both. Both things play a hand in TCP/IP binding.
    Thankyou, Thrax. So is it handled "globally" or is it handled seperately for ea. NIC? I assume seperately on some level because the drivers are involved in the process.

    The issue I'm looking into - the user has his hardwired NIC working fine. He's only experienced issues w/ the wireless USB NIC. This is the one that Linksys told him he'd "lost his TCPIP binding" on.

    The NIC was showing up fine in device manager but never showing up in NETWORK CONNECTIONS. I wouldn't have thought of that being a TCPIP binding issue but then, odviously, I'm not well versed on the topic. Don't know how the problem would present itself if that were the case...
Sign In or Register to comment.