We've just upgraded the firmware on our Vigor 2830 to version 3.3.7.1. We had some problems on the way.

232201 didn't work at all - no ADSL connection achieved (to Zen 8000 Lite which is normal, nothing special, ADSL).

2471201 worked OK but it seems to have needed a change to the firewall. We could not access our web server without adding a port 80 LAN to WAN rule. This was not necessary before - a port 80 WAN to LAN rule was all that was necessary.

On the first sign of trouble we would have downgraded immediately but there does not seem to be any firmware available for an earlier version.

We were suprised to see that Draytek UK want 77p per minute to talk to them.

Anyway, the NAT loopback that didn't seem to be working with the earlier firmware seems to be working now.

Yes, the firewall has been well and truely screwed up by this upgrade.

The problems with the firewall make me wonder if the Keep State is no longer working.

This evening our new 2830n decided to block access to every website from 2 of our PCs, allowing access for mine only. I have some firewall rules to restrict my teenager, but the firewall was blocking all categories including those not ticked in the web content filter. The only way I could get access was to disable the default data filter completely...disabling the rules that related to those 2 PCs made no difference. We had 3.3.7 232201 installed.

After reading your post I upgraded firmware to 2471201 and access is back as it should be (didn't need to add a port 80 rule to get access).

Is there any way to get hold of an earlier firmware version to downgrade? Did the previous version work...the router came with 3.3.7 so I have no experience of any previous?

Nige

The previous version worked OK, except NAT loopback didn't seem to work. (NAT loopback wasn't so important to us until recently.)

Our router stopped working again today. I got support from the UK distributor who checked the settings for me...I'd made a couple of mistakes as I'm not an expert at this by any stretch! The manual doesn't say anything about the time schedule not being able to span midnight so that was mistake #1, then I was trying to do 2 jobs with 1 filter rule which was mistake #2. Now they are corrected, and with the correct 3.3.7 single band firmware, all is working OK.