Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 
yitz
2238 posts

Uber Geek
+1 received by user: 594


  #3277699 1-Sep-2024 11:59
Send private message

It's likely this original NC(1) model is already end of support, I doubt there will be a patch, very few online services will be affected by this as unpredictability of simple DNS responses returning A records larger than 512 bytes is well known and avoided.

 

I do find it interesting that when initially querying the affected Huawei router on the first attempt the response comes back with truncated bit set but then there is no follow up TCP query - at least not that I can see on Wireshark. Subsequent A queries to the router come back empty. If I query against other servers e.g. 8.8.8.8 then a TCP fallback is immediately sent. Is the payload of that initial response that badly munted as its unclear what's happening at the Windows operating system API level.




SamF

1598 posts

Uber Geek
+1 received by user: 252

Trusted

  #3277700 1-Sep-2024 12:12
Send private message

Sure, but this looks like a BusyBox bug, so it might be worth reporting it at that level.

 

 


CcMaN
87 posts

Master Geek
+1 received by user: 37


  #3278768 4-Sep-2024 11:39
Send private message

I had the strange issues until I turned off the internal DNS. I didn't really think much of it at the time, but you are right there does seem to be a bug with it and maybe that was it.



ratbag359
25 posts

Geek
+1 received by user: 3


  #3279592 6-Sep-2024 20:43
Send private message

I have NF18ACV-NC2-R6B024.EN doing your test it also fails.
I queried Router
backupstorage100.s3.wasabisys.com fails
backupstorage10.s3.wasabisys.com  returns results

I queried CloudFlare 1.1.1.1
I get results for both.

I queried slingshot 202.180.64.10 
I get results for both.

 

Seems to be a firmware issue or limitation.


ratbag359
25 posts

Geek
+1 received by user: 3


  #3279595 6-Sep-2024 20:53
Send private message

CcMaN: I had the strange issues until I turned off the internal DNS. I didn't really think much of it at the time, but you are right there does seem to be a bug with it and maybe that was it.

I too had issues so set dchp server to give out cloudfare and google dns.
Now I know why


ratbag359
25 posts

Geek
+1 received by user: 3


  #3279633 7-Sep-2024 09:02
Send private message

I have contacted NetComm it will be interesting to see what they say.


 
 
 
 

Shop now for Dyson appliances (affiliate link).
ratbag359
25 posts

Geek
+1 received by user: 3


  #3280803 10-Sep-2024 20:23
Send private message

From netcomm

 

"According to RFC 1035 DNS response is limited to UDP 512 bytes. NF18ACV currently do not support DNS response larger then 512 bytes."

 

 

 

I take that as we are going to stick with the standard.


SamF

1598 posts

Uber Geek
+1 received by user: 252

Trusted

  #3312669 25-Nov-2024 13:21
Send private message

Hey @ratbag359, sorry I missed your responses.

 

Thanks for the testing and for following up with NetComm!

 

Interesting that other routers / OSs seem to be able to handle this situation without a problem.  Does that mean that these are not strictly adhering to RFC 1035?


Behodar
11093 posts

Uber Geek
+1 received by user: 6070

Trusted
Lifetime subscriber

  #3312670 25-Nov-2024 13:30
Send private message

It sounds like other routers are following Postel's law, "be conservative in what you do, be liberal in what you accept from others".


1 | 2 
View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.