• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

bootpc traffic

T

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.
 
You must log in or register to reply here.

Similar threads

T
Question Fail2ban trying to setup a rule to ban ai bots
Replies
4
Views
3K
Bitpalast
Bitpalast
michaeljoseph01
Question Imunify360 or fail2ban PLEASE give me your input
Replies
6
Views
4K
The 8th
The 8th
M
Question fail2ban, can I ban visitors with no user agent?
Replies
1
Views
1K
Kaspar@Plesk
Kaspar@Plesk
Endre
Issue Unable to access the remote backup storage using SFTP
Replies
6
Views
3K
Endre
Endre
burnley
Forwarded to devs After Onyx -> Obsidian upgrade we see "graceful-req",false followed by "stop-start",true in apache_restart_stat.log
Replies
6
Views
2K
burnley
burnley
Back
Top