Securifi Community Forum

Securifi Products => Almond and Almond A1A => Topic started by: daddywags on October 20, 2013, 09:33:12 pm

Title: Constant chatter between Almond and cable modem
Post by: daddywags on October 20, 2013, 09:33:12 pm

Lately My cable modems Tx and Rx lights are always flashing.  When the Almond is removed it stops.  It only used to do this occasionally but now it is happening all the time.  Is this normal?  Can I safely upgrade the software in this state? 

Title: Re: Constant chatter between Almond and cable modem
Post by: Patrick Wilson on October 20, 2013, 11:47:00 pm

Quote from: daddywags on October 20, 2013, 09:33:12 pm

Lately My cable modems Tx and Rx lights are always flashing.  When the Almond is removed it stops.  It only used to do this occasionally but now it is happening all the time.  Is this normal?  Can I safely upgrade the software in this state?

Upgrading in that state should not be a problem.  The real trick will be to diagnose what is causing the "mystery" traffic on your Almond.  This can be easily done from the command-line of the Router,  but before we do that,  perhaps go could share what you are doing on your network that might be causing this traffic. 

For example,  are you running any form of Web Server on your network?  How about Torrents.  Are you running any form of Torrent or other P2P traffic from any of your internal machines? 

If you access the "System Logs" on the WebUI of the Almond it should give you some clues on what is going on.

Title: Re: Constant chatter between Almond and cable modem
Post by: daddywags on October 21, 2013, 12:54:29 am

I am doing none of the things you mentioned.  I used Fing from my Ipad and I only see what should be there.  The Almond, my pc and the Ipad.  Below is a sample of the log.  The time and date are wrong because I power cycled the Almond earlier today and forgot to reset it.

Jan  1 02:10:53 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.111 to 192.168.1.151
Jan  1 02:13:02 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:17:13 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:21:23 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:25:33 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:29:03 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 02:31:48 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:40:07 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:49:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 02:50:33 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:54:23 almond user.warn syslog: Warn: *** RT3052: can't find the group [224.0.0.251].
Jan  1 02:54:28 almond user.warn syslog: Warn: *** RT3052: can't find the group [224.0.0.251].
Jan  1 02:54:34 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.101 to 192.168.1.151
Jan  1 02:56:48 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:00:58 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:05:07 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:08:47 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.101
Jan  1 03:09:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.101 to 10.10.10.111
Jan  1 03:09:10 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.111 to 192.168.1.151
Jan  1 03:09:18 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:13:28 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:17:37 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:28:03 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:29:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 03:29:58 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.111 to 192.168.1.151
Jan  1 03:32:13 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:48:53 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:53:03 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:56:23 almond user.warn syslog: Warn: *** RT3052: can't find the group [224.0.0.251].
Jan  1 03:56:24 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.101
Jan  1 03:57:13 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 04:01:22 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 04:07:38 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 04:09:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 04:10:15 almond user.warn kernel: pid 2784
Jan  1 04:10:15 almond user.warn kernel: millis 3000
Jan  1 04:10:28 almond user.warn kernel: pid 2801
Jan  1 04:10:28 almond user.warn kernel: millis 1000

Title: Re: Constant chatter between Almond and cable modem
Post by: Patrick Wilson on October 21, 2013, 10:57:45 am

Quote from: daddywags on October 21, 2013, 12:54:29 am

I am doing none of the things you mentioned.  I used Fing from my Ipad and I only see what should be there.  The Almond, my pc and the Ipad.  Below is a sample of the log.  The time and date are wrong because I power cycled the Almond earlier today and forgot to reset it.

Code: [Select]

Jan  1 02:10:53 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.111 to 192.168.1.151
Jan  1 02:13:02 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:17:13 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:21:23 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:25:33 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:29:03 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 02:31:48 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:40:07 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:49:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 02:50:33 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 02:54:23 almond user.warn syslog: Warn: *** RT3052: can't find the group [224.0.0.251].
Jan  1 02:54:28 almond user.warn syslog: Warn: *** RT3052: can't find the group [224.0.0.251].
Jan  1 02:54:34 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.101 to 192.168.1.151
Jan  1 02:56:48 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:00:58 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:05:07 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:08:47 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.101
Jan  1 03:09:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.101 to 10.10.10.111
Jan  1 03:09:10 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.111 to 192.168.1.151
Jan  1 03:09:18 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:13:28 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:17:37 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:28:03 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:29:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 03:29:58 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 10.10.10.111 to 192.168.1.151
Jan  1 03:32:13 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:48:53 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:53:03 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 03:56:23 almond user.warn syslog: Warn: *** RT3052: can't find the group [224.0.0.251].
Jan  1 03:56:24 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.101
Jan  1 03:57:13 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 04:01:22 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 04:07:38 almond user.warn syslog: Warn: MRT_DEL_MFC; Errno(2): No such file or directory
Jan  1 04:09:02 almond user.warn syslog: Warn: The origin for route 239.255.255.250 changed from 192.168.1.151 to 10.10.10.111
Jan  1 04:10:15 almond user.warn kernel: pid 2784
Jan  1 04:10:15 almond user.warn kernel: millis 3000
Jan  1 04:10:28 almond user.warn kernel: pid 2801
Jan  1 04:10:28 almond user.warn kernel: millis 1000

The mention of 239.255.255.250 here is probably the "hint" as to the issue.  I believe this is related to UPnP and Multicast routing.  I will investigate this further here,  and provide further informsation within this message thread.  (I took the opportunity to review my own logs here,  and found similar entries here). 

I will investigate further.  Please stay tuned.

Patrick.

Title: Re: Constant chatter between Almond and cable modem
Post by: daddywags on October 21, 2013, 02:35:11 pm

The 192.168.1.151 address is my Linksys WRT54G router.  It is connected off  Lan 2 on the Almond.  Since the Almond was added to my network, I've been unable to access the 54G from my browser to get to it's setup menus.  The Almond replaced an older Linksys router that was not IPV6 compliant.  Don't know if this will help, but thought I should mention it.

Title: Re: Constant chatter between Almond and cable modem
Post by: Patrick Wilson on October 25, 2013, 05:39:01 am

Quote from: daddywags on October 21, 2013, 02:35:11 pm

The 192.168.1.151 address is my Linksys WRT54G router.  It is connected off  Lan 2 on the Almond.  Since the Almond was added to my network, I've been unable to access the 54G from my browser to get to it's setup menus.  The Almond replaced an older Linksys router that was not IPV6 compliant.  Don't know if this will help, but thought I should mention it.

Daddywags,  I have contacted our technical team,  about this issue that both you and I are experiencing.