I was reading about this a few days ago on the BBS system. It's possible that someone is attempting to offer a "backup" solution in the event that 44.0.0.1 should go down. It may also be a prelude to a malicious attack.

Luc, the short and simple solution is to simply ignore that traffic. Your computer is filtering it out because it isn't coming from a credible source. It may be an honest ham trying to offer a backup solution, but until that's verified, it's best to just let the filter do its thing.

Blaine, K1QV

Sent from my iPhone

On Aug 14, 2013, at 12:08 AM, Brian Kantor Brian@ucsd.edu wrote:

(Please trim inclusions from previous messages) _______________________________________________ On Tue, Aug 13, 2013 at 08:56:46PM -0400, Luc Pernot wrote:

...

There is a message showing on my RPI gateway 44.135.96.17 tunnel TTY0 saying

"ignored packet from 44.131.160.1: 520: 504" every 5 minutes or so. any suggestion how to resolve this...

Luc VE3JGL in Ottawa

I suspect 44.131.160.1 is sending RIP packets to you. I have no idea why it would be doing so except perhaps misconfiguration.

• Brian

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

Apologies, replied to wrong message.

phil

On 8/14/13 3:07 AM, Brian Kantor wrote:

(Please trim inclusions from previous messages) _______________________________________________ On Tue, Aug 13, 2013 at 08:56:46PM -0400, Luc Pernot wrote:

...

There is a message showing on my RPI gateway 44.135.96.17 tunnel TTY0 saying

"ignored packet from 44.131.160.1: 520: 504" every 5 minutes or so. any suggestion how to resolve this...

Luc VE3JGL in Ottawa

I suspect 44.131.160.1 is sending RIP packets to you. I have no idea why it would be doing so except perhaps misconfiguration.

• Brian

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html