As you can connect to the internet you can also access your router (or at least a router). And when running ping, even if you had overlapping IP addresses you should still get responses from the network.
So, two things come to mind: Either your laptop is running with a different netmask than other devices which causes problems or you’re connected to something else than the local network you think you are. Changes on DHCP server or misconfigured network settings on the laptop might cause the first issue. The second might be because you’re connected to your phone AP, some guest network on your devices or neighbors wifi by accident (multiple networks with same SSID around or something like that).
Other might be problems with mesh-networking (problem with ARP tables or something) which could cause issues like that. That scenario should get fixed by reconnecting to the network, but I’ve seen bugs in firmware which causes errors like this. Have you tried to restart the mesh-devices?
Is it possible that your laptop has enabled very restrictive firewall rules for whatever reason? Check that.
And then there’s of course the long route. Start by verifying that you actually have IP address you assume you have (address itself, subnet, gateway address). Then verify that you can connect to your router (open management portal, ping, ssh, all the things). Assuming you can, then check the router interface and verify that your laptop is shown there as a dhcp-client/connected device (or whatever term that software uses). Then start to ping other devices on your network and also ping your laptop from those devices and also verify that they have addresses you assume (netmask/gateway included).
And so on, one piece at the time. Check only single thing at one time, so you get full picture on what’s working and what’s not. And from there you can eventually isolate the problem and fix it.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
As you can connect to the internet you can also access your router (or at least a router). And when running ping, even if you had overlapping IP addresses you should still get responses from the network.
So, two things come to mind: Either your laptop is running with a different netmask than other devices which causes problems or you’re connected to something else than the local network you think you are. Changes on DHCP server or misconfigured network settings on the laptop might cause the first issue. The second might be because you’re connected to your phone AP, some guest network on your devices or neighbors wifi by accident (multiple networks with same SSID around or something like that).
Other might be problems with mesh-networking (problem with ARP tables or something) which could cause issues like that. That scenario should get fixed by reconnecting to the network, but I’ve seen bugs in firmware which causes errors like this. Have you tried to restart the mesh-devices?
Is it possible that your laptop has enabled very restrictive firewall rules for whatever reason? Check that.
And then there’s of course the long route. Start by verifying that you actually have IP address you assume you have (address itself, subnet, gateway address). Then verify that you can connect to your router (open management portal, ping, ssh, all the things). Assuming you can, then check the router interface and verify that your laptop is shown there as a dhcp-client/connected device (or whatever term that software uses). Then start to ping other devices on your network and also ping your laptop from those devices and also verify that they have addresses you assume (netmask/gateway included).
And so on, one piece at the time. Check only single thing at one time, so you get full picture on what’s working and what’s not. And from there you can eventually isolate the problem and fix it.
If I had a nickel for every time clearing the ARP tables fixed something, I’d have a shitload of nickels.