Home Networking

198 readers

1 users here now

A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.

Rules

Please stay on topic.
Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
No affiliate links.
No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.

founded 1 year ago

MODERATORS

[email protected]

How to troubleshoot Layer 2 IP resolution delays? (alien.top)

submitted 1 year ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

When I type a local IP into my browser (to get to a VM or another machine or even my firewall), there is more of a delay than there should be. Sometimes, it just hangs until I try again.

How do I troubleshoot this?

I'm on a single VLAN (flat network), with a few unmanaged switches and a Brocade core switch connected to Sophos XG (home edition running on VM). I thought layer 2 addresses would get resolved by switches between the device requesting and the host being reached. So that would exclude need for hitting firewall, right? And wouldn't implicate my DNS provider either, right?

I'm going to replace some of the unmanaged switches with managed Brocade switches (running Ruckus Unleashed WLAN).

Suggestions on how to test different links in the chain?

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 year ago

Tracert? Anything weird? No app based vpn software? Check your arp. Layer 2 is just mac vlan. Layer 3 handles ip. Possibly multiple dhcp servers on same subnet?

[–] [email protected] 1 points 1 year ago

That should be the path over dumb switches and a flat network. Ping issues to container? Double nat maybe?

[–] [email protected] 1 points 1 year ago

If you are strictly using IP addresses in the same subnet, there should not be any name resolution involved. The initiating host will ARP for the MAC address of the host with the IP address that you specified.

If you use ping without the -n option, it will try to resolve the host name associated with the entered IP address. If the DNS query times out or gets an error, ping silently displays the IP address in the host name field instead of the host name. I believe that this is a one and done and should not effect the actual pinging.