Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 56 57 [58]

Author Topic: ZyXEL VMG8324-B10A Firmware  (Read 272340 times)

broadstairs

  • Kitizen
  • ****
  • Posts: 3090
Re: ZyXEL VMG8324-B10A Firmware
« Reply #855 on: June 24, 2018, 07:43:16 AM »

New firmware (24!)

ftp://ftp2.zyxel.com/VMG8924-B10A/firmware/

When I go to that link V21 is the latest shown. However VMG8324-B10A page does show it.

Stuart
Logged
ISP:TalkTalk Connection:FTTC Cab:ECI Router:Netgear D6220

RTouris

  • Just arrived
  • *
  • Posts: 6
Re: ZyXEL VMG8324-B10A Firmware
« Reply #856 on: June 24, 2018, 01:02:03 PM »

firmware changelog grid attached below
Logged

RTouris

  • Just arrived
  • *
  • Posts: 6
Re: ZyXEL VMG8324-B10A Firmware
« Reply #857 on: June 24, 2018, 11:56:40 PM »

Flashing the latest v.20 firmware, with an Eircom header, in effect unlocks the F1000. When the v.21 firmware is released, the F1000 should accept it. No need to open the router and do the unlock procedure.

Could someone comment on this? Given that now both v.21/24 are out for the 8324 did anyone have success flashing the generic Zyxel firmware to a previously-flashed-with-a-modified-header-f/w-v20 Eircom unit?
Logged

RTouris

  • Just arrived
  • *
  • Posts: 6
Re: ZyXEL VMG8324-B10A Firmware
« Reply #858 on: August 10, 2018, 10:30:35 PM »

Flashing the latest v.20 firmware, with an Eircom header, in effect unlocks the F1000. When the v.21 firmware is released, the F1000 should accept it. No need to open the router and do the unlock procedure.

Just a quick follow-up on my previous (last) message. Having flashed an Eircom F1000 with the modified v.20 f/w, this procedure does NOT effectively unlock the unit as it doesn't subsequently allow generic ZyXEL f/w to be flashed. It definitely is a solid solution, so long as you stay with the latest "Eircom-header"-based v.20 one, which apparently appears to be the most up-to-date available from user dmcdonnell, however new ones have yet to be available in order be on-par with the current one (v.24).
Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6063
  • Retd sw dev; A&A; 4 7km ADSL2; IPv6; Firebrick
Re: ZyXEL VMG8324-B10A Firmware
« Reply #859 on: August 11, 2018, 02:50:12 AM »

@RTouris and welcome to the forum !
Logged

RTouris

  • Just arrived
  • *
  • Posts: 6
Re: ZyXEL VMG8324-B10A Firmware
« Reply #860 on: August 11, 2018, 08:41:21 AM »

@RTouris and welcome to the forum !

Thank you for having me ;)
Logged

dmcdonnell

  • Member
  • **
  • Posts: 91
Re: ZyXEL VMG8324-B10A Firmware
« Reply #861 on: August 15, 2018, 11:47:17 AM »

You can download the v.24 firmware, modified to have an Eircom header, here:

https://drive.google.com/file/d/1PfQGZwEpUdwT04QIsbMpZx8gfQLo3kdc/view?usp=sharing
Logged

Iam_TJ

  • Member
  • **
  • Posts: 89
8924 - Wired port ARP neighbour discovery failure
« Reply #862 on: September 05, 2018, 11:13:56 AM »

I wonder if others could give me some feedback on whether an issue I've recently encountered affects other devices and/or firmware versions or is unique to this unit?

VMG8924-B10A with (currently) V1.00(AAKL.19)C0 in regular routed mode.

I have several devices directly connected to its wired LAN ports. A couple of days ago I found that these devices cannot connect to each other because they cannot discover each other through IPv4 ARP or IPv6 neighbour discovery! The ports are part of the LAN bridge (br0).

What is strange is this only affects wired-to-wired device discovery; discovery and connection from WiFi devices (also on br0 via wl0) works fine (and visa-versa).

Despite extensive diagnosis I've not identified a cause or solution. I'm currently suspecting the Broadcom hardware switch block itself.

More detail:

Using tcpdump on the various devices, and the router itself, I can see ARP who-has (and IPv6 neigh-discover) packets going out on the target device's wired port (e.g. eth0.0), and on the target device I see them received and the ARP/neigh-advert responses sent back. Those replies do not show up on the router (on the source (eth0.0) or target (eth1.0) ports, nor br0) and the target device does not see them either.

As I said, this was working a few days ago.

I discovered this because the target device is running the squid-deb-proxy Debian/Ubuntu package caching server which it advertises via multicast-DNS.

The wired clients can receive the multicast-DNS packets, including from each other, but the connection attempt to the deb-squid-proxy was faiing due to neighbour discovery failing.
Logged

zedman

  • Just arrived
  • *
  • Posts: 2
Re: ZyXEL VMG8324-B10A Firmware
« Reply #863 on: September 05, 2018, 03:22:02 PM »

The ftp site for the Vmg8924-B10A goes up to firmware 1.00(AAKL.21)C0.zip but the ftp for the Vmg8324-B10A goes up to firmware 1.00(AAKL.24)C0.zip. So  I contacted Zyxel support and the reply states that v.24 can be used on the 8924.

Quote from Zyxel: "yes, you can use the same Firmware for both devices.
ftp://ftp.zyxel.com/VMG8324-B10A/firmware/VMG8324-B10A_1.00(AAKL.24)C0.zip"
Logged

machare

  • Member
  • **
  • Posts: 44
Re: ZyXEL VMG8324-B10A Firmware
« Reply #864 on: September 05, 2018, 04:14:06 PM »

@zedman. Thank you for your post I have used your link to upgrage my VMG8924-B10A and it is still working though only acting as a switch and wifi access point.
Logged

Iam_TJ

  • Member
  • **
  • Posts: 89
Re: 8924 - Wired port ARP neighbour discovery failure
« Reply #865 on: September 08, 2018, 03:53:31 PM »

I wonder if others could give me some feedback on whether an issue I've recently encountered affects other devices and/or firmware versions or is unique to this unit?

VMG8924-B10A with (currently) V1.00(AAKL.19)C0 in regular routed mode.

I have several devices directly connected to its wired LAN ports. A couple of days ago I found that these devices cannot connect to each other because they cannot discover each other through IPv4 ARP or IPv6 neighbour discovery! The ports are part of the LAN bridge (br0).

What is strange is this only affects wired-to-wired device discovery; discovery and connection from WiFi devices (also on br0 via wl0) works fine (and visa-versa).

Despite extensive diagnosis I've not identified a cause or solution. I'm currently suspecting the Broadcom hardware switch block itself.
I tried an upgrade to firmware v24 with no improvement. I've done more detailed testing and it appears the Broadcom Forward Assist Processor (FAP) has failed in some way although there is nothing in the kernel boot messages, or syslog, to indicate anything different compared to the same logs from other devices (I have 3 other identical (8324) devices).

Right now I'm not sure if there's anything can be done about the FAP - I've not even been able to find documentation on it to confirm it gets involved in ARP/neighbour-discovery.
Logged
Pages: 1 ... 56 57 [58]