4 Jun
2017
4 Jun
'17
1:41 a.m.
Hello everyone,
Since experimenting goes one, here a new ampr-ripd version that forces
the sending of call home data to use the tunnel's IP as its source IP
address.
Tnx. Lynwood for pointing out that necessity.
Interactive map which is available at
http://yo2tm.ampr.org/ampr-map/
For those that do not want to participate, there is no need to upgrade.
And even if you do, not setting the -L parameter will not send any data,
the result being the same behavior like 2.1.1.
Download:
http://www.yo2loj.ro/hamprojects/ampr-ripd-2.3.tgz
http://yo2tm.ampr.org/hamprojects/ampr-ripd-2.3.tgz
Have fun,
Marius, YO2LOJ
4 Jun
4 Jun
4:27 a.m.
On 4/06/2017 3:41 PM, Marius Petrescu wrote:
Hello everyone,
Since experimenting goes one, here a new ampr-ripd version that forces
the sending of call home data to use the tunnel's IP as its source IP
address.
Tnx. Lynwood for pointing out that necessity.
Interactive map which is available at
http://yo2tm.ampr.org/ampr-map/
Neat, I've finally got around to joining the
party. :)
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
7:05 a.m.
Marius,
Thanks again. Apologies for the use of the term "carrier", this is an
old phrase commonly used in FCC-land to mean "telephone company" or
"ISP".
Now...
- the map at http://yo2tm.ampr.org/ampr-map/ doesn't load for me on the
Public Internet (block of the WAN discovery packets?)
- connecting from 44.60.44.14 on AMPRNet, my dot disappeared
- I assigned an IP to tunl0 (44.60.44.254) and rebooted (I guess you
implemented the code on the -i argument)
- My dot now appears green
Use of an extra IP, but this is a valid use!
Thanks and 73,
- Lynwood
KB3VWG
8:06 a.m.
Lynwood,
I choose to go with using the tunnel IP since that code is already there
and it seems somehow legit to have an IP on that interface.
BTW, you could assign the same IP as your other interface with a netmask
of /32 to the tunnel. It should work without issues (but there could be
some firewall adjustment needed if you use interface names).
The map form the internet has issues independent from myself: It seems
gateway forwarding has some problems starting with Yesterday.
Let's wait for Monday.
On 04.06.2017 14:05, lleachii--- via 44Net wrote:
Marius,
Thanks again. Apologies for the use of the term "carrier", this is an
old phrase commonly used in FCC-land to mean "telephone company" or
"ISP".
Now...
- the map at http://yo2tm.ampr.org/ampr-map/ doesn't load for me on
the Public Internet (block of the WAN discovery packets?)
- connecting from 44.60.44.14 on AMPRNet, my dot disappeared
- I assigned an IP to tunl0 (44.60.44.254) and rebooted (I guess you
implemented the code on the -i argument)
- My dot now appears green
Use of an extra IP, but this is a valid use!
Thanks and 73,
- Lynwood
KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
8:24 a.m.
Marius,
I concur, it is legit to have a de-encapsulated IP on tunl0. No
disagreement here!
(I know we've discussed that for years).
I did in fact assign 44.60.44.254/32 to tunl0 (as you noted to me a few
years ago - use a /32). On Monday, I will change the Optional note in
Startampr, to Required). I believe Monday will work out the various
issues you see as well. I think yours lies in Old_AMPRGW vs New and your
explicitly-declared tunnels for each subnet.
Monday should be a Sunny Day!
73,
- Lynwood
KB3VWG
8:57 a.m.
Marius,
An anomaly on the Linux Kernel using the same IP:
- ping now fails on the router specifying br-amprnet as SRC interface
- I can now specify tunl0 as SRC interface
- I can still specify 44.60.44.1 as SRC IP
- KB3VWG
9:11 a.m.
I'd appreciate it if you'd let me know the details so I can begin
to find the problem in advance of Monday.
- Brian
On Sun, Jun 04, 2017 at 03:06:20PM +0300, Marius Petrescu wrote:
The map form the internet has issues independent from
myself: It seems
gateway forwarding has some problems starting with Yesterday.
Let's wait for Monday.
9:16 a.m.
The problem is I have a criss-cross of causes hitting my system in a
synchronous fashion.
- my main ISP died yesterday for a few hours
- my main router was kind of hit in the head with some connection tracks
- I changed things in config.
Somehow starting with yesterday at 10Am your time RIP announcements
where missing.
Then they started flowing in incomplete.
This sorted itself out some 30min ago.
On 04.06.2017 16:11, Brian Kantor wrote:
I'd appreciate it if you'd let me know the
details so I can begin
to find the problem in advance of Monday.
- Brian
On Sun, Jun 04, 2017 at 03:06:20PM +0300, Marius Petrescu wrote:
The map form the internet has issues independent
from myself: It seems
gateway forwarding has some problems starting with Yesterday.
Let's wait for Monday.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
9:30 a.m.
I turned off RIP announcements from oldamprgw for an
hour while we did troubleshooting on Lynwood's problems,
but they've always been on from newamprgw, and they've been
back on from oldamprgw for almost a day. So the problem
must have been on your end or in the middle somewhere.
30 minutes ago I was having breakfast, feeding the cats,
and not hacking. :-)
Best wishes!
- Brian
On Sun, Jun 04, 2017 at 04:16:17PM +0300, Marius Petrescu wrote:
The problem is I have a criss-cross of causes hitting
my system in a
synchronous fashion.
- my main ISP died yesterday for a few hours
- my main router was kind of hit in the head with some connection tracks
- I changed things in config.
Somehow starting with yesterday at 10Am your time RIP announcements where
missing.
Then they started flowing in incomplete.
This sorted itself out some 30min ago.
10:25 a.m.
Marius,
So you can troubleshoot, for clarity:
I turned off RIP announcements from oldamprgw for an
hour while we did troubleshooting on Lynwood's problems,
We discovered that
those with dynamic filtering no longer received
IPENCAP from Old_AMPRGW, if they already edited their scripts for
post-Monday.
Brian added a 'dummy route' of 44.0.0.2/32 via Old_AMPRGW to solve that.
The Test AMPR Network of 44.128.0.0/16 disappeared from encap.txt, thus
leaving Old_AMPRGW erased. This will not solve other user issues with
devices that have tunnels linked to subnets - until Monday.
- KB3VWG
4:58 p.m.
Hey guys...I spoke to marius on this yesterday as he saw the same thing
but I am still not seeing RIP from the old GW
73 leon
On 6/4/2017 9:30 AM, Brian Kantor wrote:
I turned off RIP announcements from oldamprgw for an
hour while we did troubleshooting on Lynwood's problems,
but they've always been on from newamprgw, and they've been
back on from oldamprgw for almost a day. So the problem
must have been on your end or in the middle somewhere.
30 minutes ago I was having breakfast, feeding the cats,
and not hacking. :-)
---
This email has been checked for viruses by AVG.
http://www.avg.com
5:07 p.m.
Leon,
You should see RIP from the new interface.
Just switch over by changing the tunnel endpoint ip from 169.228.66.251
to 169.228.34.84.
On 04.06.2017 23:58, Leon Zetekoff wrote:
Hey guys...I spoke to marius on this yesterday as he
saw the same
thing but I am still not seeing RIP from the old GW
73 leon
On 6/4/2017 9:30 AM, Brian Kantor wrote:
I turned off RIP announcements from oldamprgw for
an
hour while we did troubleshooting on Lynwood's problems,
but they've always been on from newamprgw, and they've been
back on from oldamprgw for almost a day. So the problem
must have been on your end or in the middle somewhere.
30 minutes ago I was having breakfast, feeding the cats,
and not hacking. :-)
---
This email has been checked for viruses by AVG.
http://www.avg.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
5:16 p.m.
Hey marius...did that the link came up but still get the same error when
the script fired off
leon
On 6/4/2017 5:07 PM, Marius Petrescu wrote:
Leon,
You should see RIP from the new interface.
Just switch over by changing the tunnel endpoint ip from
169.228.66.251 to 169.228.34.84.
On 04.06.2017 23:58, Leon Zetekoff wrote:
Hey guys...I spoke to marius on this yesterday as
he saw the same
thing but I am still not seeing RIP from the old GW
73 leon
On 6/4/2017 9:30 AM, Brian Kantor wrote:
I turned off RIP announcements from oldamprgw for
an
hour while we did troubleshooting on Lynwood's problems,
but they've always been on from newamprgw, and they've been
back on from oldamprgw for almost a day. So the problem
must have been on your end or in the middle somewhere.
30 minutes ago I was having breakfast, feeding the cats,
and not hacking. :-)
---
This email has been checked for viruses by AVG.
http://www.avg.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
5 Jun
5 Jun
10:39 a.m.
GM folks...changed to new IP yesterday and still getting too few entries
available from the new GW. Any ideas?
thanks leon
On 6/4/2017 5:16 PM, Leon Zetekoff wrote:
Hey marius...did that the link came up but still get
the same error
when the script fired off
leon
On 6/4/2017 5:07 PM, Marius Petrescu wrote:
Leon,
You should see RIP from the new interface.
Just switch over by changing the tunnel endpoint ip from
169.228.66.251 to 169.228.34.84.
On 04.06.2017 23:58, Leon Zetekoff wrote:
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net Hey guys...I spoke to marius on this yesterday as
he saw the same
thing but I am still not seeing RIP from the old GW
73 leon
On 6/4/2017 9:30 AM, Brian Kantor wrote:
I turned off RIP announcements from oldamprgw for
an
hour while we did troubleshooting on Lynwood's problems,
but they've always been on from newamprgw, and they've been
back on from oldamprgw for almost a day. So the problem
must have been on your end or in the middle somewhere.
30 minutes ago I was having breakfast, feeding the cats,
and not hacking. :-)
---
This email has been checked for viruses by AVG.
http://www.avg.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
10:58 a.m.
Search for a tunnel called ampr-169.228.34.84, delete it and also delete
its associated routes.
On 05.06.2017 17:39, Leon Zetekoff wrote:
GM folks...changed to new IP yesterday and still
getting too few
entries available from the new GW. Any ideas?
thanks leon
On 6/4/2017 5:16 PM, Leon Zetekoff wrote:
Hey marius...did that the link came up but still
get the same error
when the script fired off
leon
On 6/4/2017 5:07 PM, Marius Petrescu wrote:
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net Leon,
You should see RIP from the new interface.
Just switch over by changing the tunnel endpoint ip from
169.228.66.251 to 169.228.34.84.
On 04.06.2017 23:58, Leon Zetekoff wrote:
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net Hey guys...I spoke to marius on this yesterday as
he saw the same
thing but I am still not seeing RIP from the old GW
73 leon
On 6/4/2017 9:30 AM, Brian Kantor wrote:
> I turned off RIP announcements from oldamprgw for an
> hour while we did troubleshooting on Lynwood's problems,
> but they've always been on from newamprgw, and they've been
> back on from oldamprgw for almost a day. So the problem
> must have been on your end or in the middle somewhere.
>
> 30 minutes ago I was having breakfast, feeding the cats,
> and not hacking. :-)
>
>
---
This email has been checked for viruses by AVG.
http://www.avg.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
11:43 a.m.
And filter out 44.0.0.1 and 44.0.0.2 in the RIP filter. Otherwise when you get the RIP
broadcasts, the script will re-add the tunnel and routes
Ruben - ON3RVH
On 5 Jun 2017, at 16:59, Marius Petrescu
<marius(a)yo2loj.ro> wrote:
Search for a tunnel called ampr-169.228.34.84, delete it and also delete its associated
routes.
On 05.06.2017 17:39, Leon Zetekoff wrote:
GM folks...changed to new IP yesterday and still getting too few entries available from
the new GW. Any ideas?
thanks leon
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net On 6/4/2017 5:16 PM, Leon Zetekoff wrote:
Hey marius...did that the link came up but still get the same error when the script fired
off
leon
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net On 6/4/2017 5:07 PM, Marius Petrescu wrote:
Leon,
You should see RIP from the new interface.
Just switch over by changing the tunnel endpoint ip from 169.228.66.251 to
169.228.34.84.
> On 04.06.2017 23:58, Leon Zetekoff wrote:
> Hey guys...I spoke to marius on this yesterday as he saw the same thing but I am
still not seeing RIP from the old GW
>
> 73 leon
>
>
>> On 6/4/2017 9:30 AM, Brian Kantor wrote:
>> I turned off RIP announcements from oldamprgw for an
>> hour while we did troubleshooting on Lynwood's problems,
>> but they've always been on from newamprgw, and they've been
>> back on from oldamprgw for almost a day. So the problem
>> must have been on your end or in the middle somewhere.
>>
>> 30 minutes ago I was having breakfast, feeding the cats,
>> and not hacking. :-)
>>
>>
>
>
> ---
> This email has been checked for viruses by AVG.
> http://www.avg.com
>
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
11:53 a.m.
Looks like my fault...I have two ips (dynamic) from my ISP but when I
change things or something happens I have to go through the hoops to get
an IP back on the mikrotik. I think things are populating now
sorry for the false alarm
Leon
On 6/5/2017 11:43 AM, Ruben ON3RVH wrote:
And filter out 44.0.0.1 and 44.0.0.2 in the RIP
filter. Otherwise when you get the RIP broadcasts, the script will re-add the tunnel and
routes
Ruben - ON3RVH
> On 5 Jun 2017, at 16:59, Marius Petrescu <marius(a)yo2loj.ro> wrote:
>
> Search for a tunnel called ampr-169.228.34.84, delete it and also delete its
associated routes.
>
>
>
>> On 05.06.2017 17:39, Leon Zetekoff wrote:
>> GM folks...changed to new IP yesterday and still getting too few entries
available from the new GW. Any ideas?
>>
>> thanks leon
>>
>>
>>> On 6/4/2017 5:16 PM, Leon Zetekoff wrote:
>>> Hey marius...did that the link came up but still get the same error when the
script fired off
>>>
>>> leon
>>>
>>>
>>>> On 6/4/2017 5:07 PM, Marius Petrescu wrote:
>>>> Leon,
>>>>
>>>> You should see RIP from the new interface.
>>>>
>>>> Just switch over by changing the tunnel endpoint ip from 169.228.66.251
to 169.228.34.84.
>>>>
>>>>
>>>>
>>>>> On 04.06.2017 23:58, Leon Zetekoff wrote:
>>>>> Hey guys...I spoke to marius on this yesterday as he saw the same
thing but I am still not seeing RIP from the old GW
>>>>>
>>>>> 73 leon
>>>>>
>>>>>
>>>>>> On 6/4/2017 9:30 AM, Brian Kantor wrote:
>>>>>> I turned off RIP announcements from oldamprgw for an
>>>>>> hour while we did troubleshooting on Lynwood's problems,
>>>>>> but they've always been on from newamprgw, and they've
been
>>>>>> back on from oldamprgw for almost a day. So the problem
>>>>>> must have been on your end or in the middle somewhere.
>>>>>>
>>>>>> 30 minutes ago I was having breakfast, feeding the cats,
>>>>>> and not hacking. :-)
>>>>>>
>>>>>>
>>>>>
>>>>> ---
>>>>> This email has been checked for viruses by AVG.
>>>>> http://www.avg.com
>>>>>
>>>>> _________________________________________
>>>>> 44Net mailing list
>>>>> 44Net(a)hamradio.ucsd.edu
>>>>> http://hamradio.ucsd.edu/mailman/listinfo/44net
>>> _________________________________________
>>> 44Net mailing list
>>> 44Net(a)hamradio.ucsd.edu
>>> http://hamradio.ucsd.edu/mailman/listinfo/44net
>> _________________________________________
>> 44Net mailing list
>> 44Net(a)hamradio.ucsd.edu
>> http://hamradio.ucsd.edu/mailman/listinfo/44net
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
1:09 p.m.
things working now moved one cable on my CRS switch and looks like we're
back
thanks
On 6/5/2017 11:53 AM, Leon Zetekoff wrote:
Looks like my fault...I have two ips (dynamic) from my
ISP but when I
change things or something happens I have to go through the hoops to
get an IP back on the mikrotik. I think things are populating now
sorry for the false alarm
Leon
On 6/5/2017 11:43 AM, Ruben ON3RVH wrote:
And filter out 44.0.0.1 and 44.0.0.2 in the RIP
filter. Otherwise
when you get the RIP broadcasts, the script will re-add the tunnel
and routes
Ruben - ON3RVH
> On 5 Jun 2017, at 16:59, Marius Petrescu <marius(a)yo2loj.ro> wrote:
>
> Search for a tunnel called ampr-169.228.34.84, delete it and also
> delete its associated routes.
>
>
>
>> On 05.06.2017 17:39, Leon Zetekoff wrote:
>> GM folks...changed to new IP yesterday and still getting too few
>> entries available from the new GW. Any ideas?
>>
>> thanks leon
>>
>>
>>> On 6/4/2017 5:16 PM, Leon Zetekoff wrote:
>>> Hey marius...did that the link came up but still get the same
>>> error when the script fired off
>>>
>>> leon
>>>
>>>
>>>> On 6/4/2017 5:07 PM, Marius Petrescu wrote:
>>>> Leon,
>>>>
>>>> You should see RIP from the new interface.
>>>>
>>>> Just switch over by changing the tunnel endpoint ip from
>>>> 169.228.66.251 to 169.228.34.84.
>>>>
>>>>
>>>>
>>>>> On 04.06.2017 23:58, Leon Zetekoff wrote:
>>>>> Hey guys...I spoke to marius on this yesterday as he saw the
>>>>> same thing but I am still not seeing RIP from the old GW
>>>>>
>>>>> 73 leon
>>>>>
>>>>>
>>>>>> On 6/4/2017 9:30 AM, Brian Kantor wrote:
>>>>>> I turned off RIP announcements from oldamprgw for an
>>>>>> hour while we did troubleshooting on Lynwood's problems,
>>>>>> but they've always been on from newamprgw, and they've
been
>>>>>> back on from oldamprgw for almost a day. So the problem
>>>>>> must have been on your end or in the middle somewhere.
>>>>>>
>>>>>> 30 minutes ago I was having breakfast, feeding the cats,
>>>>>> and not hacking. :-)
>>>>>>
>>>>>>
>>>>>
>>>>> ---
>>>>> This email has been checked for viruses by AVG.
>>>>> http://www.avg.com
>>>>>
>>>>> _________________________________________
>>>>> 44Net mailing list
>>>>> 44Net(a)hamradio.ucsd.edu
>>>>> http://hamradio.ucsd.edu/mailman/listinfo/44net
>>> _________________________________________
>>> 44Net mailing list
>>> 44Net(a)hamradio.ucsd.edu
>>> http://hamradio.ucsd.edu/mailman/listinfo/44net
>> _________________________________________
>> 44Net mailing list
>> 44Net(a)hamradio.ucsd.edu
>> http://hamradio.ucsd.edu/mailman/listinfo/44net
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
2538
days inactive
2539
days old
19 comments
6 participants
participants (6)
-
Brian Kantor -
Leon Zetekoff -
lleachii＠aol.com -
Marius Petrescu -
Ruben ON3RVH -
Tony Langdon