Its just some minor problem
Our intranet has 500 systems with ip addresses ranging in 172.0.x.x (i know its a public address but our senior network engineer hesitates to change)
MICROTIK CLOUD ROUTER connected to Radius server is on 172.0.0.1 (so we type 172.0.0.1 to logon to the internet with some username and password)
Now there are dome local intranet campus educational resource server (to be accessed at our campus only) over 172.0.2.x
And when a machine tries to connect to this intranet server which is in the same laboratory on the same switch it goes to the radius manager for login
Please understand the context here. I don’t need the INTERNET i just want to connect over my INTRANET local server but, RADIUS asks for LOGIN (i recieve NET PROHIBITED as per the linux terminal message during ping)
I just want a message from MICROTIK that its a wrong practice to use PUBLIC IPs and on using private IP addresses this problem will be solved (RADIUS doesn’t pop for intranet connectivity)
If i keep the address in 172.17.x.x range (which is a private range) will
it solve my problem, Will INTRAANET connect without RADIUS interrupting for
LOGIN???
Its an emergency as i have to handle it on monday for online tests in the
campus & the server ain’t connecting even after login
I understand through this reference that we should not be using public ip’s
(Oh i’m a NETACAD student also ID is 50844650 - i do simulate packet
tracer) -
https://mellowd.co.uk/ccie/?p=886<br/](https://mellowd.co.uk/ccie/?p=886">https://mellowd.co.uk/ccie/?p=886</URL><br/)>
Please do answer ASAP
Sorry for the trouble. A question from a very little humble man
Thank you