Ethernet II
mac address only
HTTP (the main protocol for the World Wide Web); TCP; IP; and if you use an Ethernet network, you are using Ethernet and ARP; DNS. There are probably a few more, too.HTTP (the main protocol for the World Wide Web); TCP; IP; and if you use an Ethernet network, you are using Ethernet and ARP; DNS. There are probably a few more, too.HTTP (the main protocol for the World Wide Web); TCP; IP; and if you use an Ethernet network, you are using Ethernet and ARP; DNS. There are probably a few more, too.HTTP (the main protocol for the World Wide Web); TCP; IP; and if you use an Ethernet network, you are using Ethernet and ARP; DNS. There are probably a few more, too.
csma
the tcp/ip frame uses the ip address to send messages between devices (computers, printers, etc) on your network. This frame is inside an ethernet frame on the network layer. The ethernet layer does not use ip addresses at all, they use mac addresses. For an ethernet frame to travel through a router, it needs a mac address. Your router actually does not need an ip address. It will respond to broadcasts. In fact sometimes it won't answer to tcp/ip requests. Its job is to deliver the datagram to its destination more than it is to answer you (your computer that is). So sometimes a router will not answer a ping, but a computer on the other side of the router will answer even if there are several router in the path.
a. Multimeter
Yes, padding is needed for an Ethernet frame if the IP packet is only 60 bytes and the Length/Type field (LCC) is not in use. Ethernet frames must be at least 64 bytes in total, including the header and trailer. Since the Ethernet header is 14 bytes and the trailer (Frame Check Sequence) is 4 bytes, the total without padding is 78 bytes. Therefore, 0 bytes of padding are needed because the total frame size exceeds the minimum requirement.
If the mainframe were using TCP/IP then you don't need to do anything except route the traffic to it. If the protocols are not Ethernet on both the mainframe and the LAN then you would need a gateway to convert the protocols back and forth from the mainframe.
BUS
HTTP works over a TCP connection.HTTP works over a TCP connection.HTTP works over a TCP connection.HTTP works over a TCP connection.
Just as much as Ethernet or Arcnet does: you simply cannot use TCP/IP (and UDP/IP), without revealing your IP address.
You could use any kind supported by the Linux kernel, though a TCP/IP network over Ethernet or wireless would probably be best.
10base5