Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 216
  • Last Modified:

TCP/IP communication question

Do you know to what extent the network card is used in TCP/IP communication if the source and destination are the same server (itself). Does data make it to the physical NIC even though the communication isn't leaving the server?
Just wondering if the NIC driver and physical NIC are involved in the process. So if I have a server with a database on it, and the same server has the client piece on it, is the data making it to the NIC level even though this is internal only?

What I'm trying to determine is this:  Would the advanced TCP/IP settings on the NIC come in to play or not in this scenario where communication never leaves the server itself?
0
ZabagaR
Asked:
ZabagaR
1 Solution
 
giltjrCommented:
No the traffic never makes it to the NIC driver.  You can see this by doing a wireshark packet capture and selecting the NIC assigned to the address in question.  You will see no traffic captured, because it never hits the driver.
0
 
FarWestCommented:
as far as I know, when you don't use loop back IP which is 127.0.0.1, traffic will go to NIC
0
 
nader alkahtaniCommented:
You should use wireshark
When you ping loopback IP address 127.0.01 through 127.255.255.255  you now work with just software level without touch NIC, but if you ping host name or IP of your machine you will work with hardware.
0
 
ZabagaRAuthor Commented:
Yes, you're right.  If I run a wireshark capture, and pick my databases port connection as a filter, I never get any data captured.
0
 
giltjrCommented:
The first thing IP does when it needs to connect to a remote host is look-up the destination IP address in the routing table.  It then determines what it needs to do based on what the routing table says.

IP will see that to talk to IP address "X" it needs to send the data out the interface with address "X".  The 1st layer of talking to IP address "X" is the Windows IP stack.  The Windows IP stack sees that the destination is itself and never passes anything on to the NIC driver, thus it never gets to the NIC.

Depending on what NIC you have and how you have it configured a IP address on a local host is know up to 3 places:

1) The IP stack
2) The NIC driver
3) The NIC

Not all NIC's support knowing the IP addresses that NIC has assigned to it.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now