All,
- Time - NTP UDP/123
- This is odd, I'm able to reach the server and 44.60.44.1 from AMPR and the Public Internet (what exactly are you trying to 'reach' at 44.60.44.1 to determine its status, as I've only announced NTP as being available there)
- using 'ntpdate -q 44.60.44.1' or 'ntpdate -q kb3vwg-001.ampr.org' works for me anywhere on the Internet
kb3vwg@kb3vwg:~$ ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 2, offset 0.001173, delay 0.02589 30 Jan 18:00:19 ntpdate[1058]: adjust time server 44.60.44.1 offset 0.001173 sec
- I have now permitted access from the Public Internet (previously, it was only available to 44 hosts), let me know
- Lynwood KB3VWG
This is from testing from 44.56.6.4 in Pennsylvania
root@pool4:~# ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 0, offset 0.000000, delay 0.00000 30 Jan 18:38:13 ntpdate[9399]: no server suitable for synchronization found
This is testing from my public ip on level 3 [root@2338 ~]# ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 0, offset 0.000000, delay 0.00000 30 Jan 18:35:07 ntpdate[6342]: no server suitable for synchronization found
Nothing found here. Corey N3FE
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail This email has been sent from a virus-free computer protected by Avast. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sat, Jan 30, 2016 at 6:08 PM, lleachii--- via 44Net < 44net@hamradio.ucsd.edu> wrote:
(Please trim inclusions from previous messages) _______________________________________________ All,
Time - NTP UDP/123
This is odd, I'm able to reach the server and 44.60.44.1 from AMPR and
the Public Internet (what exactly are you trying to 'reach' at 44.60.44.1 to determine its status, as I've only announced NTP as being available there)
- using 'ntpdate -q 44.60.44.1' or 'ntpdate -q kb3vwg-001.ampr.org' works
for me anywhere on the Internet
kb3vwg@kb3vwg:~$ ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 2, offset 0.001173, delay 0.02589 30 Jan 18:00:19 ntpdate[1058]: adjust time server 44.60.44.1 offset0.001173 sec
- I have now permitted access from the Public Internet (previously, it was
only available to 44 hosts), let me know
- Lynwood
KB3VWG
I've got exactly the same response:
root@linux:/# ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 0, offset 0.000000, delay 0.00000 31 Jan 01:22:52 ntpdate[29207]: no server suitable for synchronization found root@linux:/#
On Windows 8 desktop PC, by means of quite old program D4.exe (Dimenison 4) got nice sychronization with the following setup:
Server: 71.114.81.28 Protocol: SNTP
Best regards. Tom - SP2L
Nope, nothing there... No ping, no traceroute, no ntp server.
ntpq> peers remote refid st t when poll reach delay offset jitter ============================================================================== kb3vwg-001.ampr .INIT. 16 u - 64 0 0.000 0.000 0.000
From 44.131.243.1
ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 0, offset 0.000000, delay 0.00000 31 Jan 09:27:56 ntpdate[22996]: no server suitable for synchronization found
Regards
Andy Brittain G0HXT g0hxt@greatbrittain.co.uk
On 31 Jan 2016, at 05:54, Marius Petrescu marius@yo2loj.ro wrote:
(Please trim inclusions from previous messages) _______________________________________________ Nope, nothing there... No ping, no traceroute, no ntp server.
ntpq> peers remote refid st t when poll reach delay offset jitter ============================================================================== kb3vwg-001.ampr .INIT. 16 u - 64 0 0.000 0.000 0.000
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Could you at least set your hosts to reply to ping requests? Btw, not answering to pings on a web server or in the 44-net is no added security feature, only a useful tool being blocked.
All,
It appears when I modified the OpenWRT scripts to parse routing rules by input interface, I isolated all 44 IPs assigned to interfaces on the router itself (which, of course, are outputs from the device, and not and input of any interface).
- Therefore, I remedied this by adding an additional IP rule: ip rule from 44.60.44.1 table 44 priority 47
- Please test now
- Lynwood KB3VWG
I can ping you from my commercial IP as well as from 44.2.14.1
At 05:08 PM 1/31/2016, you wrote:
All,
It appears when I modified the OpenWRT scripts to parse routing rules by input interface, I isolated all 44 IPs assigned to interfaces on the router itself (which, of course, are outputs from the device, and not and input of any interface).
- Therefore, I remedied this by adding an additional IP rule: ip rule from 44.60.44.1 table 44 priority 47
- Please test now
- Lynwood
KB3VWG
---------- Wm Lewis (KG6BAJ) AMPR Net IP Address Coordinator - Northern and Central California Regions (A 100% Volunteer Group) (530) 263-1595 (Home/Office) ______________________________________________
---------- This message is for the designated recipient only and MAY CONTAIN PRIVILEGED OR CONFIDENTIAL INFORMATION. If you have received it in error, please notify the sender immediately and delete the original. Any other use of this E-mail is prohibited.
Right...
It is O.K. Now! All IP's: 71.114.81.28 44.60.44.1 44.60.44.3 and 44.69.44.10 reachable from Internet and AMPRNet.
Best regards. --- Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
Dnia 1 lutego 2016 2:09:45 AM lleachii--- via 44Net 44net@hamradio.ucsd.edu napisał(a):
(Please trim inclusions from previous messages) _______________________________________________ All,
It appears when I modified the OpenWRT scripts to parse routing rules by input interface, I isolated all 44 IPs assigned to interfaces on the router itself (which, of course, are outputs from the device, and not and input of any interface).
Therefore, I remedied this by adding an additional IP rule: ip rule from 44.60.44.1 table 44 priority 47
Please test now
Lynwood
KB3VWG _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Hi Lynwood
From 44.131.243.1:
I get no reply to ping or NTP at 09:15 GMT.
Regards
Andy Brittain G0HXT g0hxt@greatbrittain.co.uk
On 1 Feb 2016, at 01:08, lleachii--- via 44Net 44net@hamradio.ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ All,
It appears when I modified the OpenWRT scripts to parse routing rules by input interface, I isolated all 44 IPs assigned to interfaces on the router itself (which, of course, are outputs from the device, and not and input of any interface).
Therefore, I remedied this by adding an additional IP rule: ip rule from 44.60.44.1 table 44 priority 47
Please test now
Lynwood
KB3VWG _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Andy,
You literally caught me rebooting, test now.
- Lynwood KB3VWG
Hi again
Sorry, I was being stupid, everything working from 44.131.243.1,
Regards
Andy Brittain G0HXT g0hxt@greatbrittain.co.uk
On 1 Feb 2016, at 01:08, lleachii--- via 44Net 44net@hamradio.ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ All,
It appears when I modified the OpenWRT scripts to parse routing rules by input interface, I isolated all 44 IPs assigned to interfaces on the router itself (which, of course, are outputs from the device, and not and input of any interface).
Therefore, I remedied this by adding an additional IP rule: ip rule from 44.60.44.1 table 44 priority 47
Please test now
Lynwood
KB3VWG _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Andy Brittain -
Corey Dean -
lleachii＠aol.com -
Marius Petrescu -
SP2L -
SP2L Tom
-
William Lewis