• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

This forum thread needs a solution.
Kudos1 Stats

Core - We need a "User Defined Subnet" capability

Core is using a 172.16.x.x network, and my Corporate Network already uses this same IP address space.  So I have a routing conflict with my Corporate VPN, as the 172.16.x.x network exists locally on the Core, and also on my Corporate VPN.

Core needs to support RFC 1918 https://en.wikipedia.org/wiki/Private_network which will allow the Core User to define a "User Defined Subnet" for Core to use.

Most of us have to use a Corporate VPN from home, and it is imperative that the Core User has the ability to choose a "User Defined Subnet" within the RFC 1918 address spaces, so that the Core User can build a network that works properly.

Every home router I have ever purchased supports the ability to change the "User Defined Subnet" of the router.

RFC 1918 = The Private Network Address spaces that Core needs to support as a "User Defined Subnet":

10.0.0.0/8 = 10.0.0.0 – 10.255.255.255

172.16.0.0/12 = 172.16.0.0 – 172.31.255.255

192.168.0.0/16 = 192.168.0.0 – 192.168.255.255

Replies

Kudos0

Re: Core - We need a "User Defined Subnet" capability

Network Engineer There are multiple threads on the forums having discussed the customer need for RFC 1918 implementation. Norton is 100% aware of the customers need for that as well as why. That being said Core in its current form as you most already know ONLY supports IP "reservation" with a 3rd octet of the IP being the reservation. Personally and without knowledge of the original design of core internals such as firmware I believe to allow FULL RFC 1918 would go against the basic implementations of Core security. It has been stated that static IP can be set at the time of setup onboarding with Core if the ISP provides one for the customer. To date I have not seen that option available and have asked for validation from Norton. I'm still awaiting that official answer.

https://support.norton.com/sp/en/us/home/current/solutions/v118380605_core_en_us

You may follow the release thread here for future announcements regarding firmware, although, I WOULDN'T expect it to be implemented any time in the near term if ever. https://community.norton.com/en/forums/norton-core-firmware-update-release-notes

Cheers

"From DOS to Windows10 what a journey it has been" Windows 10 Professional x 64 Fall Creators Update version 1709 / build 16299.194 / NSBU 22.11.2.7 Traditional / Norton BETA tester