| |
I0OJJ > TCPIP 11.08.13 14:45l 48 Lines 1850 Bytes #999 (0) @ WW
BID : 16929_I0OJJ
Read: GUEST
Subj: Re: RIPv2 updates from 44.131.160.1
Path: IZ3LSV<IR1UAW<IQ5KG<I0OJJ
Sent: 130811/1343Z 16929@I0OJJ.ILAZ.ITA.EU $:16929_I0OJJ
From: I0OJJ@I0OJJ.ILAZ.ITA.EU
To : TCPIP@WW
Hi Matt,
I guess they are attempts for a new setup on the new
official 'portal.ampr.org'... and being the 44.131.x.x
the 44 network on United Kingdom.
However here, on my site in Rome, arrive several kinda
broadcasts at least from three 'ampr.org' routers
belonging to the chief site of 'ucsd.edu'.
I made some tests on the past days on the attempt of a
full understanding and further integration of RIPv2
protocols between other networks... it is easy you may
heard some other broadcasts too :)
However the 44.131.160.1 results fully pingable from
here, and so, fully integrated to the ampr.org network:
PING 44.131.160.1 (44.131.160.1) 56(84) bytes of data.
64 bytes from 44.131.160.1: icmp_seq=1 ttl=62 time=186 ms
64 bytes from 44.131.160.1: icmp_seq=2 ttl=62 time=202 ms
64 bytes from 44.131.160.1: icmp_seq=4 ttl=62 time=187 ms
64 bytes from 44.131.160.1: icmp_seq=5 ttl=62 time=184 ms
--- 44.131.160.1 ping statistics ---
6 packets transmitted, 4 received, 33% packet loss, time 5013ms
rtt min/avg/max/mdev = 184.452/190.199/202.544/7.222 ms
What is your mensioned rip44d process?
73, gus i0ojj
-----------------------start of original msg--------------------------
I started receiving on my ampenet gateway RIPv2 updates from 44.131.160.1.
Unlike the 44.0.0.1 updates, they do not contain any password. My rip44d
process is rejecting them, since they are not coming from 44.0.0.1.
Does anyone understand why 44.131.160.1 has started sending out these RIPv2
advertisements? Is it due to a misconfigured router, or is the intention
that this should act as a backup source of route advertisements? If the
latter, then it should probably be including a password the same as
44.0.0.1, and the rip44d script will need to be updated to accept updates
from that source address.
73, Matt VK2RQ
Read previous mail | Read next mail
| |
