Broadband Related > Broadband Hardware
Bricked (semi) ZyXEL VMG 1312-B10A
johnson:
It does seems like this may be the culprit.
For some reason Weavers base config, a slightly modified one from AAISP, has the default interface group missing LAN4.
For reference heres mine:
Notice LAN1 is missing from the Default group as its assigned to the VDSL connection, in Weavers the Default list is missing LAN4, but with no second group owning it.
Maybe this is due to a previous other interface group that has since been removed? Not sure.
LAN4 is also non functional when attempting to access the recovery page after booting into recovery mode. With a serial console attached plugging in a cable to LAN4 results in messages saying the port has been disabled.
This would seem to explain both the loss of connectivity to the normal web interface and the problems accessing the recovery page. But as Weaver says, still just a theory, I guess a test with one of the currently functional modems changing the cable to LAN4 would be a good way to prove or disprove.
Edit: In case its useful as the labels are tiny and virtually impossible to see if you have the unit wall mounted, LAN4 is the furthest from power in and closest to the phone cable in.
Weaver:
Guys, should we try and fix this?
banger:
Mine appears to have the LAN group including all LAN sockets, maybe an AA foible?
j0hn:
--- Quote from: Weaver on August 07, 2018, 06:48:18 AM ---Guys, should we try and fix this?
--- End quote ---
Fix what?
--- Quote ---For some reason Weavers base config, a slightly modified one from AAISP, has the default interface group missing LAN4.
--- End quote ---
Just don't use any AA settings. You have modified firmware and won't be relying on AA for updating your modem.
Most people make an effort to remove any ISP config from their Zyxel modem. As you bought these retail I have no idea how you have for AA settings in amongst your config.
Weaver:
I should have looked at the standard default config that the brand new ones come with, for inspiration.
Rationale: not entirely rational. [Remember I am completely full of drugs. ??? ]
I bought one from AA ages ago when they still had some stock and that was really cheap. I specifically wanted to use the AA config, although with Burakkucat’s help I did disable the TR-069 remote updating, because as you said, I have custom firmware.
AA staff did the donkey work so that it just worked immediately out of the box in modem-only mode as I asked, as they set up the basic ADSL settings.
I also have a slightly tuned config in other respects: (1i) going on a tip from Burakkucat, I have locked it to G.992.3 only, disabling auto-mode because I do not want it to select G.992.5. This optimistic tweak is in hope of slightly higher performance by reducing the input frequency range window and so reducing the total noise ingested. That is the idea, but it does not seem to deliver any improvements from the evidence of experiments. Since it doesn't hurt, I have kept it in though. (2) I also have slightly reduced overhead by changing from RFC2684 LLC to the more efficient VC-MUX, which I can safely do because I am not on 20CN whereas AA would have to do two configurations.
I hoped I could get internet access to the modem going, behind my usual firewalling, but have not got that far. I wanted to get NTP to work and DNS and also ideally I wanted to make it really easy for AA staff to directly log in and have a peep at stats without me having to dig them out and send them to AA, cutting out the round trip. For that reason I wanted some other AA customisations such as correct IP addresses set for AA's NTP server, DNS servers etc.
Navigation
[0] Message Index
[*] Previous page
Go to full version