17-Oct-2014

Router on tilt?
It was about 10 o’clock – in the evening – when searching data on the intenet on both my mobile phone and a tablet, that all of a sudden the connections dropped for no appearent reason; my Andoid phone complained that the wiFi connection was unstable. A slow down normally means there is an attempt running to break into some service at my site, but that would not cause the Wifi to beconme unstable, just that traffic slows down tremendously and that sites cannot be found because name resolution slows down too much. So there was something else going on.
Going up to theatic it became immediately clear that indeed there was something going on: every two seconds a beep of the Alpha system signalled a mail coming in – from the SYSLOG daemon, triggered by the router.
It turned out that a number of name servers tried to access the router (given the address) in a stream of UDP-messages that caused the router (by its configuration) to block them as being DoS attacks, similar to
Charon2: [DOS][Block][udp_RP_flood, timeout=10] [(address:53 -> )82.161.236.244:port][UDP][HLen=(Headerlength), TLen=(Transport-length)]
.
Given the originating port (53) marks the requests were sent by a name server (port 53 is the default port for DNS), I checked the addresses, and all were, indeed, name srvices: From my ISP, a few others, and Google. The way to get this stopped was shutting down the WAN interface (the ‘dirty side’ of the router); closing port 53 would be useless, since the router blocked the access: the requests didn’t make it into the LAN. After re-enabling the port all was back to normal.
Since SYSLOGD has been set up to log this type of request not just the the logfile but to OPCOM as well, it’s an easy trip to track it all down. And I found that the whole sequence started by a flood of UDP packets – twice – from a secured port:
%%%%%%%%%%% OPCOM 17-OCT-2014 19:49:23.80 %%%%%%%%%%%
Message from user SYSTEM on DIANA
Message from syslogd@charon.intra.grootersnet.nl at Oct 17 19:49:23 ...
Charon2: [DOS][Block][udp_RP_flood, timeout=10][82.94.234.15:443->82.161.236.244:39146][UDP][HLen=20, TLen=65]

%%%%%%%%%%% OPCOM 17-OCT-2014 19:49:25.33 %%%%%%%%%%%
Message from user SYSTEM on DIANA
Message from syslogd@charon.intra.grootersnet.nl at Oct 17 19:49:24 ...
Charon2: [DOS][Block][udp_RP_flood, timeout=10][82.94.234.15:443->82.161.236.244:39146][UDP][HLen=20, TLen=1378]

This address is the Google cache at my ISP….
The very next moment comes a mail message, and from that moment on, the trouble starts and name services start firing their request. In the beginning, the Google Cache service hops in a few times but that doesn’t show up later on; as well as incoming mail messages (but operator.log doesn’t show the originating address – I’ll have to dig the PMAS or SYSLOGD logs for them). Then it stops after I disabled the WAN interface, about 30 minutes after it all started.
The log shows that the router spewed out a message every 2 seconds, but the instability started when the number op available channels droipped too far so new connections could not be established.
This may have caused the instability of the Wifi connection – as signalled by my phone. But as it turned out, it was not the interface that was unstable, but a far too budy router….
This is one of those cases that is hard – if not impossible – to reproduce, but even so, I’ll mention it to the manufacturer.

16-Oct-2013

Vigor trouble – again
This morning, I remotely added another IP-object – a complete set of networks – because from these, there is a constant flow of break-in attempts from China as if this were a Linux or Windows machine that is badly configured. I rebooted the router afterwards to get rid of some weird data (Dial-out triggerdata: from 192.160.0.2 to 8.8.8.8 ???) like I have done before without any trouble. Except for this morning: the router did no longer respond.
So when I got home, I tried to connect directly over Wifi, but I could not connect. So I restarted it once again, it does restart, connection is possible, all works – for a minute of so, when the router freezes.
There surely is something wrong. Last week, and earlier there have been a number of interruptions in telephone – connections that broke within a minute, or no connection at all when phoning in….Not constantly, but at times, making it hard, even impossible, to locate the problem.
Anyway, I had to remove the Vigor and re-install the inappropriate Fritzbox, to have Internet access, TV and phone again…

02-May-2013

Replacement has arrived
It seems the Vigor router was broken beyond repair. Not really a surprise knowing that it is impossible to repair anything that is soldered on a board by robots….The problem was not software, that’s for sure.
Today I received a box that contained the whole lot: router, antennas, power unit, cables and docs.
Next step is to reload the saved configuration, and re-install it.And find out what can be improved in the installation.

04-Apr-2013

Indeed: broken
I just received confirmation of the supplier that the Vigor router is indeed broken ‘beyond repair’. This type is no longer available in the normal channels, so they will contact Draytek for repair or a replacement. It may take some time… Luckily, I already contacted Draytek on the issue, perhaps I can speed things up….

But the downside is that if I receive a replacement, I might have to redo the configuration from scratch. Since the backup of Draytek is both binary and encrypted, I cannot read these files unless there is software to read these filoes. There is some on the internet, but it also contains the warning that not all information can be read – because the file is binary…Another question to Draytek!

30-Mar-2013

Router replaced
The update supplied by Draytek didn’t solve the problems: After 6 minutes or so after login on the admin GUI, connection is lost. So I had to replace the Draytek with the Fritzbox supplied by the ISP, in order to ship the Draytek to the supplier to have it checked and fixed; there is no alternative as to work with equipment that does not fit my requirements. No real problem as long as it works – and the situation is expected to be temporary.