New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Don't be surprised what you will find by snuffing arround your net.
All unmanaged services are ticking time bombs.
Its not isolated. But if on everyones server the same appears, then rather its exposed by the current wan connection the server works on. Nothing strange, cause that are just names, not visible IPs.
But you could search the /24 IP list on ASN, as some provide details, or DNS settings.
If two of us buys two servers as our remote desktops, and I share my Dropbox folder with you, it’s beneficial to keep mDNS running so that Dropbox LAN sync could allow us to sync the folder with each other directly.
Hi,
i am sorry, but i actually still do not understand the problem.
What is the exact difference from the point of security, if a user is doing a port scan or if a user is using multicast to get a list of information, while the port scan will deliver more security relevant informations than a simple multicast call if i am not mistaken.
You claim that "serious" providers should filter that. Why?
Should we also ban clients who are doing a port scans? Or if they are doing connection attempts without prior written permission?
Why exactly should we limit the use of legit internet / protocol mechanics?
Not all, some are, others are not.
VPS is self-managed service, as well as the node on which that VPS created... Good luck.
Not usual, but not crazy. Some providers use networking solutions that naturally don't pass multicast traffic, some use ones that do, and from that group, some deliberately block it and some don't.
I'd certainly be annoyed if my provider was censoring some packets people sent to my address.
I go away to touch grass for like less than one day and this blows up. It's Servitro, MassiveGrid shouldn't be catching strays here as I had no issues with them (just didn't need that VPS)
well, some services were intended to be discoverable, so it's the vps owner responsibility to limit / disable certain response to some ip(s) only. also, discoverability doesn't mean it's not password-protected or doesn't apply some AAA method(s). cmiiw.
my problem with this provider-fault kind were some clueless providers when it come to some implementation. for example, ipv6 router-adv broadcast that would make ipv6 routing goes to the broadcaster but not properly respons to routed packet sent there. this happens once and I won't mention the provider since I had the fix and I was no longer using them.