![]() ![]() ![]() If permanent logs were not enabled, please enable them and run the WOL tests in order to see what is registered in the permanent logs for Pearl.įirst of all, thank you very much for the quick feedback regarding the former problem described here. To download permanent logs, navigate to the maintenance page, click on “download permanent logs” near the top of the page. Please also provide the firmware version of your unit as well as any networking complexities in between (different subnets, VPN, etc.) Please provide the permanent logs for your Pearl unit, as well as date/time of performed WOL attempts. Please send an email to regarding this forum post. We appreciate the granularity of your testing, however in order for our QA and development team to make better sense of your setup, more details are needed. While WOL is a BIOS level behavior that shouldn’t be affected by software or hardware shutdown, we cannot rule out the possibility that something has changed and a bug has occurred. They will be testing this specific behavior use case to see if they can reproduce it. That being said, I brought it to the attention of the QA team that you were experiencing this WOL issue specifically regarding software shutdown from the Web UI on the maintenance page. Rather, our QA team and Development teams utilize a basic Python script to trigger the command, which is tested on weekly cycles throughout firmware testing and development. WOL does work with Pearl-2 to date with all of our direct testing, however no pre-baked software applications are being used to issue these tests and commands. I have spoken to the manager of the QA team regarding your testing and your questions and his team will be touching base with me as soon as possible regarding testing. I can certainly understand your frustration given that Pearl-2 or Pearl Mini are not behaving as you would expect them to. I’m really sorry to see that you and your team are continuing to face issues with WOL with the Pearl family. It is annoying enough that a Pearl cannot shut down time-controlled via the software (only manually via WEB interface), but then it should at least be possible to wake it up the Pearl again without having to walk across the whole campus to the respective location !! We have already checked various programs here in our network laboratory at our university, … which always wake up various systems or PCs, but ust * not * any of our PEARL-2 or PEARL-Mini. Wireshark) which shows that always correct WOL packets are sent to the Pearl interface. Note: We also used a LAN analyzer Software (e.g. If the Pearl is active, communication runs perfectly …īut if the Pearl is shut down “by software command” (Maintenance -> Power Off), the LAN-interface goes into the 10Mbps state, but that’s it … never woke up … Please name any software or a program with which this scenario works in your environment !!! Then there are no “excuses” possible, that any “unknown network” might be the reason why it does not work … we now do have only a 1: 1 LAN cable connection. Unfortunately, it doesn’t help if Epiphan keeps saying that WOL works in their Pearls ( )), but at the end there is no proof, that it really works ?Īt the end of our test series here we have connected a (Windows) PC directly via a LAN cable (1: 1 and/or cross-over assignment) to a Pearl-Mini. So this WOL function is getting now very important here - if it would work … ![]() Since these devices are distributed around our campus here and, thanks to NDI support even now working over subnets, these encoders can now also be used remotely. The WOL features announced does not work, although the devices have an active LAN interface (with 10 Mbps) after being switched off, which is also quit common for WOL in such a special stand by mode. format (DEFAULT_PORT ) ,ĭefault =DEFAULT_PORT, type = int ) return parser.Recently we have invested a lot of time to get the Wake-On-LAN function in the Pearl-2 and PearMini systems to work - no CHANCE !! Raise Exception ( 'invalid MAC address format. Import socket import struct from traceback import print_excĭEFAULT_PORT = 7 # 7 or 9 or 30000 ? #BROADCAST_IPADDR = ''īROADCAST_IPADDR = '255.255.255.255' def send_magic_packet (mac_addr, port =DEFAULT_PORT ): #!/usr/bin/env python3 # -*- coding: utf-8 -*- import argparse ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |