Speedport w504v firmware 1.10 www fleetcor comnbsp. 504v firmware speedport w502v speedport w504v firmware 1.10 probleme speedport w504v bedienungsanleitung download firmware update fr speedport w500v w504v update firmware speedport w701v speedport w701v firmware update birthday card maker. Hallo zusammen, habe ein Problem kann kein Firmwareupdate von Speedport W701 V bei der angegebenen Adresse aus dem Internet runterladen. (telekom.de/download) Da.

Some years ago I switched to using a Speedport W701V from on my ADSL line at home. I set it up in modem-mode and let a small Linux box handle everything else.

This setup had worked fine with other modems but shortly after switching to the Speedport I noticed that my local caching DNS server didn’t work correctly anymore. I didn’t really connect the dots at this point, though. That happened a few days later when I tried to use Apple’s Back to My Mac — it just didn’t work. After some network tracing I found out that the Apple machine sent DNS SOA requests but never got a reply back.

It turned out that all SOA request got blocked somewhere. Sending requests to my own name server ( host -t soa blackdown.de ns.blackdown.de) and tracing DNS there showed that no packet ever arrived. I put the Speedport back into router-mode at this point and, who would have guessed it, SOA requests worked fine again.

After fruitless discussions with Deutsche Telekom support (it was impossible to find anyone who even remotely understood what I was talking about) and sending a bug report to (the 701V actually is a FRITZ!Box) which never got an answer, I finally solved the problem by putting a firmware on the Speedport. This firmware had an option to disable the PPPoE-Filter.

After disabling the filter the device worked flawlessly in modem-mode. Now, a few days ago, I switched to VDSL and got a new router: a Speedport W920V. First thing I did was to put it into modem-mode.

And there it was again, the DNS SOA problem! The source code supports authentication with since version 4.43. Started enabling this feature in exim4_4.50-2.

After I’ve had upgraded to that version and replaced my saslauthd authenticators with brand-new cyrus_sasl authenticators, I’ve noticed that auth.log got flooded with entries like ‘ exim4: OTP unavailable because can't read/write key database /etc/opiekeys: No such file or directory. 100 Years War Ph Client Download here. ’ My exim configuration uses three different cyrus_sasl authenticators and each exim invocation resulted in three of these OTP warnings because exim calls sasl_listmech() for each configured authenticator. It doesn’t specify a limiting mech_list, that means SASL will test which of all installed mechs actually can be used for authentication. Debian’s SASL package includes libotp.so, so it also tries to use OTP which is not configured on my system.

There are two ways to get rid off the warnings: • Remove /usr/lib/sasl2/libotp.*. You’ll have to do this after each upgrade of the libsasl2-modules package. • Rebuild exim with this. The patch specifies a limiting mech_list option for SASL. This limits sasl_listmech() to the mechs used in the exim configuration. Other mechs won’t be tried anymore. May 3rd, 2005: A slightly modified version of the patch has been integrated into Exim CVS and will be included in the next Debian release of exim4 (see Debian bug ).

As my server only accepts public key based authentication, I’m not really worried about brute force password attacks. But these scans tend to clobber my auth.log. So after some discussion with, I’ve written a few custom actions for my setup.

They use the module which allows to track seen IP addresses and match against them using some criteria. The action can be used to limit accepted connections per IP and timeframe. The hardcoded limit currently is 6 connections per 60 seconds. If an IP tries to connect more often, the attempts will be DROPed. The action provides some simple port-knocking whitelist.

If you know the WHITELIST_PORT and can lift the limits imposed by the action for your IP and 60 seconds by connecting to that port. Here’s how you can integrate those two actions: • Create two empty files: • shorewall/action.Limit • shorewall/action.Whitelist • Copy and to the shorewall directory • Add Limit and Whitelist to shorewall/actions • Set WHITELIST_PORT in shorewall/params • Use Limit in shorewall/rules, for instance: Limit:ULOG:SSH net fw tcp ssh Limit:ULOG:IMAP net fw tcp imap,imaps Note: You must use the:: format for the rules. Uses the for the ipt_recent table name. • Optionally add a Whitelist rule: Whitelist:ULOG net fw If you’re running 3.9 or later, you additionally might want to set MaxAuthTries to 1 (see sshd_config(5)). May 9th, 2005: I have found a bug in the ipt_recent module, see for more information and a fix.