Cannot sync network time (NTP) on Win10 on BSNL FTTH

  • Thread starter Thread starter vishalrao
  • Start date Start date
  • Replies Replies 84
  • Views Views 17,040
Nice link... and no I don't have a fancy router software to try this.
 
I had posted the issue on Microsoft forum but no response or anything from them.
 
Could be the same problem of using source port 123

Still doesn't change that it's silly to not use random source ports.
 
Last edited:
@BraveHunt If the cams have an option to change NTP Server, what you can do is setup your own NTP Server on something like Pi as @shashankb suggested.

You can easily customize the source port that your local NTP Server uses to contact stratum servers.

Kinda similar to using DNS on another port (DoH or DoT though DNS is also encrypted in this case) if ISP hijacks destination port 53 (but in this case its source port instead).
 
Last edited:
bsnl guy confirmed ntp etc ports are blocked because of risk of malware attacks like amplification ddos attacks which consume user data lots
 
I think they are correct. The last DDOS attack on BSNL network was a result of hijacked ONT asking for time...
So, they made a band aid solution as it is in their blood.
Instead of asking vendors to provide reguler patches to dumb ONT, they put a tape on the leaking tank...
Dont expect much more from them. I got to know recently that nobody in my exchange know about traceroutes and why they change with time and how packets travel. So, i am quite happy they did something.
 
JB701 said:
superuser.com

Change source port of NTP requests on router using iptables

My ISP blocks outbound udp port 123. This is preventing ntpd from getting ntp updates. How do I get my router (Asus router running Asuswrt Merlin) to automatically change the port number from 123 to
superuser.com superuser.com

Related maybe?
Click to expand...

BSNL aren't the first ISP to do it though tbf

AT&T blocks outbound UDP traffic with source port 123, to mitigate common NTP reflection attacks from compromised machines on customer networks. Destination port 123 is allowed, but most NTP clients use 123 for the source port as well.
Click to expand...
 
Last edited:
My friend had to call the Backend directly for opening multiple ports as they were working on some project . So BSNL hooked him up with a network engineer . He did not know basic Network skills , my friend had to take Anydesk remote of the BSNL side and get his work done . That guy also had no clue about Cisco CCNA

Instead BSNL providing you support ,it is the other way
 
You must log in or register to reply here.
Back