• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

bootpc traffic

tonyolm

Basic Pleskian
I never saw this before.

One server has

255.255.255.255:bootps <=> *

when running iftop with data going back and forth.

15:31:29.539882 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.540756 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.543334 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.543431 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.544319 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.546883 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.546983 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.547848 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.550410 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.550506 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.551382 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.553927 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300
15:31:29.554025 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:e6:fa:11:9e, length: 300


Its continual.


Anyway to figure out what the mac address belongs to?
 
That mac belongs to " 000AE6 Elitegroup Computer S"

you'd need to interrogate the switch to see what port that MAC is coming from. If you wanted to be evil you could also just throw a dhcp server up and give it an IP, and take a look at it with a port scanner.
 
Evil?

Moi?

Don't you know about karma and all :)

It's not my datacenter but a clients server. Everything is fine on the server except I saw the request traffic on iftop.

Iftop should be on everyones server.
 
Back
Top