New ISP activated
Yesterday, even before the estimated time, the engineer came long to install the new Fiber modem and the new router. No IPTV yet, nor VoIP, although the connections are present: it seems there is some administration to attend first, but the new ISP has promised to work on it as fast as possible, since we’re unreachable by phone for over a month now….Worst case it could take another 2-3 weeks…
Next was the challenge to have DNS updated as soon as possible, so a mail was sent after a phone call, but it was impossible to handle the request that night. But it would certainly be the next working day – that is: today. Indeed, it looks that between 15:00 and 15:30 (local time) the domain registrations were updated.
Outgoing internet was (mostly) working. But incoming wasn’t because of the DNS issue.
But that alone doesn’t mean all is well…
The new router (Fritz!Box 3790) is not connected to be a router: all connections are on the LAN-switch, even the incoming from the modem. No real problem since the router uses VLAN tagging, and the different VLANs are bridged to different ports; it seems that the one carrying the incoming signal is passing the firewall to connect to the port routing into the LAN – presumably all traffic would pass to the Vigor router that is taking care of the boundary for years. In this respect, it would need to get another (fixed, of dynamic) address on the WAN port, and it would need to route all traffic over the new router.
However, that didn’t work as expected. Although I saw packages coming in, they were addresses to the internal address if the new router, and passing the answer back failed altogether, the default route being defined properly the software. The answer would be to bypass the Fritz!box – setting the VLAN up as a bridge, which has been done before (by a script) but that was not at all recommended.
This morning the first attempt was to use the Vigor 2910 insetad, but that fails to connect, because it doesn’t support IPV6 and VLAN tagging, as does its successor (Vigor 2920) or its smaller brother 2310 – though it looks that misses the highly validated security facilities. And because of the difference in price is not that big, I’ll purchase the first.
But to be able to be accessed in the mean time, I copied the port forwarding specification into the Fritz!Box; it didn’t help first since there was a route left over from earlier attempts…Once that was taken off, it all seems to work now.
That is: until a message sent from one of the PC’s was rejected due to denied access. Duh. The SMTP configuration still mentioned the SMTP-server from the previous ISP as alternate gateway. After I changed that, mail also worked. Now it is a matter of waiting for the DNS update has passed over the Internet so mails in transit will be delivered – on the right spot.