similar to: Netgear FA312 Wake-on-Lan problem

Sorry for the extra info required, but I had digest mode turned on and wouldn't have received the mailing till tomorrow. I have since updated the data manually, but after 'yum update tzdata' was run, the zdump -v for EST5EDT and America/New_York all still showed a date of April 1, instead of March 11. After manually fixing, it is correct. This was mostly a question about why yum

I tested moving a box from Tao 1.0 to CentOS 3.7. All went well, as far as I can tell, with the OS upgrades, but I needed to rpm -ivh --force the desktop-* stuff. This was a minor thing to fix for no real purpose other than to just be doing it. I still get, though, the Tao screens when the graphic login screen appears. I have changed the Application->Settings->Login Screen->

I read a few days back on the list where the tzdata rpm was to take care of the new DST rules. I run CentOS 3 servers, and did a 'yum update tzdata' , but received a 2006a update of the rpm. Is this proper? It sure didn't fix anything. Thanks Steve Campbell campbell at cnpapers.com Charleston Newspapers

I'm running CentOS 3 and have just installed a Liteon lightscribe DVD/CD unit. I firstly realized I didn't know exactly how to mount it, as /dev/dvd didn't exist, I didn't want to generate anything if it already existed, and I didn't want to mess up my cdrom unit that works just fine. I mounted the device though the X window just to see how it might mount, and find that it

Mr. Parsley, the main man at the Tao Linux group, has announced that he will no longer be able to do his thing for Tao Linux. Just recently, I had decided to investigate CentOS 4 before his announcement, and liked a lot of what I saw. Due to the Tao announcement, I have decided that CentOS will "have" to be the OS for my company in the future. Hence, my new membership to this list.

Getting in late on this one, but if I didn't need to spend money, couldn't spend money, or what ever the reason may be, and the aliasing was something that needed changing on a schedule, then why not just set up multiple alias files, run cron to replace them when needed, and "newaliases", all in cron scripts? You would need to maintain as many versions as required, but sounds

I have read the Wiki for the Yum stuff, and tried to pay attention to the variations for Centos 3/Centos 4 mentioned, but for the life of me, I can't seem to get the Dag repo working properly on my CentOS 3 system. I have installed the rpmforge rpm, but this doesn't seem to do much. It does create(I think it created it) the yum.repos.d folder, and I edited the Dag repos file to be

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

I should change this to OT, as it's not really CentOS related. I had a post on the list last week asking how the rpmforge rpm was to be implemented in yum. Craig White was kind enough to list how his yum.conf is appended, I assume after he installed the rpm. Unfortunately, mine is not appended with these lines. I am running CentOS 3. I will add these lines manually, and probably remove

On a semi-related subtopic, Why do I want WoL? What concrete examples are there where it's useful? I understand what it is and how it works but the "why" has eluded me. -- Drew "Nothing in life is to be feared. It is only to be understood." --Marie Curie

Has anyone experience with WOL under Centos (5.3).? If so, how exactly do you put the machine to sleep, and how exactly do you wake it up remotely? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

>> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Rich Greenwood >> Sent: Monday, 18 May, 2020 08:34 >> To: centos at centos.org >> Subject: Re: [CentOS] ether-wake >> >> Some switch hardware can generate the packets directly, negating the need >> for a box on every VLAN. Meraki hardware can do it, but

Actually you are not correct. 1st: I didn't quote the wikipedia article,? someone sent that as an answer to my previous post. ?? (similar mindset probably, as in your response) 2: You are wrong,? broadcast packets, like for example DHCP, and also WOL (if UDP), can be routed, by the means of ip helper addresses and directed broadcasts on Cisco equipment Also, you like others seem to

On Sun, 2020-05-17 at 20:25 -0600, R C wrote: > Ok, I get that, found it before; "typically sent as a UDP datagram to > port 0, 7 or 9, or directly over Ethernet as EtherType 0x0842" > > > The keyword being 'typically', but what is it that ether-wake actually > uses/does? (I need to forward a WOL packet to a different > > vlan on some Cisco

> Actually you are not correct. > > > 1st: I didn't quote the wikipedia article,? someone sent that as an > answer to my previous post. > > ?? (similar mindset probably, as in your response) > > 2: You are wrong,? broadcast packets, like for example DHCP, and also > WOL (if UDP), can be routed, by > > the means of ip helper addresses and directed broadcasts

Hello list I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R motherboard. Integrated network card is Realtek 8111B. I can not wake the computer after I shutdown it from FreeBSD. It is a dualboot system - windows xp and freebsd. If I shutdown the computer from windows - later I can wake it up with magic packet. Even if i shutdown the machine on the boot menu with the power

Some switch hardware can generate the packets directly, negating the need for a box on every VLAN. Meraki hardware can do it, but you have to go through the dashboard so automating it isn't currently possible. Here is some documentation on forwarding WoL on catalyst 3750 switches from Cisco:

Ok,? I get that, found it before;? "typically sent as a UDP datagram to port 0, 7 or 9, or directly over Ethernet as EtherType 0x0842" The keyword being 'typically',?? but what is it that ether-wake actually uses/does?? (I need to forward a WOL packet to a different vlan on some Cisco hardware, between two Centos machines). Ron On 5/17/20 8:14 PM, John Pierce wrote: >

The WoL magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it could be sent as any network- and transport-layer protocol, although it is typically sent as a UDP <https://en.m.wikipedia.org/wiki/User_Datagram_Protocol> datagram <https://en.m.wikipedia.org/wiki/Datagram> to port <https://en.m.wikipedia.org/wiki/TCP_and_UDP_port> 0,]

Can you be more specific about the hardware? I have a setup of DELL desktop, DELL Server SuperMicro Server and couple other devices. I am using from a cgi script the next on one server to wake the other: /usr/bin/sudo /usr/sbin/ether-wake "XY::XY" -b && echo 1 All of my servers have Intel PRO 1Gbit ethernet nics(2,4,1.. ports per machine). To make the Desktop wakeup I had to do