Skip to main content

Timeline for Bridging Traffic on a LAN w/o DHCP

Current License: CC BY-SA 4.0

9 events
when toggle format what by license comment
Dec 2, 2018 at 7:53 vote accept tarabyte
Dec 2, 2018 at 7:51 answer added dirkt timeline score: 1
Dec 2, 2018 at 6:03 history edited tarabyte CC BY-SA 4.0
edited title
Dec 2, 2018 at 4:47 comment added Ron Maupin By the way, your reference to routing is incorrect. Routing is when you send traffic from one network through a router to a different network. On the same LAN, it is bridging.
Dec 2, 2018 at 4:43 comment added Ron Maupin On such a network, ARP requests would be very, very rare because ARP caches in a table. You would also need to statically configure every box with its corresponding IP address. It's not just enough to get the frame to the box, the data-link layer (MAC address) will pass the payload of the frame to the network layer (IP address), and the destination network address must match that of the receiving host, otherwise the host will drop the packet.
Dec 2, 2018 at 3:40 history edited tarabyte CC BY-SA 4.0
deleted 44 characters in body
Dec 2, 2018 at 3:36 comment added tarabyte Adding a permanent neighbor should stop periodic ARP requests, reducing a small portion of traffic. I guess I'm hoping that associating the MAC address with an IP address is a way to form an IP reservation and give me a way to issue HTTP requests to those client devices. These devices only send data to box-a.
Dec 2, 2018 at 0:59 comment added grawity_u1686 I'm not sure why you think that DHCP is related to ip neighbor or MAC address resolution. It doesn't do that, ARP does.
Dec 2, 2018 at 0:23 history asked tarabyte CC BY-SA 4.0