I always chuckle when I see someone censoring an internal IP. Itβs like intentionally not naming the room youβre in (kitchen, bathroom, bedroom, etc) when youβre on the phone so the person on the other end canβt find you on a globe.
Selfhosted
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:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
If we pull in a team effort we can all collectively try 1 to 255 for the last octet and download all the money from this man's bank account and split it between us what say?
Are you sure he's using 255.255.255.0 network mask though?
Isn't 255 the broadcast address?
Depends on the network mask.
The 192.168.x.x IP range doesn't allow for subnet masks greater than 255.255.255.0. How that's enforced I can't remember, but I'm 99% sure he isn't using larger subnets.
The .x.x literally shows that you can fit a /16 (255.255.0.0) in there. 192.168.0.0 255.255.0.0
No, that's a placeholder a set. It's a class C range which is limited to 254 hosts.
We'll mark you down as having tested 255 then, 1 down, 254 to go!
Gotta censor out those local IP's
Kind of new to selfhosting. Didn't know any better π€·πΎββοΈ
I was going to comment this, that's so cute.
No problem. One more tip though: If you ever censor your public IP, don't just censor the last two digits. Otherwise it will be easily brute-forced.
You don't need to put in the effort to hide those IPs. An IP starting with 192.168 is a private network and virtually useless as any way to compromise your network - an outsider would need access to your network (via your modems public facing IP) and know the device access credentials to make any use of the IPs.
That being said, it appears your input devices are unable to connect because they can't be found. That means a mismatch in network details somewhere. Check the IP address and confirm it's using the same subject; does the device connecting use the same 192.168.1.x network as the input/source device?
No I have his ip and now I will hax!!!