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,927 other followers

Archive for the ‘Ethernet’ Category

Netgear Prosafe GS110TP – Tweakers

Posted by jpluimers on 2020/04/24

Interesting Power over Ethernet (PoE) capable router: [WayBack] Netgear Prosafe GS110TP – Tweakers

About the same price as [WayBackAmazon.com: Netgear Prosafe GS110TP

–jeroen

Posted in Ethernet, Network-and-equipment, Power User | Leave a Comment »

XW6600 WOL – stopped working on Windows 10 – my trusty APC PDU to the rescue

Posted by jpluimers on 2020/01/17

A long time ago I wrote in Mac/PC: sending Wake-on-LAN (WOL) packets « The Wiert Corner – irregular stream of stuff “I’ve succesfully woken up these machines: HP XW6600 running ESXi 5.1 ThinkPad W701U running Windows 7”.

The XW6600 have now been demoted to Windows 10 machines that I only need every now and then, so most of the time they are shutdown.

However, with the installation of Windows 10 however, they stopped reacting to WOL (Wake on LAN).

Per web-search results, I’ve tried all the permutations of the below settings to no avail.

Luckily, my trusty APC PDU AP7921 (and little sister AP7920) helped out: when setting the “Reboot Duration” to 30 seconds or more (so the power fully drains), it can be rebooted.

Note that since I bought these a long time ago, they have been replaced by these:

Firmwares:

Power usage:

  • an XW66000 with 32 gigabytes of RAM and one hard disk takes between 0.6-1.2 Ampère of current, which at 230 Volt is 140-275 Watt.
  • over one day that is between 3.4 and 6.6 kWh

Settings tried

Read the rest of this entry »

Posted in Ethernet, Hardware, HP XW6600, Network-and-equipment, Power User, Wake-on-LAN (WoL), Windows, Windows 10 | Leave a Comment »

`ll header` in `martian source` is the Data Link Layer: 2 MAC addresses

Posted by jpluimers on 2019/06/03

The ll header field in a martian source message on linux is about the [WayBackEthernet frame – Wikipedia: Data Link Layer.

The first 6 hex digits are the source MAC address, the next are the destination MAC address:

May 10 08:59:24 linux kernel: IPv4: martian source 255.255.255.255 from 192.168.17.44, on dev eth1
May 10 08:59:24 linux kernel: ll header: 00000000: ff ff ff ff ff ff 00 0c 29 f7 0f fe 08 00 ........).....

In the above example:

  • Destination = MAC ff ff ff ff ff ff (broadcast, which corresponds with IPv4 target 255.255.255.255)
  • Source = MAC 00 0c 29 f7 0f fe (specific, which I could verify after checking out the machine having IPv4 192.168.17.44)
  • EtherType  08 00 (IPv4)

Some sources indicate it is a martian, as 255.255.255.255 is never a valid IP address, but [WayBack] Martian packet – Wikipedia: IPv4 disagrees.

References:

–jeroen

Posted in Ethernet, Network-and-equipment, Power User | Leave a Comment »

WoL (Wake on LAN) from various routers

Posted by jpluimers on 2019/02/25

Until recently, I hardly used Wake on LAN, so I never noticed that many routers nowadays can send WoL requests themselves.

A few links:

And a few ones from my previous WoL related posts:

–jeroen

Posted in Ethernet, Network-and-equipment, Power User, Wake-on-LAN (WoL) | Leave a Comment »

Windows 7..10: disable shutdown/hibernate/sleep/restart from UI

Posted by jpluimers on 2019/02/18

I needed this for the Windows 10 machine of my mentally retarded brother: WoL (wake-on LAN) for his machine always works when it is in sleep or deep sleep mode, not every now and then fails when fully powered off.

After it is disabled in the UI, you can still perform it with [WayBackshutdown.exe, so I added these shortcuts first:

Disabling the Shutdown related actions in the UI consists of two steps:

  1. Removing it from the logon screen using the registry
  2. Removing it from the user using gpedit.msc (which is wrapped in mmc.exe)

I will try to get the registry changes for the second using [WayBackRegFromApp – Generate RegEdit .reg file from Registry changes made by application (thanks [WayBack] magicandre1981 for suggesting that at [WayBackwindows – How can I use Process Monitor to detect register changes made by GPEdit modifications? – Super User).
The wrapping mmc.exeis easiest to obtain using Process Explorer, and RegFromApp likely needs to run in elevated mode.

If that fails, I can try Process Monitor as suggested by [WayBack] Tom Wijsman in [WayBackcommand line – Change group policy using windows CMD – Super User.

The reason for the above is that I want to avoid UI based modifications that are hard to script.

Remove Shutdown options from the logon screen

This is just the registry setting below.

It also removes the reboot/hibernate/sleep options from the logon screen, so you need shortcuts for that.

Remove Shutdown for the regular users UI

This can be done using either gpedit.msc (Group Policy Editor) drilling down to the local policies or secpol.msc (the Local Policy Editor):

  1. Drill down to
    1. Local Policies
    2. User Rights Management
  2. Double click Shut down the system
  3. Remove the groups you don’t want the system to shutdown
  4. Press OK to confirm

See the video below how.

I’ve removed the group Users and kept the group Administrators to allow ShutDown.

Administrators now do need to execute the above commands (for instance shutdown.exe /h /f) in with an UAC administrative token enabled!

If you do not want that, add the users that can perform Shutdown commands to a new group, then aadd that group to Shutdown the system.

If you want to perform this system wide for all users, then it’s faster to change the [WayBackWindows Explorer NoClose policy (see also [WayBackGroup Policy Registry Reference).

Read the rest of this entry »

Posted in Ethernet, Network-and-equipment, Power User, Wake-on-LAN (WoL), Windows | Leave a Comment »

 
%d bloggers like this: