Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: Weaver on September 17, 2018, 06:58:58 PM
-
- I think that the magic runes are to set the admin IP from the CLI are eg:
lan config --ipaddr primary 192.168.4.1 255.255.255.0
What are ‘primary’ and ‘secondary’ ? Just two addresses that you can associate with the port and that’s all there is to it? - I notice there is a dhcpclient option too. Wow, so I could really make the modem controllable by an external DHCP server?
If I were to use that then I could get the Firebrick to configure the modems automatically and so no having to keep their addresses straight. - Would there then also be a configurable default IP address in the absence of a DHCP server?
- Could anyone else tell me if this is safe to at least try? (Given the grief I have had recovering a modem, though not always.) I didn’t dare try this in case I bricked it, but I would love to give it a go. I would have to work out how to do the Firebrick config first, with per-interface dhcp pools, for this to be any use.
- I tried the ‘dns’ command out too, could not get it to work, or maybe it doesn’t do what I hoped. I could not work out how to test it though. It appears to have taken effect, according to the lan show command’s output. I don’t think I could test it without getting a default route to the outside world going.
- I tried the route command but couldn’t get anywhere with it. I tried to work out how to route everything in the world to the Firebrick’s address on that link, 192.268.4.254 in the current case, where the modem is at 192.168.4.1, but error messages with everything I could think of. It really seemed to hate a netmask of 0.0.0.0, I think that was it, don’t know why.
-
This modem currently shows:
lan show
br0 Link encap:Ethernet HWaddr 04:BF:6D:3A:44:D0
inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0
inet6 addr: fe80::6bf:6dff:fe3a:44d0/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1508 Metric:1
RX packets:3271 errors:0 dropped:0 overruns:0 frame:0
TX packets:3095 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:213015 (208.0 KiB) TX bytes:813237 (794.1 KiB)
br0:0 Link encap:Ethernet HWaddr 04:BF:6D:3A:44:D0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1508 Metric:1
Group Name DNS Type
Default Static(DNS Server : 192.168.4.254,0.0.0.0)
-
Be very careful, I just tried issuing this:
lan config --dhcpclient enable
To which it responded:
sshd:error:921.139:rutNtwk_getActiveDns6Ip:697:no ipv6Obj->IPv6DNSWANConnection found
sshd:error:921.152:rutNtwk_getActiveDns6Ip:717:fail to get dns6 server
=========== Setting success please wait 5 sec ===========
Config saved to flash.
Rebooted and my VMG1312 is now stuck in a boot loop... Will have a look what its saying on the console and get back to you.
-
Be very careful, I just tried issuing this:
lan config --dhcpclient enable
To which it responded:
sshd:error:921.139:rutNtwk_getActiveDns6Ip:697:no ipv6Obj->IPv6DNSWANConnection found
sshd:error:921.152:rutNtwk_getActiveDns6Ip:717:fail to get dns6 server
=========== Setting success please wait 5 sec ===========
Config saved to flash.
Rebooted and my VMG1312 is now stuck in a boot loop... Will have a look what its saying on the console and get back to you.
Ooo errr, not good.
-
So the modem boots fine with no ethernet cables attached, but when you plug one in:
eth1 Link UP 100 mbps full duplex
ssk:error:91.569:rutNtwk_getActiveDns6Ip:697:no ipv6Obj->IPv6DNSWANConnection found
ssk:error:91.569:rutNtwk_getActiveDns6Ip:717:fail to get dns6 server
DHCP aquired LAN side IP address 192.168.x.x
smd:error:91.696:collectApp:1559:ssk (pid 260) exited due to uncaught signal number 11
smd:error:91.697:oal_processEvents:911:ssk has died. smd must exit now!
Need to reboot
umount: tmpfs busy - remounted read-only
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to
Requesting system reboot
Restarting system.
So it appears the zyxel management stuff gets upset with a DHCP acquired address.
-
I have no problems changing the default IP address using:
lan config --ipaddr primary 192.168.1.x 255.255.255.0
Are you hoping to use the "dns" and "route" commands to give the modem internet access?
-
Indeed.
Thanks for spotting that disaster! Good job I didn’t risk it.
They really do not believe in testing.