Sfdwhf

Why did Kant, Hegel, and Adorno leave some words and phrases in the Greek alphabet?

Valid Badminton Score?

Is it okay / does it make sense for another player to join a running game of Munchkin?

Time travel short story where a man arrives in the late 19th century in a time machine and then sends the machine back into the past

What defines a dissertation?

Can criminal fraud exist without damages?

How to verify if g is a generator for p?

Is exact Kanji stroke length important?

Is it correct to write "is not focus on"?

The baby cries all morning

If you attempt to grapple an opponent that you are hidden from, do they roll at disadvantage?

How does it work when somebody invests in my business?

How does a character multiclassing into warlock get a focus?

Increase performance creating Mandelbrot set in python

Have I saved too much for retirement so far?

Go Pregnant or Go Home

Is HostGator storing my password in plaintext?

Irreducibility of a simple polynomial

Failed to fetch jessie backports repository

Is the destination of a commercial flight important for the pilot?

How was Earth single-handedly capable of creating 3 of the 4 gods of chaos?

Is there an Impartial Brexit Deal comparison site?

What's a natural way to say that someone works somewhere (for a job)?

Can a monster with multiattack use this ability if they are missing a limb?

Wake On Lan Remote Times Out 18.04

wake on lan not working if i turn of with ubuntuWake on Lan remotelyspeed up eth0 from 10 Mb/s to 100 Mb/sInternet slow on Ubuntu but not windows using a RTL8111Wake on Lan on Ubuntu?Ubuntu won't connect to Network through EthernetWake On Lan not workingWake-on-lan from suspend“Wired Connection” option is not availabe in settings->network and “MODSIGN: couldn't get UEFI db list ” is showing on boot, what is solution18.04 LTS upgrade has stopped WOL (wake-on-LAN)ssh connection times outLAN speed slow on Ubuntu 18.04, but Internet speed is fine

0

So I have wol working almost perfectly, after I shut down my pc I have approx a one-minute window where my desktop is detected as inactive by my routers 'connected devices' menu and I can send a magic packet and wake up my desktop from a remote computer using.

wakeonlan -i 174.X.XXX.XX -p 9 70:XX:XX:XX:XX:XX

After, the desktop is no longer detected by the router and the only way I can wake the desktop up is if I send the magic packet directly to the mac address from the local network.

For some reason my raspberry pi does not time out on the routers 'connected devices' and always remains visible with inactive status which leads me to believe this could be something related settings on my desktop and not my router. Or is this simply just not possible.

Here is the ethtool readout (which oddly does not show wake-on-settings unless I use sudo)

Settings for enp42s0:

Supported ports: [ TP ]

Supported link modes:   10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Supported pause frame use: Symmetric

Supports auto-negotiation: Yes

Supported FEC modes: Not reported

Advertised link modes:  10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Advertised pause frame use: Symmetric

Advertised auto-negotiation: Yes

Advertised FEC modes: Not reported

Speed: 1000Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: on (auto)

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000007 (7)

               drv probe link

Link detected: yes

I also tried adding this to /etc/default/halt and using sudo poweroff -h from terminal.

HALT=poweroff

NETDOWN=no

I also tried this

networking 18.04 shutdown

share|improve this question

asked 13 mins ago

Justin FrancisJustin Francis

1

New contributor

Justin Francis is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

0

So I have wol working almost perfectly, after I shut down my pc I have approx a one-minute window where my desktop is detected as inactive by my routers 'connected devices' menu and I can send a magic packet and wake up my desktop from a remote computer using.

wakeonlan -i 174.X.XXX.XX -p 9 70:XX:XX:XX:XX:XX

After, the desktop is no longer detected by the router and the only way I can wake the desktop up is if I send the magic packet directly to the mac address from the local network.

For some reason my raspberry pi does not time out on the routers 'connected devices' and always remains visible with inactive status which leads me to believe this could be something related settings on my desktop and not my router. Or is this simply just not possible.

Here is the ethtool readout (which oddly does not show wake-on-settings unless I use sudo)

Settings for enp42s0:

Supported ports: [ TP ]

Supported link modes:   10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Supported pause frame use: Symmetric

Supports auto-negotiation: Yes

Supported FEC modes: Not reported

Advertised link modes:  10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Advertised pause frame use: Symmetric

Advertised auto-negotiation: Yes

Advertised FEC modes: Not reported

Speed: 1000Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: on (auto)

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000007 (7)

               drv probe link

Link detected: yes

I also tried adding this to /etc/default/halt and using sudo poweroff -h from terminal.

HALT=poweroff

NETDOWN=no

I also tried this

networking 18.04 shutdown

share|improve this question

asked 13 mins ago

Justin FrancisJustin Francis

1

New contributor

Justin Francis is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

So I have wol working almost perfectly, after I shut down my pc I have approx a one-minute window where my desktop is detected as inactive by my routers 'connected devices' menu and I can send a magic packet and wake up my desktop from a remote computer using.

wakeonlan -i 174.X.XXX.XX -p 9 70:XX:XX:XX:XX:XX

After, the desktop is no longer detected by the router and the only way I can wake the desktop up is if I send the magic packet directly to the mac address from the local network.

For some reason my raspberry pi does not time out on the routers 'connected devices' and always remains visible with inactive status which leads me to believe this could be something related settings on my desktop and not my router. Or is this simply just not possible.

Here is the ethtool readout (which oddly does not show wake-on-settings unless I use sudo)

Settings for enp42s0:

Supported ports: [ TP ]

Supported link modes:   10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Supported pause frame use: Symmetric

Supports auto-negotiation: Yes

Supported FEC modes: Not reported

Advertised link modes:  10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Advertised pause frame use: Symmetric

Advertised auto-negotiation: Yes

Advertised FEC modes: Not reported

Speed: 1000Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: on (auto)

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000007 (7)

               drv probe link

Link detected: yes

I also tried adding this to /etc/default/halt and using sudo poweroff -h from terminal.

HALT=poweroff

NETDOWN=no

I also tried this

networking 18.04 shutdown

share|improve this question

asked 13 mins ago

Justin FrancisJustin Francis

1

New contributor

Justin Francis is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

wakeonlan -i 174.X.XXX.XX -p 9 70:XX:XX:XX:XX:XX

Settings for enp42s0:

Supported ports: [ TP ]

Supported link modes:   10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Supported pause frame use: Symmetric

Supports auto-negotiation: Yes

Supported FEC modes: Not reported

Advertised link modes:  10baseT/Half 10baseT/Full 

                        100baseT/Half 100baseT/Full 

                        1000baseT/Full 

Advertised pause frame use: Symmetric

Advertised auto-negotiation: Yes

Advertised FEC modes: Not reported

Speed: 1000Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: on (auto)

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000007 (7)

               drv probe link

Link detected: yes

HALT=poweroff

NETDOWN=no

share|improve this question

asked 13 mins ago

Justin FrancisJustin Francis

1

New contributor

Justin Francis is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 13 mins ago

Justin FrancisJustin Francis

1

New contributor

Justin Francis is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 13 mins ago

Justin FrancisJustin Francis

1

New contributor

Justin Francis is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 13 mins ago

Justin FrancisJustin Francis

1