The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,829 other subscribers

Archive for the ‘Network-and-equipment’ Category

In some countries @archiveis redirect their domains using http-302 which can have trouble with multi-WAN

Posted by jpluimers on 2022/08/12

From [Wayback Archive.is blog — Why has the URL “archive-li” changed to…:

Why has the URL “archive-li” changed to “archive-ph”, and will this affect saved bookmarks at any time in the future?

Anonymous

This is temporary and only for some countries. All 7 domains work, so you do not need to change the bookmarks.

In The Netherlands all Archive Today domains redirect to archive.ph using a HTTP 302 redirect.

This caused trouble at my home location, but not at my brother, so I searched for local issues.

In the end, it was because I have dual WAN as network load balancing at home.

TL;DR

Modifying the routing table so traffic for 54.37.18.234 goes to WAN1 was my solution.

Finding the destination address

Read the rest of this entry »

Posted in .NET, Development, Hardware, Network-and-equipment, Power User, PowerShell, routers, Scripting, Software Development | Leave a Comment »

Fritzbox 7490 ISDN landline and internal ISDN S0 bus links

Posted by jpluimers on 2022/08/08

Edit 20260617: intenral -> internal in the post title

Somehow WordPress.com failed to post it on the scheduled date 20150331, not sure why.

Though ISDN has been phased out in The Netherlands as and almost phased out in Germany, you can still use end user Terminal Equipment on the internal S-bus.

Since scheduling the post for 2015, the same information as the original diagram below appeared in text form on Wikipedia and there it also adds TAE connector information: Fritz!Box: Belegung der kombinierten DSL-Telefon-Buchse – Wikipedia

Read the rest of this entry »

Posted in DECT, Fritz!, Fritz!Box, Hardware, ISDN, Network-and-equipment, Power User, PSTN, Telephony | Leave a Comment »

Fritz!box 7590 interface extremely slow : fritzbox

Posted by jpluimers on 2022/08/05

I tried the solution in [Wayback/Archive.is] Fritz!box 7590 interface extremely slow : fritzbox (remove the some 30-40 unused machines from the network overview), but it didn’t matter: since Fritz!OS 7.x, the Fritz!Box 7490 UI is just very very slow: each page takes 10+ seconds to load.

Hopefully I can get rid of these and move to pfSense based hardware eventually.

–jeroen

Posted in Fritz!, Fritz!Box, Hardware, Network-and-equipment, pfSense, Power User, routers | Leave a Comment »

Hardware MAC address formats (which I need for Wake-on-LAN.ps1)

Posted by jpluimers on 2022/07/06

Early june, I blogged about Wake-on-LAN from a Windows machine.

My plan was to adopt [Wayback/Archive.is] Wake.ps1 into Wake-on-LAN.ps1 (as naming is important).

One of the goals was to support multiple hardware MAC address formats, especially as Wake.ps1 had the below comment, but did support the AA-BB-CC-DD-EE-FF, though not the AA:BB:CC:DD:EE:FF hardware MAC address format:

<#
...
.NOTES
Make sure the MAC addresses supplied don't contain "-" or ".".
#>

A colon separated hardware MAC address would result in this error inside the call to the [Wayback/Archive.is] PhysicalAddress.Parse Method (System.Net.NetworkInformation) | Microsoft Docs:

Send-Packet : Exception calling "Parse" with "1" argument(s): "An invalid physical address was specified."

So I did some digging, starting inside the above mentioned blog post, and adding more:

  1. Wake.ps1 uses the [Wayback/Archive.is] Parse method in the [Wayback/Archive.is] PhysicalAddress.cs source code in C# .NET,  which contains code like this:
                //has dashes? 
                if (address.IndexOf('-') >= 0 ){ 
                    hasDashes = true;
                    buffer = new byte[(address.Length+1)/3]; 
                }
  2. The Perl script at [Wayback/Archive.is] wakeonlan/wakeonlan at master · jpoliv/wakeonlan that started my first blog post in this series which mentions:
    • xx:xx:xx:xx:xx:xx (canonical)
    • xx-xx-xx-xx-xx-xx (Windows)
    • xxxxxx-xxxxxx (Hewlett-Packard switches)
    • xxxxxxxxxxxx (Intel Landesk)

    I should rename the first one IEEE 802, as per this:

  3. The MAC address: Notational conventions – Wikipedia

    The standard (IEEE 802) format for printing EUI-48 addresses in human-friendly form is six groups of two hexadecimal digits, separated by hyphens (-) in transmission order (e.g. 01-23-45-67-89-AB). This form is also commonly used for EUI-64 (e.g. 01-23-45-67-89-AB-CD-EF).[2] Other conventions include six groups of two hexadecimal digits separated by colons (:) (e.g. 01:23:45:67:89:AB), and three groups of four hexadecimal digits separated by dots (.) (e.g. 0123.4567.89AB); again in transmission order.[30]

    The latter is used by Cisco (see for instance [Wayback/Archive.is] Cisco DCNM Security Configuration Guide, Release 4.0 – Configuring MAC ACLs [Support] – Cisco and [Wayback/Archive.is] Cisco IOS LAN Switching Command Reference – mac address-group through revision [Support] – Cisco), so another format to add:

    • xxxx.xxxx.xxxx (Cisco)
  4. [Wayback/Archive.is] PhysicalAddress.Parse Method (System.Net.NetworkInformation) | Microsoft Docs remarks:

    The address parameter must contain a string that can only consist of numbers and letters as hexadecimal digits. Some examples of string formats that are acceptable are as follows:

    • 001122334455
    • 00-11-22-33-44-55
    • 0011.2233.4455
    • 00:11:22:33:44:55
    • F0-E1-D2-C3-B4-A5
    • f0-e1-d2-c3-b4-a5

    Use the GetAddressBytes method to retrieve the address from an existing PhysicalAddress instance.

  5. After a bit more digging via [Wayback/Archive.is] “three groups of four hexadecimal digits separated by dots” – Google Search , I found that even more hardware MAC address formats are in use as per [Wayback/Archive.is] What are the various standard and industry practice ways to express a 48-bit MAC address? – Network Engineering Stack Exchange.

    I really do not have all the sources for the various representations for 48-bit MAC addresses, but I have seen them variously used:

    AA-BB-CC-DD-EE-FF
    AA.BB.CC.DD.EE.FF
    AA:BB:CC:DD:EE:FF
    AAA-BBB-CCC-DDD
    AAA.BBB.CCC.DDD
    AAA:BBB:CCC:DDD
    AAAA-BBBB-CCCC
    AAAA.BBBB.CCCC
    AAAA:BBBB:CCCC
    AAAAAA-BBBBBB
    AAAAAA.BBBBBB
    AAAAAA:BBBBBB

From the last list, which is far more complete than the others, I recognise quite a few from tools I used in the past, but too forgot the actual sources, so I took the full list from there and tried to name them in parenthesis after the links I found above and what I remembered:

  • AABBCCDDEEFF (Bare / Landesk)
  • AA-BB-CC-DD-EE-FF (IEEE 802 / Windows)
  • AA.BB.CC.DD.EE.FF (???)
  • AA:BB:CC:DD:EE:FF (Linux / BSD / MacOS)
  • AAA-BBB-CCC-DDD (???)
  • AAA.BBB.CCC.DDD (Cisco?)
  • AAA:BBB:CCC:DDD (???)
  • AAAA-BBBB-CCCC (???)
  • AAAA.BBBB.CCCC (Cisco / Brocade)
  • AAAA:BBBB:CCCC (???)
  • AAAAAA-BBBBBB (Hewlett-Packard networking)
  • AAAAAA.BBBBBB (???)
  • AAAAAA:BBBBBB (???)

Some additional links in addition to the ones above:

–jeroen

Posted in .NET, CommandLine, Development, Encoding, HEX encoding, Network-and-equipment, Power User, PowerShell, PowerShell, Scripting, Software Development | Leave a Comment »

Jeff Geerling on Twitter: “I plug computers into my computers…” is indeed a PCIe KVM board based on a Raspberry Pi Compute Module 4

Posted by jpluimers on 2022/05/10

Last month, I wrote

Hopefully the picture below is the board of a PCIe KVM board based on a Raspberry Pi Compute Module 4 supporting Power over Ethernet (PoE). At least it seems to looking at the thread started by…

The thread was by Jeff Geerling on Twitter: “I plug computers into my computers…”.

Jeff followed up on this much sooner than I expected with [Wayback/Archive] Jeff Geerling on Twitter: “Hey look! That computer inside a computer thing is real now! It’s the PCIe version of the Blicube KVM: …”

Read the rest of this entry »

Posted in Compute Module, Development, Ethernet, Hardware, Hardware Development, KVM keyboard/video/mouse, Network-and-equipment, PiKVM / Pi-KVM, PoE - Power over Ethernet, Power User, Raspberry Pi, Wake-on-LAN (WoL) | Leave a Comment »

Jeff Geerling on Twitter: “I plug computers into my computers…”

Posted by jpluimers on 2022/04/20

Hopefully the picture below is the board of a PCIe KVM board based on a Raspberry Pi Compute Module 4 supporting Power over Ethernet (PoE).

At least it seems to looking at the thread started by [Wayback/Archive] Jeff Geerling on Twitter: “I plug computers into my computers… “:

It would also very much match the below issue that Jeff raised:

Read the rest of this entry »

Posted in Development, Ethernet, Hardware, Hardware Development, KVM keyboard/video/mouse, Network-and-equipment, PiKVM / Pi-KVM, PoE - Power over Ethernet, Power User, Raspberry Pi | Leave a Comment »

Perkeep lets you permanently keep your stuff, for life.

Posted by jpluimers on 2022/03/30

For my link archive: [Wayback] Perkeep

Via [Wayback] bradfitz – Joining Tailscale: Simplifying Networking, Authentication, and Authorization (which has many interesting linkis, including [Archive.is] bradfitz/homelab: Brad’s homelab setup)

–jeroen

Posted in Cloud, Hardware, Infrastructure, Network-and-equipment, Perkeep, Power User, Storage, Tailscale, VPN, Wireguard | Leave a Comment »

Some links on Tailscale / Wiregard

Posted by jpluimers on 2022/03/29

For my link archive:

Related: [Wayback] Using Tailscale on Windows to network more easily with WSL2 and Visual Studio Code – Scott Hanselman’s Blog

–jeroen

Posted in Hardware, Network-and-equipment, Power User, Tailscale, VPN, Wireguard | Leave a Comment »

“Using Tailscale on Windows to network more easily with WSL2 and Visual Studio Code”

Posted by jpluimers on 2022/03/23

“Using Tailscale on Windows to network more easily with WSL2 and Visual Studio Code”

Points to [Wayback] Using Tailscale on Windows to network more easily with WSL2 and Visual Studio Code – Scott Hanselman’s Blog

 

Related:

–jeroen

Posted in Hardware, Network-and-equipment, Power User, Tailscale, VPN, Wireguard | Leave a Comment »

Wake-on LAN over tailscale VPN

Posted by jpluimers on 2022/03/22

Hey macOS desktop in the basement, thanks for going to sleep while I was in the middle of typing at you via SSH.

Maybe that should be a signal not to sleep, eh?

$ sudo wakeonlan ac:87:a3:19:7e:81
Sending magic packet to 255.255.255.255:9 with

Well, at least that works.

Related:

–jeroen

 

Posted in Hardware, Network-and-equipment, Power User, Tailscale, VPN, Wireguard | Leave a Comment »