Archive for the ‘Internet’ Category
Posted by jpluimers on 2016/05/13
Buffalo WLAE-AG300N is one of those buggy DHCP clients… Even running firmware Ver.1.85 (R1.05/B1.00)), it gets the length of the DHCP host name wrong so adds a bogus NULL byte to that name.
@Buffalo: please fix this.
The DHCP client options are of structure Type/Length/Value so a client is supposed to set the length of the hostname to exactly the number of characters.
However there exist buggy clients that either send a length of 1 more and a \00 at the end of the name, or send a fixed length and pad it with \00 as necessary.
Source: DHCP server: Odd active hostname behaviour: some views have null character at the end, some don’t. – MikroTik RouterOS
Fromt a packet capture:
Read the rest of this entry »
Posted in Access Points, Buffalo, Hardware, Internet, MikroTik, Network-and-equipment, Power User, routers, WinBox | Leave a Comment »
Posted by jpluimers on 2016/05/06
In the absence of http://www.mikrotik.com/download/CHANGELOG_6 (somehow it’s unreachable where I live) here links that do work:
–jeroen
Posted in Internet, MikroTik, Power User, routers | Leave a Comment »
Posted by jpluimers on 2016/04/25
I remember this happening when I was almost starting the studies at University: the Netherlands getting their country code top-level domain in 1986: at first mostly universities and research institutions were getting their .nl domains.
Today 30 years ago .nl came into existence and the first research institution domain here was cwi.nl (the research institution for math and informatics) as it handled the registrations (for years Piet Beertema did that, even before he hooked CWI to NFSnet in 1988).
This was the era of uucp – way before the web – which handled a lot of the mail traffic, but not the only one as back-then my HLERUL5.bitnet email address wasn’t even tied to the .nl dmain back then: it ran over DECnet based Mail-11 software. So it took a few more years before I got a .nl email address that the university and one of the reasons I still use a jeroenp account on many systems, for instance a few more years later when I got jeroenp@dragons.nest.nl at home.
This was way after the first commercial companies got their .nl toplevel domains, for instance and.nl was registered very early on (and Jos Horsmeier was very active).
So: happy birthday .nl and a bit thank you for all the people involved in getting .nl into existence.
–jeroen
Source: .nl – Wikipedia, the free encyclopedia
Posted in History, Internet, Power User | Leave a Comment »
Posted by jpluimers on 2016/03/28
20150412 ping statistics from WiFi -> ADSL -> VPN -> fiber (where ADSL and fiber both are Fritz!Box machines having LAN-LAN VPN to each other):
PING 192.168.71.1 (192.168.71.1): 56 data bytes
64 bytes from 192.168.71.1: icmp_seq=0 ttl=63 time=19.190 ms
...64 bytes from 192.168.71.1: icmp_seq=1 ttl=63 time=18.905 ms
64 bytes from 192.168.71.1: icmp_seq=2 ttl=63 time=19.261 ms
64 bytes from 192.168.71.1: icmp_seq=3 ttl=63 time=19.982 ms
64 bytes from 192.168.71.1: icmp_seq=4 ttl=63 time=19.332 ms
64 bytes from 192.168.71.1: icmp_seq=5 ttl=63 time=26.800 ms
64 bytes from 192.168.71.1: icmp_seq=6 ttl=63 time=20.139 ms
64 bytes from 192.168.71.1: icmp_seq=7 ttl=63 time=19.498 ms
64 bytes from 192.168.71.1: icmp_seq=8 ttl=63 time=18.915 ms
64 bytes from 192.168.71.1: icmp_seq=9 ttl=63 time=19.200 ms
64 bytes from 192.168.71.1: icmp_seq=10 ttl=63 time=18.948 ms
64 bytes from 192.168.71.1: icmp_seq=11 ttl=63 time=19.524 ms
64 bytes from 192.168.71.1: icmp_seq=12 ttl=63 time=19.511 ms
64 bytes from 192.168.71.1: icmp_seq=13 ttl=63 time=20.417 ms
64 bytes from 192.168.71.1: icmp_seq=14 ttl=63 time=19.350 ms
64 bytes from 192.168.71.1: icmp_seq=15 ttl=63 time=18.690 ms
64 bytes from 192.168.71.1: icmp_seq=16 ttl=63 time=18.632 ms
64 bytes from 192.168.71.1: icmp_seq=17 ttl=63 time=18.912 ms
64 bytes from 192.168.71.1: icmp_seq=18 ttl=63 time=19.397 ms
64 bytes from 192.168.71.1: icmp_seq=19 ttl=63 time=19.257 ms
64 bytes from 192.168.71.1: icmp_seq=20 ttl=63 time=18.147 ms
64 bytes from 192.168.71.1: icmp_seq=21 ttl=63 time=18.601 ms
^C
--- 192.168.71.1 ping statistics ---
22 packets transmitted, 22 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.147/19.573/26.800/1.657 ms
same but LAN –> fiber -> VPN -> ADSL
Pinging 192.168.24.1 with 32 bytes of data:
Reply from 192.168.24.1: bytes=32 time=19ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Ping statistics for 192.168.24.1:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 19ms, Average = 17ms
–jeroen
Posted in ADSL, fiber, Fritz!, Fritz!Box, Internet, Network-and-equipment, Power User, routers, VPN | Leave a Comment »
Posted by jpluimers on 2016/03/18
Mikrotik have statistics and way more features. The most lacking or disturbing features on the TP-LINK (none of which are mentioned in their documentation):
- The documentation mentions you can enable Enable Bandwidth Based Balance Routing then select the WAN connections to combine but that doesn’t work at all, even if you follow the bandwidth steps carefully.
- Balanced Routing work when you perform these steps as mentioned at time point 457 in this video https://youtu.be/YDUfP8a5zNY
- Enable Application Optimized Routing
- Enable Bandwidth Based Balance Routing
- Virtual-Server table can only handle 32 incoming port redirects; you get the message “Cannot add more than 32 Virtual Server entries” like in the picture below.
- No IPv6 support
- No way to show any statistics as graphs.
- Every once in a while the web interface becomes really really slow which only a reboot can resolve.
- You cannot have one of the WAN connections have multiple IP addresses.
- Local DHCP clients are not added to the DNS proxy which means you cannot resolve them by name.
- TCP Sequence Prediction: Difficulty=0 (Trivial joke)
- You cannot configure how often to check WAN connections
On the other hand: when you do balanced routing indeed bundles all the WAN connections, configured Virtual Servers do work well and WAN specific routing settings to what they need to.
Source: Gigabit Load Balance Broadband Router TL-ER5120 – Welcome to TP-LINK
Verdict: fine for home use, not good for real multi-WAN use.
–jeroen
Read the rest of this entry »
Posted in Internet, Power User, routers | 1 Comment »
Posted by jpluimers on 2016/03/15
I’ve tried the below on a Fritz!Box 7490 configuration and it fails as well.
The case is that I’ve a VPN (see Getting Fritz!Box LAN-LAN VPN to work) between a Fritz!Box 7360 (having internal IP 192.168.24.1) and a Fritz!Box 7490 (having internal IP 192.168.71.1). This is how it looks from the Fritz!Box 7360 side:
| Name |
Address in the Internet |
local network |
remote network |
| 80.100.143.119 |
80.100.143.119 |
192.168.24.0/24 |
192.168.171.0/24 |
On the 192.168.171.0/24 side of things, the internal IP of the 80.100.143.119 router is 192.168.171.1. Inside the 192.168.171.0/24 network is is another router (192.168.171.22) having an internal 192.168.71.0/24 network.
Basically I want to tell the Fritz!Box 7360 (at IP 192.168.24.1) that there is an internal route to 192.168.71.0/24 via 192.168.171.22.
I found and read Accessing multiple IP networks behind a FRITZ!Box over VPN connection between two FRITZ!Boxes | FRITZ!Box 7360 | AVM International.
Based on it, I wanted to add this route on the 192.168.24.1:
Static IPv4 Route
| IPv4 network |
192.168.71.0 |
| Subnet mask |
255.255.255.0 |
| Gateway |
192.168.171.22 |
| Enabled |
X |
When you do that, you get this error message:
An error occurred.
Error description: The route is illegal.
Please enter your data again. If the error occurs again, please consult AVM Support.
How can I get this route to work?
–jeroen
Posted in Fritz!, Fritz!Box, Internet, Power User | 1 Comment »
Posted by jpluimers on 2016/02/25
Find out how good the YouTube experience is with your Internet Provider using the Google Video Quality Report.
Source: Google Video Quality Report
Kissimmee hotel internet: not so good (:
DOWNLOAD 0.81 Mbps
UPLOAD 2.91 Mbps
–jeroen
Read the rest of this entry »
Posted in Internet, Power User, SpeedTest | Leave a Comment »
Posted by jpluimers on 2016/02/05
Copy had some advantages and disadvantages. For instance, it was better handling long file names, character encodings in filenames and a lot easier to configure over a CNTLM proxy than DropBox, but unlike DropBox didn’t keep history of changes.
Alas no more copy.com as of 20160501: [WayBack] Barracuda Copy – Copy End-of-Life.
They suggest using [WayBack] Mover with OneDrive as target: [WayBack] Barracuda Copy – Moving Your Data from Copy
Note that Mover has many more connectors, including cloud storage ones (Box, Copy, Dropbox, Google Drive, OneDrive and Yandex.Disk are free):
[WayBack] Connectors • Mover: FTP, Dropbox, Box, GoogleDrive, Copy, Egnyte, Amazon S3, SharePoint, MySQL the list goes on!
For me it means it’s time to think about what kinds of cloud storage I want to use and how to share what data with others at which access level. As I’m already contemplating on how to use ZFS, I now have two storage concepts to think about.
–jeroen
Posted in Cloud, Cloud Apps, Cntlm, Copy.com, DropBox, Infrastructure, NTLM, Power User, SocialMedia, Windows, Windows-Http-Proxy | Leave a Comment »