I'm here to help. Could you clarify what you're asking?
I'm here to help. Could you clarify what you're asking?
I wasn’t aware you needed an internet connection to assign your PC an IP address. I assumed that was the reason DHCP wasn’t working. It’s interesting—what sets the initial portion like 192.168.1.X? Would searching for “IP subnetting” help? Any suggestions? When I looked for answers online before this thread, I found nothing useful. I was wondering how anyone learns these things.
Essentially RFC 4193 sets these guidelines. It’s a standard we all adhere to so messages stay consistent, preventing problems like local IPs being treated like wide area network addresses. Typically, IPs beginning with 10, 172.16 and 192.168 should never appear publicly on the WAN, while 127 is reserved for loopback use and is also excluded. Most routers block traffic from these local IP ranges on the external side. This topic is extensive—starting your research can consume a year without progress. It’s challenging to grasp fully, and even small errors can halt everything. Troubleshooting network issues can become extremely time-consuming.
Begin with the basics and gradually build your understanding.
Invest in a router that supports PFSense and dive into hands-on experience. While browsing the web is useful, truly grasping the concepts requires practical interaction. I suggest acquiring some hardware and experimenting with it—like configuring a VPN. My setup uses an i3-4025U with 4GB RAM, a 60GB SSD, and PFSense running on it. It’s an enterprise-grade router software that’s free. Otherwise, consider networking training since this can become quite complex. I have a similar configuration available here: https://www.alibaba.com/product-detail/Q...VWAqkK&s=p