Equipment Support > Hardware By Brand > ZyXEL > Zywall fw 4.01 out

reply to kruser

Re: Zywall fw 4.01 out

Most likely not. The PPPoE code is completely different from the firewall code that is dropping traceroute on LAN interface.

reply to Anav
I've experiencing the tracert problem but my PPoE connection is rock solid.

reply to old_gear
Hi,

I've noticed this post about the Z5 4.01 fw problems.

I have the same problems in Belgium (Belgacom/Skynet) like Stefaan when 4.01 firmware is installed. I'm using a SpeedTouch modem in bridge setup, so my configuration is very close to Stefaan's setup. I reverted back to 4.00 after i noticed the DNS/ping problems. Getting IP address was indeed no problem.

So, Stefaan what are the actual results/fixes today? Is it still only a drop/add of the default route or have u also reverted back to 4.00 ???

THX in advance,
Erwin

reply to old_gear
OK, thank you. I will go for the same approach and maybe a next release will address this issue.

Regards,
Erwin

reply to old_gear
Here are the results from my (new) Z5 adventure.

When I uploaded (again) the new 4.01(XD.0) firmware my Z5 made a good connection to the ISP’s central. DNS information was found quickly after the wan IP address and I was able to game and surf without any problem. A quick look with telnet gave this result:

Dest FF Len Device Gateway Metric stat Timer Use
default 00 0 poe0 ChangeMe 1 00ab 0 7

I remember that on previous 4.00 > 4.01 changes, the first attempt was always OK. I call this clue 1.

Then overnight no activity on the internet was performed and I found my Z5 in the morning searching for DNS info and getting new wan IP addresses every few seconds, the same problem was back. (Kruser called it ‘fall asleep’ after no internet traffic in he’s first post)

Telnet results:

ras> ip route stat
Dest FF Len Device Gateway Metric stat Timer Use
87.66.77.1 00 32 poe0 87.66.77.1 1 03a9 0 5700
192.168.1.0 00 24 enet0 192.168.1.1 1 041b 0 130904
default 00 0 idle ChangeMe 101 002b 0 0
ras>

Notice the Device = idle and Metric = 101 for default route.
When I used the drop/add (used 1 when adding) method I got the same results, ‘idle’ and ‘101’.

Last week I called a technician from the ISP support team and he told me that he noticed when I disconnected my Z5 (or dropped the IP) that my account was still logged in, longer then he expected. But this latter is open for debate, how long is this account info hold at the ISP’s central and what is to long? On the other hand, this is normal behaviour. It always takes some time before a real account drop is acknowledged at the ISP’s site. Nevertheless I call this clue 2.

Combining clue one and two, I decided (deliberately) to change my account info in the WAN settings to a false account name. Adding one figure is enough to do the trick. This is forcing a (faster) drop of the actual account’s info at the ISP’s site. Immediate I changed it back to the correct account info and again I pushed the Apply-button. And guess what happened?

Yes, I got a new IP address and the system found the ISP’s DNS info real fast, surfing and gaming was OK from that moment.

Telnet results:

ras> ip route stat
Dest FF Len Device Gateway Metric stat Timer Use
87.66.195.1 00 32 poe0 87.66.195.1 1 03a9 0 7
192.168.1.0 00 24 enet0 192.168.1.1 1 041b 0 132733
default 00 0 poe0 ChangeMe 1 00ab 0 7
ras>

Here we see that the Metric is OK as soon as the Device is back on poe0. No manual Metric change was needed.

(This is a slightly other behaviour then we can see in post 5 of StefaanE, where he's Device stays on poe0, but the Metric is wrong)

Conclusion:

IMHO the 4.01(XD.0) FW is far to sensitive (read buggy) in the way he’s handling this zero traffic period and specific in the way he’s trying to recover from this scenario. The failing test to recover with the same account info and the positive recover after an account’s info-change speaks for it. I reverted back to 4.00(XD.8) and will wait for a next 4.01(XD.1) update.

Erwin

sniper__e,

My "fall asleep" problem has been confirmed by Zyxel to be an ARP problem.

I can't test for your poe problem as I'm on a static connection and no poe involved.

As far as the first pings to the Z5's LAN interface timing out after a 5 minute no activity period, Zyxel says this fix will be included in the next release.
This ping timeout fix also fixes the ARP problem (actually, the ARP fix fixes the first ping timeout ).
I'm hoping they will also include a few other fixes such as a fix for the tracert bug that has been reported by other several times.

euhhhh, we are back to 4.00 ???

Zyxell released a new 4.00(XD.11)C0 for Z5.
Will download it and see what this is all about ...

Erwin

what did it say in the release notes??

reply to sniper__e
Where did you get 11 from? I only see 10 in the FTP site?

~CMT
--
There's no place like 127.0.0.1

Look here ...

»www.zyxel.com/web/download_us.ph···11C0.zip

It seems that the 4.01 is to buggy and they reverted back to the latest release in the 4.00 series. I think this one never got published before ... (therefore the special download place?)

ZyNOS Version: V4.00(XD.11) | 08/14/2006 14:05:05
Bootbase Version: V1.08 | 01/28/2005
Vantage Agent Version: 2.1.3(XD.0)

I just got it installed, indeed it looks like the rest of the 4.00 family

Erwin

No they always update the last version bout 2-3 times, so that peple that dont like bleeding edge can feel safe and get big fixes
--
"Perl is executable line noise, Python is executable pseudo-code."

reply to stefaanE
I have got a big problem about Z35 4.01. My Z35 appears the "101 Metric" problem yesterday, if I reboot the Z35, the PPPoE connection is OK, the default route is "1 Metric". But after 2 minutes, the default route will auto change to "101 Metric" and can't route to the Internet, but the Z35 got an IP address all right.

Then I proceeded to fix the route manually, it's work but only 30 seconds, the Z35 will auto change from "1 Metric" to "101 Metric" itself, so I can't route to Internet again.

So I go back to v4.00(WZ.10) and use the 20 second reset button trick to get the Z35 to stop rebooting over and over again after I went back to 4.00(WZ.10), I also reset to factory defaults, but also has the same problem, the default route auto change to "101 Metric" and can't route to the Internet, what can I do?

Exact the same problem i had with Z5, 4.01 and PPPoE. It's one of the bugs in this new 4.01 FW.

If you go back to the 4.00 series and do everything by the book (also restore a previous backup) then this problem should be gone!

BTW there's a 4.00(WZ.11)C0 for your Z35, you should go for that. Get it here ...

»www.zyxel.com/web/download_us.ph···11c0.zip

Erwin

reply to idolclub

So you reverted back to FW 4.00(xx.xx) and your last know good backup.

If the RIP suggestion from Stefaan does not help you then something else is going on here.

Are you sure your ADSL modem gets its synchronisation over the line? To test, unplug the power from this modem for 3 minutes and see what happens when you start it up again ...

If artifacts are possible on a Zywall (? never seen that before) then perhaps try to load this new 4.00(WZ.11)C0 for your Z35. If nothing else is working then you can't lose anything by trying this one ...

PS Why 3 min? Then i also know that your account information is dropped at the ISP's central.

Let us know the results,
Erwin

reply to old_gear

Management Page error