Goline Logo



  • Route RPKI validation April 1st, 2022
    RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
  • RIPE – Atlas Anchor February 17th, 2022
    We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
  • MANRS June 20th, 2020
    GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

Configuring w32tm on DC/GC Windows (ntp)


w32tm /config /manualpeerlist:”ntp.goline.ch,ntp2.goline.ch” /reliable:yes /update

w32tm /config /manualpeerlist:[server],0x8 /syncfromflags:MANUAL 
The actual IP address of the NTP server or its host name must be entered instead of [server]
The flag "0x8" forces w32time not to send "symmetric active" packets but normal "client" requests which the NTP server replies to as usual.

Then the following command can be used to immediately make the changes effective:

w32tm /config /update 
If this command has completed successfully your system clock has synchronized to the given NTP server. To check it open a Date and Time window (click "time" icon in the lower right corner of the desktop) -> Change date and time settings -> Internet Time. You should see something similar to Figure 6.

Alternatively, the w32time service can be restarted:

net stop w32time 
net start w32time

The command:

w32tm /query /peers
can be used to check the configuration. The output should look similar to the line below:

#Peers: 1
Peer: ntp.goline.ch,0x2
State: Active
Time Remaining: 221.4934473s
Mode: 1 (Symmetric Active)
Stratum: 2 (secondary reference – syncd by (S)NTP)
PeerPoll Interval: 8 (256s)
HostPoll Interval: 8 (256s)

The current SNTP value is:[server],0x8

If the w32time service is restarted it sends immediately a request to the NTP server. Additionally, the command:

w32tm /resync 
can be used to let w32time send a request.

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x