El 19 jul 2017, a las 0:37, Leon Zetekoff
<wa4zlw(a)backwoodswireless.net> escribió:
Hi Jonathan...I can ping but not trace to it...Leon (.10)
On 7/18/2017 4:31 PM, Jonathan Gonzalez [EA1HET] wrote:
Hi Leon,
Maybe the host was down by the user. Try .10 instead.
BR.
15:13, July 18, 2017, Leon Zetekoff <wa4zlw(a)backwoodswireless.net>
<mailto:wa4zlw@backwoodswireless.net>:
Hi Jonathan...i tried to get to you from 44.56.53.3 and it fails....
C:\Users\leonz>tracert 44.133.233.8
Tracing route to 44.133.233.8 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms
t30.wa4zlw.homedns.org [10.195.10.3]
2 1 ms <1 ms 1 ms
core100.wa4zlw.ampr.org [44.56.53.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 ^C
C:\Users\leonz>
73 leon
On 7/18/2017 9:47 AM, Jonathan Gonzalez [EA1HET] wrote:
Hi Marc,
I don’t think there’s a minimal spec you should abide to in order to to put to work Net
44 on your site.
In my case, where we run a BGP session with Internet and publish our assigned segment,
we use a CCR1036 having in memory the full BGP routing table, but even so, this is not a
compulsory requirement for you.
In example, you can configure a less expensive router with only a default gateway to
your ISP and/or to the ISP that runs the BGP session for you (if that would be the case).
Our network design follows as a mere example of use (in ASCII art due to list
restrictions):
_( )_( )_ ( ) x.x.x.x/30 ( ) _( )_( )_(_) ( )_
(_INTERNET_)—( X ) -------------- ( X )-(_44.133.233.0/24 _)
(_) (__) ( ) ( ) (_) (__) (__) (_)
BGP Local bridged
router router w/ firewall
Both routers above are Mikrotik CCR1036 (CCR1036-8G-2S+EM) as mentioned before. If you
want to launch a traceroute from public Internet, just to demonstrate above setup, you can
use 44.133.233.8.
radio.ucsd.edu/mailman/listinfo/44net
---
This email has been checked for viruses by AVG.
http://www.avg.com <http://www.avg.com/>
--
Vy73 de EA1HET, Jonathan
<http://www.avg.com/internet-security>
This email has been checked for viruses by AVG antivirus software.
<http://www.avg.com/internet-security>
<x-msg://1/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>