Hello guys
DNA wrotesince you opened the topic, the same thing happened to me on ogero DSL at home, tried to go to youtube.com and same error popped up saying connection was not private and attackers trying to steal info and some sites gave a disabled by administrator error was shocked about this error and entered the router to see what is the IP, i noticed that its the first time ever i get a private IP from ogero 172.x.x.x, freaked out for a bit but the issue was solved with a restart got my public ip back and didn't see it again since 3 days. it appears Ogero has some monitoring going on on their private IP's but how did i get one of their internal private IPs, who knows...
Your IP is not private IP in the first place.
You have 3 legacy classes for IP addresses: A, B, and C. And in each class you have a range that is dedicated for private use that will NOT be routed over by routers. These ranges are:
A: 10.X.X.X
B: 172.16.X.X
C: 192.168.X.X
You see, you indeed have the first octet of your IP 172 but the second one isn't. Your IP may be 172.15.X.X or 172.33.X.X or 172.1.X.X or 172.254.X.X ... all are public IP.
NuclearVision wroteOgero does assign private IPs for residential dsl.
I remember, 3 years ago, when I still had ogero dsl, i set up servers on my machine, that friends could access using public iP/port directly.
Ogero can't do tricks like private ISPs do because there are some laws Ogero must follow, while ISPs can make their own policies to follow, like putting you behind a NAT and then they will give you a private IP! which really sucks!!
So NO, Ogero will never give you a private IP.
rolf wroteDNA wroteit's impossible for someone to do an attack on the DSL network between a router and the BRAS unless he is INSIDE ogero's building. either its a misconfiguration of some sort, or Ogero is preparing to start giving out Private IPs which if happened, i'll be giving them a really bad time lol
rolf wroteWhy and how your router would get a different IP address, I don't know much about protocols ISPs use.
the IP addressing is dynamic by default on all packages, so everytime you reconnect a pppoe connection you get a random IP from the available IPs in the pool.
Yes it is. What I mean is I don't know details about the protocol and if it can be easily hijacked. For example, on an ethernet LAN, you can set up a second DHCP server and the clients can get their address from your DHCP server, instead of the "legit" one, which is usually on the router. Whether they take their adress from the normal DHCP server or your second DHCP server depends on things like latency, I guess. So IP address distribution using DHCP is not very secure, and anyone can disrupt that, and attempt to do a man in the middle attack by giving new clients a different IP and gateway address.
I don't know what protocol is used for IP allocation on the ISP side, and how vulnerable it is.
Well that is for DHCP and it's true, it is technology used LANs not WANs.
So when you use DHCP in your very own private network you at least can maintain some security for your network physically. I mean when you are in your home or your office, wouldn't you notice someone plugging in a router in your network? That is why you don't need authentication here since you are in a controlled environment.
While on WAN connections like DSL between you and ISP, indeed security threats rises here, and that is why you need authentication when you connect to pppoe using and username and a password.