Correct. No need to connect to modem's user interface.
(Other than to confirm the double NAT theory.)
If the static IP values are setup just like the DHCP values...
...and static works, but DHCP fails
...then I cannot wrap my head around that one.
Maybe the OP can return/exchange the router.
Thanks for taking the time to help me think/learn about this.
It is a new router, he will be taking it to the shop.
One thing I couldn't change in router DHCP settings was domain name. I never had such an option in my previous routers so I am not sure what this would be. My guess is it is a just a descriptive informational setting.
Default value was: domain.name and when the textbox was cleared, it wouldn't save with an error of Invalid characters!
Do you know anything about this setting? The only webpage I found this setting on lists this setting as "Optional".
Also want to add, factory reset was already performed by OP.
should I marked this as solved? anyway big thanks for Mr.GoKay for sharing his time fixing this problem. still he manage to find a soulution to this. now my wireless devices can connect to internet.
Hey, it would be better to wait until you change that router (at shop) and actually get Internet access with dynamic IP. What we did was just a workaround.
Alright sir gokay, if not tomorrow then I'll go on thursday to return the router into the shop. thank you
anyway, should I get a same unit? or a different one.
These cheap routers are pretty much the same deal, I have Linksys WR110 (also a cheap router) which has the same features and nothing more. If it works same is ok, if not get some other model.
Okay sir, I will inform you asap when I get a new one! :) anyway the router cost only around 13.80 euro. it's really cheap
The router's field for "domain.name" is explained here:
https://tools.ietf.org/html/rfc6762
Some networking equipment's user interface label this field as optional. Some let you leave the field blank. (Some might not offer the field at all.) But all networking equipment handling DHCP should assign ".local" as the domain if no other value is (or can be) entered into the local domain field.
There are plenty of reasons why you might want to use local domain names. Here is one such reason: How (and Why) to Assign the .local Domain to Your Raspberry Pi
Hmm, my router/modem doesn't have such a field for domain name, but I made a little test:
- pinging <computername>.local did return a response whilst a random .domain_name could not find the host, so router DHCP sets the .local configuration.
I believe I used to know all this stuff (MCSE 2000, it has been 10-12 years) but forgot almost all about them
I also tried ping <computername> and that also resulted in a response. I wonder if .local dns suffix(?) is added automatically from somewhere, or it was possible because it was in the same network segment.
Thanks for the info!
When testing name resolution scenarios, it is probably best to disable the service named DNS Client (dnscache). That said, your description of Ping's performance is as expected. A total guess on my part would be that Ping asked the OS on your computer to find the computer that you wanted to ping. The OS on your computer followed the settings for the network adapter in use at the time.
Hopefully, we are not boring the OP while we await a new router
Quote
