Jump to content
LordPaul

protocol 0800 is buggy

Recommended Posts

Any ideas what "protocol 0800 is buggy" and "daemon.notice wansensing" means

Sat Jan 23 20:41:48 2021 daemon.info dnsmasq-dhcp[22817]: DHCPREQUEST(br-lan) 192.168.0.251 00:51:ed:5a:9f:88
Sat Jan 23 20:41:43 2021 kern.crit kernel: [566112.547000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:41:40 2021 daemon.notice miniupnpd[7414]: redirecting port 56392 to 192.168.0.11:56392 protocol UDP on ptm0 for: Teredo 192.168.0.11:56392->56392 UDP
Sat Jan 23 20:41:28 2021 kern.crit kernel: [566097.107000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:41:25 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan6_ok)
Sat Jan 23 20:41:25 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan_ok)
Sat Jan 23 20:41:19 2021 kern.crit kernel: [566087.986000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:41:06 2021 kern.crit kernel: [566075.583000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:40:57 2021 kern.crit kernel: [566066.467000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:40:55 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan6_ok)
Sat Jan 23 20:40:55 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan_ok)
Sat Jan 23 20:40:41 2021 kern.crit kernel: [566050.206000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:40:41 2021 kern.crit kernel: [566050.206000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:40:34 2021 daemon.notice odhcpd[3685]: Got DHCPv6 request
Sat Jan 23 20:40:30 2021 daemon.info odhcpd[3685]: Using a RA lifetime of 1800 seconds on wl0_1
Sat Jan 23 20:40:25 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan6_ok)
Sat Jan 23 20:40:25 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan_ok)
Sat Jan 23 20:40:00 2021 cron.info crond[2425]: USER root pid 24393 cmd /sbin/trafficmon.lua
Sat Jan 23 20:40:00 2021 cron.info crond[2425]: USER root pid 24391 cmd /usr/bin/thermalProtection /sys/devices/i2c-0/0-0048/hwmon/hwmon0/temp1_input /sys/devices/i2c-0/0-004f/hwmon/hwmon1/temp1_input
Sat Jan 23 20:39:55 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan6_ok)
Sat Jan 23 20:39:55 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,supervision_wan_ok)
Sat Jan 23 20:39:44 2021 kern.crit kernel: [565993.424000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:39:28 2021 kern.crit kernel: [565977.226000] protocol 0800 is buggy, dev br-lan
Sat Jan 23 20:39:28 2021 kern.crit kernel: [565977.226000] protocol 0800 is buggy, dev br-lan

Share this post


Link to post
Share on other sites

The log files are primarily for developers and not for users to try and diagnose issues - it can appear to a user that there is an issue when it is just showing normal background processes which is the case here so nothing to worry about!

Share this post


Link to post
Share on other sites

On the contrary, this is a bug in the software of the technicolor modem. It is one that I have reported to Telstra. I encountered it using software called Jamkazam that allows playing music together over the internet. It requires low latency similar to gaming. It was introduced by an update to the firmware. It did not occur before the update, and it did after. When it occurred for me (or rather a friends who had this modem. I have the Arcadyan version of the modem) it was followed by errors of the for "Tue Aug 11 18:25:24 2020 kern.warn kernel: [185835.753000] nf_conntrack: expectation table full". What it appeared was that packets being transmitted were being lost in the modem which did not send them on. The end result was that we could hear all the people playing using other modems, but not the person who had the technicolor version of the modem. The only fix we could find that would work was a new modem.

Share this post


Link to post
Share on other sites
On 2/18/2021 at 5:41 AM, Geoff I said:

On the contrary, this is a bug in the software of the technicolor modem. It is one that I have reported to Telstra. I encountered it using software called Jamkazam that allows playing music together over the internet. It requires low latency similar to gaming. It was introduced by an update to the firmware. It did not occur before the update, and it did after. When it occurred for me (or rather a friends who had this modem. I have the Arcadyan version of the modem) it was followed by errors of the for "Tue Aug 11 18:25:24 2020 kern.warn kernel: [185835.753000] nf_conntrack: expectation table full". What it appeared was that packets being transmitted were being lost in the modem which did not send them on. The end result was that we could hear all the people playing using other modems, but not the person who had the technicolor version of the modem. The only fix we could find that would work was a new modem.

Hey, just out of interest, for those having difficulty with the Telstra modem's, are there other devices using the internet at that time through those modem's? Were the connections over wired or wireless?

Share this post


Link to post
Share on other sites

I now have this in my log file. it appears to be dumaos forcing jumbo frames, but I am unable to turn them off on the router.

When duamaos was not active, this error disappears.

Share this post


Link to post
Share on other sites
10 hours ago, BundyBob said:

I now have this in my log file. it appears to be dumaos forcing jumbo frames, but I am unable to turn them off on the router.

When duamaos was not active, this error disappears.

Are you experiencing any issues alongside this? As Fraser mentions, logs are primarily for developer insights as it can appear to a user that there is an issue when it is just showing normal background processes.

Share this post


Link to post
Share on other sites

initially being disconnected from modem on two / nine devices.

checked logs to see if there was anything obvious,

the buggy protocol was one, cli.lua was another and Extender cache value failed callback was the third..

The protocol error is the only one that does not come with a netdumaos tag.

 

A quick search reveals that jumbo frames is the cause of the buggy protocol usually, but all networks are set to mtu 1500 so I am guessing that netdumaos is looking for larger but not finding them.

 

the cli.lua and extender cache errors are specifically dumaos. I don't like errors filling my logs. 

Share this post


Link to post
Share on other sites

I can certainly understand the concern, what were the devices that disconnected? How were they connected to the modem, via wired or wireless?

Share this post


Link to post
Share on other sites
On 8/27/2021 at 10:52 PM, Netduma Liam said:

I can certainly understand the concern, what were the devices that disconnected? How were they connected to the modem, via wired or wireless?

The devices are TCL tv and Fetch TV settop box.

The TV just comes up with no wifi.

The fetch tv set top box will display no wifi signal and reboot if it does not detect wifi signal.

 

Share this post


Link to post
Share on other sites

One disconnection for each overnight (i think)

in the log file there are 40,471 entries from Sun Aug 29 21:46:13 2021 to Mon Aug 30 10:10:43 2021.

Of those,

19,711 are from daemon.err cli.lua wl: wl driver adapter not found or Command failed: Not found

13,918 are from com.netdumasoftware.devicemanager Extender cache value failed callback: Unterminated JSON encoded object found at position in []

1,104 are from kern.crit kernel protocol 86dd is buggy or protocol 0800 is buggy

688 are from com.netdumasoftware.neighwatch DHCP old event or DHCP lease change (all items have reserved ip's or static programed ip's

84 are from kern.warn kernel net_ratelimit: xx callbacks suppressed

Total Netdumaos entries 35,505 or 87.73% of entries.

Normally I get 3 days of entries in a full log file

With netdumaos active I get a little over 10 hrs 

If an error I am looking forward happens overnight, I am likely to miss it.

 

Share this post


Link to post
Share on other sites

I see from your other topic you're using the Adblocker, could you disable this for a day or two and see whether the disconnections stop and whether the log file is smaller please?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...