Baris, Rueben mentioned several replies ago to check your 44. address. They are not the same as what the gateway is set up for you. Cheers, Don
On Wed, Dec 13, 2017 at 7:45 AM Brian Kantor Brian@ucsd.edu wrote:
On Wed, Dec 13, 2017 at 03:07:38PM +0300, Barış DİNÇ wrote:
I have a message on debug output : (total 648 entries). RIP len 504 header version 2, Command 2 (Response) Simple password: pLaInTeXtpAsSwD Simple password authentication successful. Is the password "pLaInTeXtpAsSwD" ? :)
Yes, it is a dummy password, not intended for security but to satisfy the protocol requirements.
Since you are seeing that, you are receiving the RIP transmissions from the ampr gateway system. In addition, I am able to ping your gateway address from amprgw, so there is no problem with connectivity between amprgw and your gateway system.
The filter table on amprgw allows traffic from the internet to the three addresses 44.176.206.1, 44.176.206.200, and 44.176.206.202.
I have confirmed that traffic to 44.176.206.1 is being encapsulated and sent to 178.233.172.203.
You should try running tcpdump on your 44.176.206.1 system to see if you see incoming internet connection attempts. There are always some of those every minute or so and you should be getting them.
I suspect the problem may be the path back to amprgw from your 44.176.206.1 system. Check your routing tables to be sure that packets intended for the internet (non-44 addresses) are encapsulated and sent to amprgw on 169.228.34.84. Try running tcpdump and see what traffic is being sent to and received from 169.228.34.84. - Brian
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net