Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: Weaver on August 07, 2018, 06:45:30 AM
-
I cannot for the life of me see any mention of 192.168.1.1 in the XML config of my modem-router. Am I going mad? Sanity check please. Where is it storing this value ?
-
From my 8324 with an ip of 192.168.1.8 the nearby tags are:
<LANHostConfigManagement>
<IPInterfaceNumberOfEntries>3</IPInterfaceNumberOfEntries>
<IPInterface instance="1">
<Enable>TRUE</Enable>
<IPInterfaceIPAddress>192.168.1.8</IPInterfaceIPAddress>
<X_5067F0_IfName>br0</X_5067F0_IfName>
</IPInterface>
-
I grep-ed for "192.168." and nothing relevant apart from the .254 which is the Firebrick, the last machine that talked to the modem.
What I have for the corresponding element is:
<LANHostConfigManagement>
<LanDnsType>From_ISP</LanDnsType>
<DHCPLeaseTime>3600</DHCPLeaseTime>
<IPInterfaceNumberOfEntries>3</IPInterfaceNumberOfEntries>
<IPInterface instance="1">
<Enable>TRUE</Enable>
<X_404A03_IfName>br0</X_404A03_IfName>
</IPInterface>
<IPInterface instance="2">
<IPInterfaceIPAddress>0.0.0.0</IPInterfaceIPAddress>
<IPInterfaceSubnetMask>0.0.0.0</IPInterfaceSubnetMask>
<X_404A03_IfName>br0:0</X_404A03_IfName>
</IPInterface>
<IPInterface instance="3">
<IPInterfaceIPAddress>0.0.0.0</IPInterfaceIPAddress>
<IPInterfaceSubnetMask>0.0.0.0</IPInterfaceSubnetMask>
<X_404A03_IfName>br0:1</X_404A03_IfName>
</IPInterface>
<IPInterface nextInstance="4"></IPInterface>
</LANHostConfigManagement>
Madness?
-
No madness on your part, but some from the Zyxel devs!
Just tried on mine, setting the Default groups IP back to 192.168.1.1 removes its presence from the XML config completely...
I guess its another of those wonderful hardcoded in a binary choices they seem to enjoy in their firmware dev team. ::)
-
That is indeed it, compared it with a 'modem 2' 192.168.2.1, and there it was. So that was a bug in the tool I wrote to adapt xml files and customise them to be modem-n. The tool was sometimes taking a template file that had a no reference to 192.168.1.1, and so was not doing the right thing because it searched for that and altered it, but did nothing if it was not found - which was no good at all.
-
I modified the iPad tool that I wrote so that it will spot the missing 192.168.1.1 and insert the correct thing in its place, so that sanity is restored and now it can take any config file, even a modem #1 variety lacking the address insertion point marker, and it generates a derived customised version with the right IP address for link #n correctly now.