Lucas Janin 🇨🇦🇫🇷Dec 22

I configured my #homelab subnet as 192.168.1.0 and am using #tailscale with #headscale to connect remotely to my homelab when I'm away from home

I encountered an issue in France, as some internet providers use the same 192.168.1.0 subnet

I'm considering moving my homelab to a new vlan or moveing all my subnets

What options and strategies do you recommend? Any suggestions would be greatly appreciated.
Boots will be welcome 😉

#pool #vlan #ipv4 #networking #selfhosting #selfhosted #devops

192.168.2.0 [move only my homelab to]
3.1%
192.168.{xx}{vlan}.0 [new]
13.8%
10.{xxx}.{vlan}.0 [new]
67.7%
172.23. {vlan}.0 [new]
15.4%
Poll ended at .
Show thread4n6
@lucas3d this page has some helpful guidance, and even offers you a random subnet suggestion at the end of the page! I like 172.16., personally, as I find 192.168. and 10. Seem to be used everywhere. While 10. technically has many subnets to hide in, some networks seem to think they need to use the whole range (10.0.0.0/8), which can still cause issues. https://blog.benjojo.co.uk/post/picking-unused-rfc1918-ip-space
Picking uncontested private IP subnets with usage data

Dec 22 at 9:33amWeb
Show threadRideDon'tSlideDec 22
@4n6 @lucas3d I had an instance where I ran into a conflict within the 172 range with a TrueNas App that did some docker network exposure and I had to change the VLAN bc I was not feeling it to tinker on the app side. So 192.168.x and 10.x for me it is from now on.
Show threadLucas Janin 🇨🇦🇫🇷Dec 22

@ridedontslide @4n6 Agree, Docker uses a lot of 172.xx.0.x. So I stay away from that range.

On my side, the 192.168.1.x causes me issues; this is the reason for the reflection and the pool.

Show threadLucas Janin 🇨🇦🇫🇷Dec 22

@4n6 Thanks for this link with very interesting information.

This confirms my initial pick 10.xxx.{vlan}.0. But I am thinking of using 10.xxx.xx{vlan}.0 to be safer :-)

But, let's see the result of the pool in a few days.