Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Are TCP and UDP the only protocols supported by the Internet? If they are, do other networking protocols that are not meant to be used with common hardware exist?
No, not at all. The Internet is routed at the network layer, which is IP.
The problem is that NAPT that is used for IPv4 because we have run out of those addresses only supports TCP, UDP, and ICMP. IPv6 restores the IP end-to-end paradigm and you can use any transport protocol because the Internet only cares about IP, not any protocols above that.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
ARP and RARP are the main Protocol uses in Link Layer. To do the ARP request, a device requires IP and MAC address pair for broadcasting. So my question is ARP doing the mapping the IP to MAC by referring the data
and operates using the LAN.
So RARP is the reverse algorithm of that like mapping logical address to physical address in caches in Computer Systems.
I hope a good answer from the community.
There are dozens of protocols that use the data-link layer the same way ARP does, including IPv4, IPv6, etc. See IEEE 802 Numbers for a list of protocols that use the data-link layer.
For protocols in the data-link layer, there are/were many. For example, token ring, ARCNET, FDDI, frame relay, HDLC, ATM, PPP, etc. Ethernet used to be the king, but Wi-Fi has dethroned it since there are more devices shipping with Wi-Fi interfaces than devices with ethernet interfaces.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
I am working on a small embedded device based upon an STM32F4xx MCU. It implements a TCP/IP server over a Wi-Fi connection. The question I have relates to exposing the IP address of the device so that it may be discovered by computers on the same network. UPnP and SSDP seem to be rather "heavy" solutions to this problem.
Are there other techniques/protocols that have a smaller footprint than UPnP and SSDP?
Thanks in advance for your input,
Sid
If you can make up any custom protocol, a simple UDP beacon periodically sent to the broadcast address (255.255.255.255 or your preferred interface's broadcast address) is simple and reliable.
Synopsis of comments:
For listing in mainstream platforms' (Windows, Linux, OS X) network views, the best option would likely be to implement the full stack required for Windows' Network Discovery.
If hostname lookup is enough, Netbios or mDNS could be enough.
The search term you are likely looking for is zero-configuration networking and should give you all the available options
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Is there a method to determine whether a host (on your LAN) is on WiFi vs Ethernet using nmap or any other tool? I am OK with fuzzy guesses as well.
tl;dr No, there is none
Long answer:
There is no way to find out what kind of connection other PC on your network is using(without physically accessing it ofc).
Those things are abstracted on network. You can sniff traffic on transport layer by Wireshark and see there is no data on interfaces being transported.
An option:
You can learn a physical network interface vendor by sniffing traffic.
Wireshark can guess those, because vendors have their own MAC address prefixes. And if it's some company which is making wireless interfaces only, you can hit a jackpot. It's not even close to being a bulletproof method though.
Nmap may be used to look for open ports. There might be a chance that you can deduce which software server is running by getting info on ports, but I can hardly imagine you will find anything wlan/eth specific.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I understand the mechanism of ARP but I am wondering why do we use it even if we have the recipient's IP address? Isn't it enough to rely on the recipient's IP address to send packets instead of taking extra steps of finding its matching MAC address?
Thank you.
An IP address is a layer-3 address. Layer-3 packets get encapsulated into layer-2 frames, and layer-2 also has addressing (MAC addresses) which needs to be supplied. ARP (Address Resolution Protocol) resolves the layer-3 IP address to a layer-2 MAC address so that the layer-3 packet can be encapsulated into a layer-2 frame which is then sent out the layer-1 interface.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I know they are address schemes used in different layers, and that IPV4 is 32 bits while MAC is 48 bits.
My questions are:
Why do we need two different address schemes?
What is the problem if we decided to use the same address for both purposes?
Is there a reason for the MAC address requiring more memory?
Has the introduction of ipv6 changed anything?
MAC addresses is a Layer 2 Address, while IP is a Layer 3 Address.
Layer 1 is phisical layer
Layer 2 is data link layer ---> MAC ADDRESS
Layer 3 is Network Layer ---> IP Address
http://en.wikipedia.org/wiki/OSI_model