Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: GigabitEthernet on July 13, 2017, 02:29:51 PM
-
I've just received one of these. It is from "italk" and admin/1234 doesn't work for a login. I have already reset the router.
Would really appreciate any guidance.
-
I shall have to make the same request to you as I made to stevebrass (http://forum.kitz.co.uk/index.php/topic,19972.msg350526.html#msg350526), yesterday --
Will you please identify to which device you are referring -- a VMG1312-B10D or a VMG1312-B10A ?
-
Is is the B10A but not to worry as I have managed to rebrand it. I put it into "recovery mode" (it asks you to upload an image) and I uploaded the newest ZyXEL firmware. I was then able to login using admin/1234.
-
Well done. How do you get into recovery mode for future ref?
-
Ah, I see. All is good. :)
You might, however, find it worthwhile to clear the ROM-D as that is the location of ISPs/CPs customisations.
-
To get into "recovery mode" you need to hold down the reset button for around 30 seconds. First the power LED will flash, you need to keep it held down until it goes solid red. Then you can access recovery mode on LAN1 at 192.168.1.1. It will accept a bin file.
The next thing I need to figure out is why this router won't let me ping clients by their hostnames. My Raspberry Pi is called "raspberrypi" but pinging that results in an error. It is called "raspberrypi" on the VMG1312's admin pages so this is very odd indeed.
-
Many thanks for that info.
-
I've updated the "Subject:" line of this thread so that the device is now precisely named.
-
Nobody has any idea about the hostnames issue then?
Can somebody with this router try pinging a device by its hostname and see if it works?
-
As I own a VMG1312-B10D my results are not directly applicable to your situation.
However I ping'd & traceroute'd my RaspberryPi first by IPv4 address and both returned the expected result. I then tried to ping & traceroute by name and both failed.
-
Thank you for confirming. It seems as though the DNS server used by the ZyXEL devices only supports hostname resolution of the router itself and not any devices. What an odd thing to do.
-
My Zyxel 8324 does resolve by name of DNS hosts so perhaps only 1312 has problem. I know it works as I have to edit a router config save and reload it to get the hostnames I want as the GUI has stupid (aka wrong IMO) validation rules.
Can you confirm you get the same issue when using the pi to ping out to say a windows machine?
No access to router at moment but I can check my config if you think it will help you as it has not changed for years - do not remember doing any special other than what already mentioned though?
-
I have performed a series of experiments with my VMG1312-B10D.
Two targets were chosen: A WAN side site, Name "kitz.co.uk", IPv4 address 185.24.98.37 and LAN side device, Name "RaspberryPi", IPv4 address 192.168.1.4
Ping by IPv4 address: Both respond correctly.
Traceroute by IPv4 address: Both respond correctly. (Though it is a bit meaningless for the R-Pi. ;) )
Nslookup by IPv4 address: The string "Unknown Host or Unreachable Network!" is returned.
Ping by name: Correct response for the Kitz site, no response for the R-Pi.
Traceroute by name: Correct response for the Kitz site, no response for the R-Pi.
Nslookup by name: Correct response for the Kitz site, no response for the R-Pi.
-
I have just tried it on my VMG8324 and it also doesn't work.
-
Definitely works on my 8324 - very strange.
I can remote into any machine (Linux or windows) on network and it recognises any dns hostname I have added to the router. Only the router knows the names so it has to be the router resolving them.
-
Definitely works on my 8324 - very strange.
I can remote into any machine (Linux or windows) on network and it recognises any dns hostname I have added to the router. Only the router knows the names so it has to be the router resolving them.
DNS names you have added - manually?
-
The next thing I need to figure out is why this router won't let me ping clients by their hostnames. My Raspberry Pi is called "raspberrypi" but pinging that results in an error. It is called "raspberrypi" on the VMG1312's admin pages so this is very odd indeed.
I may have misunderstood and, thus, confused everyone with my experiment, above. :-[
In my tests, I was using the functions on the VMG1312-B10D device's Maintenance >> Diagnostic page page . . .
(b*cat goes in search of suitable brown paper bag. :paperbag: )
-
I may have misunderstood and, thus, confused everyone with my experiment, above. :-[
In my tests, I was using the functions on the VMG1312-B10D device's Maintenance >> Diagnostic page page . . .
(b*cat goes in search of suitable brown paper bag. :paperbag: )
If you open a terminal on a PC, can you ping a device by its hostname? I cannot.
-
How very strange, reset my VMG1312 to factory resets and cleared the ROM-D for good measure and pinging by hostname is now working.
-
If you open a terminal on a PC, can you ping a device by its hostname? I cannot.
Ah, let me see --
[Duo2 ~]$ ping -c 5 ap
PING AP (192.168.1.254) 56(84) bytes of data.
64 bytes from AP (192.168.1.254): icmp_seq=1 ttl=64 time=7.22 ms
64 bytes from AP (192.168.1.254): icmp_seq=2 ttl=64 time=5.35 ms
64 bytes from AP (192.168.1.254): icmp_seq=3 ttl=64 time=3.06 ms
64 bytes from AP (192.168.1.254): icmp_seq=4 ttl=64 time=6.38 ms
64 bytes from AP (192.168.1.254): icmp_seq=5 ttl=64 time=3.07 ms
--- AP ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4008ms
rtt min/avg/max/mdev = 3.067/5.022/7.227/1.699 ms
[Duo2 ~]$ ping -c 5 raspberrypi
PING RaspberryPi (192.168.1.4) 56(84) bytes of data.
64 bytes from RaspberryPi (192.168.1.4): icmp_seq=1 ttl=64 time=3.03 ms
64 bytes from RaspberryPi (192.168.1.4): icmp_seq=2 ttl=64 time=5.66 ms
64 bytes from RaspberryPi (192.168.1.4): icmp_seq=3 ttl=64 time=3.32 ms
64 bytes from RaspberryPi (192.168.1.4): icmp_seq=4 ttl=64 time=5.50 ms
64 bytes from RaspberryPi (192.168.1.4): icmp_seq=5 ttl=64 time=5.00 ms
--- RaspberryPi ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4012ms
rtt min/avg/max/mdev = 3.037/4.506/5.662/1.111 ms
[Duo2 ~]$
Yes, that works for me. :)