What's new

Asuswrt-Merlin 3.0.0.4.374.35 is out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Hmmm, this pops up on my syslog. :confused:

Code:
Nov 30 15:09:14 nmbd[347]: [2013/11/30 15:09:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:09:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:11:14 nmbd[347]: [2013/11/30 15:11:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:11:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:13:14 nmbd[347]: [2013/11/30 15:13:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:13:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:15:14 nmbd[347]: [2013/11/30 15:15:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:15:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:17:14 nmbd[347]: [2013/11/30 15:17:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:17:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:19:14 nmbd[347]: [2013/11/30 15:19:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:19:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:21:14 nmbd[347]: [2013/11/30 15:21:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:21:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:23:14 nmbd[347]: [2013/11/30 15:23:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:23:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:25:14 nmbd[347]: [2013/11/30 15:25:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:25:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:27:14 nmbd[347]: [2013/11/30 15:27:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:27:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:29:14 nmbd[347]: [2013/11/30 15:29:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:29:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:31:14 nmbd[347]: [2013/11/30 15:31:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:31:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:33:14 nmbd[347]: [2013/11/30 15:33:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:33:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:35:14 nmbd[347]: [2013/11/30 15:35:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:35:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
 
I see that Asus has implement openVPN into the RT-AC68U. It is nice to see them embrace open source, this is real kool. Does this merlin build use the asus version for the RT-n66u or is it the merlin version as 3.0.0.4.374.33_0 that I am use to?

The new hybrid webui that merges both my old webui and Asus's own webui is used accross all router models with OpenVPN support.

This may not be the place but RMerlin you posted in another forum that popped up on a google search that if the jff directory is place up high in the memory that it may stay intact during firmware upgrade. This could be worth a try, if it is not too much trouble could you explain how we place this directory?

This is something done by the firmware, not by the end-user. I implemented it that way on the RT-AC56/RT-AC68U, but it's too late to change it on the RT-AC66U as it would cause everyone to lose their JFFS content.
 
Hmmm, this pops up on my syslog. :confused:

Code:
Nov 30 15:09:14 nmbd[347]: [2013/11/30 15:09:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:09:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:11:14 nmbd[347]: [2013/11/30 15:11:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:11:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:13:14 nmbd[347]: [2013/11/30 15:13:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:13:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:15:14 nmbd[347]: [2013/11/30 15:15:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:15:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:17:14 nmbd[347]: [2013/11/30 15:17:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:17:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:19:14 nmbd[347]: [2013/11/30 15:19:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:19:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:21:14 nmbd[347]: [2013/11/30 15:21:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:21:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:23:14 nmbd[347]: [2013/11/30 15:23:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:23:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:25:14 nmbd[347]: [2013/11/30 15:25:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:25:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:27:14 nmbd[347]: [2013/11/30 15:27:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:27:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:29:14 nmbd[347]: [2013/11/30 15:29:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:29:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:31:14 nmbd[347]: [2013/11/30 15:31:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:31:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:33:14 nmbd[347]: [2013/11/30 15:33:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:33:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.
Nov 30 15:35:14 nmbd[347]: [2013/11/30 15:35:14, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(702)
Nov 30 15:35:14 nmbd[347]:   process_get_backup_list_request: Invalid name type 0 - should be 0x1b or 0x1d.

This is something specific to Samba and your network. Try a Google search on the error message, I have no idea what it means.
 
This is something specific to Samba and your network. Try a Google search on the error message, I have no idea what it means.

Thx, I'll look into it.
However I did not see this syslog message before on previous firmware.
My network didn't change in between as far as I know.

Edit: I used Google on the "nmbd_incomingdgrams.c" part and found some code.

The help part on the specific section gives me this:
Code:
/*******************************************************************
  Process a send backup list request packet.

  A client sends a backup list request to ask for a list of servers on
  the net that maintain server lists for a domain. A server is then
  chosen from this list to send NetServerEnum commands to to list
  available servers.

********************************************************************/

Looks it has something to do with the "Force as Master Browser = Yes" option I always switch on.
(Stupidly hidden under "USB Application->Servers Center->Miscellaneous setting".)
 
Last edited:
Totally sure no tapping into. Netmask is a basic /24.
Nothing unusual on the Connections page, only valid IP's.

If this happens I also find a "DHCP-Thread" on the Real-time Traffic monitor.
No clue what this is. :confused:

I rebooted the router and keep a close eye on it to see what might trigger this.

This seems to happen when I login to my own network using OpenVPN.
If I check the router with my OpenVPN session I see one UDP connection is active per funny IP address. (See pic.)

More funny is this doesn't show up on the Connections page. :confused:
 

Attachments

  • During OpenVPN session.jpg
    During OpenVPN session.jpg
    65.3 KB · Views: 561
This seems to happen when I login to my own network using OpenVPN.
If I check the router with my OpenVPN session I see one UDP connection is active per funny IP address. (See pic.)

More funny is this doesn't show up on the Connections page. :confused:

Are you using a TAP interface? In that case, it's as if you had an Ethernet cable between both networks, so your router ends up seeing anything that's also on your side of the tunnel.
 
Are you using a TAP interface? In that case, it's as if you had an Ethernet cable between both networks, so your router ends up seeing anything that's also on your side of the tunnel.

TUN.

However my router is using IP address 10.0.0.254 /24
VPN subnet is 10.8.0.0 /24

Could that give a problem?
Maybe use /16 mask for the VPN?
 

Attachments

  • Settings.jpg
    Settings.jpg
    56.7 KB · Views: 493
TUN.

However my router is using IP address 10.0.0.254 /24
VPN subnet is 10.8.0.0 /24

Could that give a problem?
Maybe use /16 mask for the VPN?

No idea then.

You definitely want to use a /24 for your use.
 
374.35_4 was uploaded to Mediafire. This update mostly focuses on fixing some of the new VPN-related issues introduced with the feature merge of 374.35.
 
RMerlin, when do you expect to release the next system update with the new Broadcom drivers, if you even have an idea at all?

I'm considering upgrading the AC66U handling my network from 374.32 to 375.35_4, but I have a lot of people and devices to re-configure to get everything working on when I reset the wireless, so I don't want to do it more often than I have to ;)

I'm getting the occasional wireless drop where I have to power cycle the router but that does not happen very often.
 
374.35_4 was uploaded to Mediafire. This update mostly focuses on fixing some of the new VPN-related issues introduced with the feature merge of 374.35.

Hey Merlin,

Just downloaded this...is this the recommended fw for now? I had been following the Atium Bead thread but seems like it's past due now? Planning on updating tomorrow.

Thanks,

Mike
 
RMerlin, when do you expect to release the next system update with the new Broadcom drivers, if you even have an idea at all?

What new Broadcom driver? There hasn't been an RT-AC66U update for a few weeks now.
 
Hey Merlin,

Just downloaded this...is this the recommended fw for now? I had been following the Atium Bead thread but seems like it's past due now? Planning on updating tomorrow.

Thanks,

Mike

Atium Bead was mostly a preview release. 374.35_4 is what I recommend RT-AC68U users run.
 
Hi RMerlin,

I try to keep up with fw releases, so I went form 35_2 to 35_4 on my ac66u.
But I get this:
Code:
Jan  1 01:00:23 pppd[498]: Plugin rp-pppoe.so loaded.
Jan  1 01:00:23 pppd[498]: RP-PPPoE plugin version 3.11 compiled against pppd 2.4.5
Jan  1 01:00:23 pppd[499]: pppd 2.4.5 started by admin, uid 0
Jan  1 01:00:24 pppd[499]: PPP session is 11918 (0x2e8e)
Jan  1 01:00:24 pppd[499]: Connected to 00:1f:3f:5a:01:c1 via interface eth0
Jan  1 01:00:24 pppd[499]: Using interface ppp0
Jan  1 01:00:24 pppd[499]: Connect: ppp0 <--> eth0
Jan  1 01:00:25 pppd[499]: Remote message: duplicate address detected
Jan  1 01:00:25 pppd[499]: PAP authentication failed
Jan  1 01:00:31 pppd[499]: Connection terminated.
Jan  1 01:00:31 pppd[499]: Sent PADT
Jan  1 01:00:31 pppd[499]: Modem hangup
No internet after that, manual reboot by pulling power, no internet, even after 5 mins....
I clear my port forwards, reboot, and online after 66sec... why?
 
Hi RMerlin,

I try to keep up with fw releases, so I went form 35_2 to 35_4 on my ac66u.
But I get this:
Code:
Jan  1 01:00:25 pppd[499]: Remote message: duplicate address detected
No internet after that, manual reboot by pulling power, no internet, even after 5 mins....
I clear my port forwards, reboot, and online after 66sec... why?

That line indicates that you have an IP conflict.
 
No idea then.

You definitely want to use a /24 for your use.

I changed to 192.168.0.0 /24 for the VPN Subnet / Netmask.
This works just fine. (You get routed to the 10.0.0.0 network so no problem.)

However I still see all those funny Host IP addresses on the Traffic Monitor->Per device->Real-time tab.

Something is wrong in this department if you ask me.
 
That line indicates that you have an IP conflict.
Sorry, I don't understand it, I thought the pppoe connection setup was without ip addresses, but soly mac based? wiki
I will try again with "clone mac address" maybe it makes a difference.

Found it: "Enable VPN + DHCP Connection Yes/No" For some reason it was set to yes
Flashed back 35_2 and set to NO, then flashed to 35_4, no more occurence (-;
 
Last edited:

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top