are these 2 entries for a single route or 2 separate routes to a single
destination? It seems to me they are actually separate redundant routes to
the same /21. should redundant routes not be allowed? It would seem quite
the reverse that redundancy being useful and importaint these ought to be
allowed to stand so long as they are valid routes to the specified /21.
Eric
AF6EP
On Thu, Aug 15, 2013 at 2:54 AM, G1FEF <chris(a)g1fef.co.uk> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi Marc,
No, there should not be two entries for one route and the portal should
not allow this to happen, so I will look into how it occurred and amend the
code as necessary.
Thanks,
Chris
On 15 Aug 2013, at 10:31, "Marc, LX1DUC" <lx1duc(a)rlx.lu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
while analyzing the routing table on my Mikrotik router, I noticed
that there are 2 gateways for 44.136.0.0/21:
114.198.116.219
203.5.58.162
The encap file has both as well:
route addprivate 44.136/21 encap 203.5.58.162
route addprivate 44.136/21 encap 114.198.116.219
I have tried to create 2 routes for some of my networks via the
portal, but the portal complains with the words "The network overlaps
an existing entry".
I'm now interested to know, if these 2 routes are intended to
co-exist? If yes, how can one create those entries via the portal.
If no, which one is correct and why are there 2 entries?
73 de Marc, LX1DUC
- --
http://lx1duc.mcs.tel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools -
http://gpgtools.org
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iQIcBAEBAgAGBQJSDJ/oAAoJEHFIN1T8ZA8v8EoP/0HHZn+S4SB0EiqJKjZR8gJG
GL7imNQ0sTZUBE6QMQzXs5+Dr6D++jEYyO36AlqgR0Z2SABs/HFhbuHYV+9Bvb+n
m01m8eKDFJam3uqXGQjsvV5gH/nC8nVJ0hgdsMolatu8B8WBUR02QQDkgq2u11pP
GLwffzANg4/FPLLShYZKk2IL6unh0GFqvW2bePQUZ+8OQv2X1UyDR2jWg4gi7sOO
6imU3CVfKfc53SfPox2De7nLGxsKZsk2O/RCxHEom0MKYCdWtNmoszOTDpxNmkPd
cVJfEZ7zOIBHW+ZYFtsCy1GfoanDlel0jOMm5zNe4WkxeCjPtvD/46vxpPOAh2xk
84lDA3oWY2LYKny6c6YD7zFEcHcX84gR+6gdFFvuaiKU99RizFK0XORJxdVqU4tT
TSBCCt+oW6sPCAJe2vuorA9TyqLMwc6RDg98ZdoEEAYQJke7/CgTBkP+A6EY/U15
HCWk6cXIvHsu2j33K4HoqoaJa74yZMctTnumMu+E4x2Kw+OtCFJfsNt3dTAqeWkr
uuKpeqnjWqPAnT6l3uQOTknwfara79Cw9zWfaG2nnRS8gcIki+Voe+gWAOdiObbF
m0dcmsCBqcyFaRtBHyR0N4BuQC/o5H6rQBgzNFDW54EKraRPLokuM9fW6PF1YJ1l
+TItkIm+J2u9xwlSJbXq
=invI
-----END PGP SIGNATURE-----
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html