OIT Network Systems

Devices Blocked from Visitor IP Service

This is a list of devices currently blocked from receiving OIT Visitor IP Service.

For information about the service, see Visitor IP Service.

Note that Visitor IP Service is also unavailable to Devices Blocked from Temporary Unregistered Dormnet IP Address Service, Devices Blocked from Temporary Visitor Wireless Network Access, and Devices Blocked from OIT Mobile IP Service.

This document is updated several times each day; it was last updated at Mon Nov 23 03:01:04 2009.

Devices Declared Ineligible for Visitor IP Service

The devices listed below have been declared ineligible for Visitor IP Service.

Often this is because the DHCP client operates in such a way as to interfere with other customers of the service. (Sometimes this is due to a bug in the DHCP client implementation; sometimes it is due to misconfiguration of the client.)

Other times it may because the device is the source of inappropriate IP traffic (e.g. an attack directed at other computers or at the network).

Hardware Address Date Reason Ineligible
0:0:0:60:4a:27 Oct 18 2007 compromised
0:0:39:4b:58:f7 Jan 5 2005 compromised
0:0:39:56:3a:e9 July 6 2005 compromised
0:0:39:73:7:8d Nov 14 2005 compromised
0:0:4c:2e:13:b3 May 17 2004 compromised
0:0:86:43:6b:d6 June 23 2004 broken DHCP client, ignores lease expiration time
0:0:86:5a:60:bc Apr 6 2005 compromised
0:0:86:5d:7a:9b Jan 28 2004 stealing IP addresses
0:0:86:62:3d:7e Apr 5 2005 compromised
0:0:aa:c2:6c:1f Feb 27 2009 ignores DHCP lease time
0:10:60:f6:e7:f9 Nov 28 2006 broken DHCP client
0:10:99:4:ae:10 Aug 4 2007
0:10:99:4:ae:11 Aug 4 2007 rogue DHCP server
0:10:a4:14:ec:f Aug 25 2005 compromised
0:10:a4:16:73:a9 June 7 2007 compromised
0:10:a4:9a:c2:87 Aug 23 2006 theft of service
0:10:a4:b2:f6:ed Oct 18 2005 compromised
0:10:a4:c4:56:b9 Aug 12 2005 compromised
0:10:a4:fc:30:a6 Aug 5 2005 compromised
0:10:b5:3d:44:db Oct 21 2007
0:10:b5:74:74:2f Jan 28 2005 compromised
0:10:b5:d:f4:a0 Jan 8 2005 compromised
0:10:e0:1:be:4a Feb 27 2006 compromised
0:11:11:2a:1f:d5 Oct 19 2006
0:11:24:5:ba:c2 Jan 15 2007 WAP re-attached in residential space covered by OIT Wirelesss Service
0:11:24:5:ba:c3 Jan 15 2007 WAP re-attached in residential space covered by OIT Wirelesss Service
0:11:24:5:fe:a Nov 8 2006 broken DHCP client
0:11:24:8f:2f:40 Mar 20 2005 theft of service
0:11:24:99:ea:29 Oct 9 2008 broken DHCP client
0:11:24:c4:56:73 July 3 2008 as per IT Policy Advisor mail
0:11:2f:28:48:e3 July 28 2006 compromised
0:11:2f:4f:b5:b9 Oct 14 2005 compromised
0:11:43:5f:3b:58 Jan 7 2007 stealing TUD IP
0:11:43:7a:9c:e2 Dec 10 2007 compromised
0:11:50:5c:43:70 Sep 10 2005 rogue DHCP server
0:11:50:70:f1:98 August 7 2008 as per IT Policy Advisor mail
0:11:9:5c:af:7a Oct 9 2008 compromised
0:11:d9:1:9e:27 Feb 9 2009 ignores DHCP lease time
0:11:f5:32:d8:26 October 12 2009 compromised
0:11:f5:a:8:99 May 31 2007 rogue DHCP server
0:12:17:55:17:92 Oct 30 2006 persistently attached without being registered
0:12:17:7f:b0:68 August 19 2007 rogue wireless bridge stealing IP
0:12:17:7f:b0:69 August 19 2007 connected via rogue wireless bridge
0:12:17:ae:59:ef July 9 2007 rogue DHCP server
0:12:3:c2:e5:b6 August 10 2007 configured to steal IP address
0:12:3f:1c:aa:7 Aug 22 2008 rogue DHCP server
0:12:3f:1f:f5:b8 May 21 2009 persistent extended pinging of OIT router
0:12:3f:75:59:33 Feb 26 2006 theft of service
0:12:3f:c:cb:29 October 16 2009 blocked as per IT Policy Advisor mail
0:12:3f:e3:5c:a2 October 16 2009 malfunctioning NAT software or hardware
0:12:5a:a2:4f:de June 8 2007 using wrong IP and excessive broadcast traffic
0:12:bf:4d:de:ae Sep 7 2007 compromised
0:12:f0:7a:b6:5b Dec 10 2007 compromised
0:12:f0:93:fb:90 August 10 2007 configured to steal IP address
0:12:f0:a2:73:b2 July 17 2007 as per IT Policy Advisor mail
0:12:f0:a9:ba:87 October 16 2009 blocked as per IT Policy Advisor mail
0:12:f0:c5:a6:f Oct 22 2007 malfunctioning NAT
0:12:f0:cb:a6:58 June 14 2009 rogue DHCP server
0:13:02:6f:67:ef Nov 8 2007 rogue wireless access bridge
0:13:02:b1:89:d0 May 27 2009 blocked as per IT Policy Advisor mail
0:13:10:47:cf:88 April 5 2007 as per IT Policy Advisor mail
0:13:10:7e:8c:ac July 11 2005 broken DHCP client
0:13:10:98:d3:36 Dec 1 2006 rogue network bridge
0:13:10:a2:ad:cf Jan 18 2007 rogue DHCP server
0:13:10:c3:6d:8e May 16 2006 device causing bridge loop
0:13:10:c3:6d:8f May 16 2006 device causing bridge loop
0:13:10:e2:59:51 March 9 2007 rogue wireless bridge stealing IP
0:13:11:ae:b5:a May 11 2007 connected via rogue wireless bridge
0:13:20:a8:5:a3 August 1 2007 as per IT Policy Advisor mail
0:13:21:10:50:66 Aug 22 2008 using inappropriate IP addresses
0:13:2:2c:fc:d2 Nov 7 2008 rogue DHCP server
0:13:2:3d:89:b7 Feb 20 2009 blocked as per IT Policy Advisor mail
0:13:2:47:94:e1 Sep 20 2006
0:13:2:8:49:76 April 2 2007 as per IT Policy Advisor mail
0:13:2:9a:7e:c6 Nov 22 2006 rogue DHCP server
0:13:2:b1:f6:fb Oct 9 2008 compromised
0:13:2:c7:6c:3d Feb 17 2008 rogue wireless bridge stealing IP
0:13:2:cc:92:fe Dec 29 2008 banned from network
0:13:49:24:c:b6 July 19 2005 banned from network
0:13:60:e2:c1:19 Sep 17 2008 rogue DHCP server
0:13:60:e2:c1:1a Sep 17 2008 rogue DHCP server
0:13:a9:3f:ac:5d Sep 10 2008 incorrect response to broadcast traffic
0:13:a9:47:38:4e May 9 2009 rogue DHCP server
0:13:b6:33:49:af October 2 2009 configured to steal IP address
0:13:ce:20:37:9b July 15 2008 as per IT Policy Advisor mail
0:13:ce:20:dc:52 Dec 8 2007 rogue DHCP server
0:13:ce:2b:4f:4b Feb 18 2009 blocked as per IT Policy Advisor mail
0:13:ce:2b:79:c0 October 16 2009 malfunctioning NAT software or hardware
0:13:ce:35:7c:3 May 21 2009 persistent extended pinging of OIT router
0:13:ce:44:42:4b Nov 30 2008 blocked as per IT Policy Advisor mail
0:13:ce:bb:41:3 August 7 2008 as per IT Policy Advisor mail
0:13:ce:cc:80:67 Feb 8 2008 rogue wireless bridge stealing IP
0:13:ce:e7:20:5c Nov 16 2007 rogue DHCP server
0:13:d3:75:76:9b July 13 2009 stole many IP addresses
0:13:d3:75:d:5f Jan 11 2007 rogue DHCP server
0:13:d3:76:bf:c3 March 14 2009 using IP address not assigned for its use
0:13:e8:7c:a4:f9 March 31 2009 blocked as per IT Policy Advisor mail
0:13:e8:83:45:2d Aug 23 2008 as per IT Policy Advisor mail
0:13:e8:b:85:83 Sep 25 2008 sending erroneous DHCP traffic
0:13:e8:e8:e3:89 Feb 19 2008 rogue wireless bridge stealing IP
0:13:e8:f6:bc:d1 Dec 18 2008 rogue wireless bridge stealing IP
0:14:22:af:af:77 Dec 14 2008 rogue DHCP server
0:14:22:e4:96:1a August 7 2008 as per IT Policy Advisor mail
0:14:22:f6:1:cb Oct 18 2007 as per IT Policy Advisor mail
0:14:38:6:f:e5 Feb 26 200 theft of service
0:14:51:8:95:2c Aug 30 2007 excessive DHCP traffic
0:14:51:ed:2a:da Aug 2 2006 stole IP address, and broken DHCP client
0:14:51:ef:ea:8c August 13 2008 rogue wireless bridge stealing IP
0:14:6c:a6:ec:7f Sep 29 2006 malfunctioning NAT
0:14:a5:23:8d:3b July 24 2008 excessive DNS traffic
0:14:a5:24:a9:16 Oct 23 2008 rogue DHCP server
0:14:a5:27:25:3b May 5 2008 as per IT Policy Advisor mail
0:14:a5:4f:cb:d4 July 27 2008 stealing IP address
0:14:a5:70:3:59 Aug 2 2006 broken DHCP client
0:14:a5:7a:bf:c6 August 8 2008 as per IT Policy Advisor mail
0:14:a5:7c:8e:3a Nov 16 2007 excessive ICMP traffic
0:14:a5:83:36:87 September 14 2009 blocked as per IT Policy Advisor mail
0:14:a5:8f:cd:d8 August 7 2008 as per IT Policy Advisor mail
0:14:a5:ad:90:a3 Aug 6 2007 as per IT Policy Advisor mail
0:14:a5:b0:b8:72 Nov 9 2006
0:14:a5:bf:ee:d9 Sep 10 2008 rogue DHCP server
0:14:a5:cf:d3:7f July 3 2008 as per IT Policy Advisor mail
0:14:a5:ee:42:7a August 1 2007 malfunctioning DHCP client software
0:14:a5:ee:d8:1c April 24 2008 as per IT Policy Advisor mail
0:14:a5:f7:93:5a Feb 20 2008 rogue wireless bridge stealing IP
0:14:bf:14:dc:be July 9 2008 rogue DHCP server
0:14:bf:42:12:3 October 24 2009 rogue DHCP server
0:14:bf:79:4f:e9 June 19 2006 malfunctioning NAT
0:14:bf:e3:4d:1a July 18 2009 rogue wireless bridge stealing IP
0:15:2:e2:2:15 September 2 2009 malfunctioning DHCP client
0:15:af:e4:86:b7 August 10 2009 ignores DHCP lease time
0:15:c5:17:e6:80 August 19 2007 rogue wireless bridge stealing IP
0:15:c5:21:c:c4 Oct 9 2008 compromised
0:15:c5:6:a9:7f Sep 21 2006 client of rogue network bridge
0:15:c5:7a:8b:a5 July 24 2008 as per IT Policy Advisor mail
0:15:c5:8:c5:6 Jan 15 2007 hardware address forgery, stealing TUD IP and Mobile IP
0:15:c5:cf:3a:56 July 24 2008 compromised
0:15:c5:d1:24:6f August 10 2009 rogue DHCP server
0:15:eb:14:91:47 Nov 9 2006 connected via rogue wireless bridge
0:16:36:87:e9:68 August 1 2007 malfunctioning DHCP client software
0:16:36:fc:cd:43 August 1 2007 as per IT Policy Advisor mail
0:16:41:52:47:bf August 8 2009 blocked as per IT Policy Advisor mail
0:16:44:73:67:6 July 30 2008 source of erroneous DHCP traffic
0:16:63:95:10:7d Aug 21 2008 rogue DHCP server
0:16:63:c4:21:6e Aug 21 2008 rogue DHCP server
0:16:6f:2c:a:ee April 2 2009 blocked as per IT Policy Advisor mail
0:16:6f:74:39:f4 Oct 4 2006 rogue wireless bridge stealing IP
0:16:6f:8c:6c:64 Sep 13 2008 running two simultaneous DHCP clients
0:16:6f:9b:8a:7e Mar 1 2007 as per IT Policy Advisor mail
0:16:b6:b6:d2:0 June 8 2007 erroneous response to broadcast traffic
0:16:cb:5:41:d6 March 4 2008 rogue wireless bridge stealing IP
0:16:cb:6:93:a Feb 15 2007 rogue wireless bridge stealing IP
0:16:cb:7:9e:2f Jan 23 2008 rogue wireless bridge stealing IP
0:16:cb:8:9a:66 May 21 2009 rogue wireless bridge stealing IP
0:16:cb:96:c0:b4 Oct 20 2008 running multiple DHCP clients on a single network interface simultaneously
0:16:cb:9:1d:50 Jan 21 2009 rogue wireless bridge stealing IP
0:16:cb:9:9:59 Dec 22 2007 rogue wireless bridge stealing IP
0:16:cb:9:f:f4 Feb 27 2008 rogue wireless bridge stealing IP
0:16:cb:9b:2d:b4 August 15 2008 repeated hardware address forgery
0:16:cb:b7:43:f8 Oct 31 2006 rogue wireless bridge, also stealing IP
0:16:cb:b8:10:81 Nov 15 2006 rogue wireless bridge stealing IP
0:16:cb:b8:3b:15 June 11 2008 rogue wireless bridge stealing IP
0:16:cb:b9:6:f2 Sep 6 2008 rogue wireless bridge stealing IP
0:16:cb:b9:8:62 May 16 2007 rogue wireless bridge stealing IP
0:16:cb:b9:d8:df April 28 2009 rogue wireless bridge stealing IP
0:16:cb:ba:63:70 June 4 2007 rogue wireless bridge stealing IP
0:16:cb:ba:b2:30 Oct 8 2006 rogue wireless bridge, also stealing IP
0:16:cb:bc:46:4d June 11 2008 rogue wireless bridge stealing IP
0:16:cb:bc:87:e3 March 19 2008 rogue wireless bridge stealing IP
0:16:cb:bc:8e:76 Feb 28 2007 rogue wireless bridge stealing IP
0:16:cb:bf:a:40 Feb 7 2007 rogue wireless bridge stealing IP
0:16:cb:d0:2:95 Nov 20 2008 running multiple DHCP clients on a single network interface
0:16:ce:19:57:70 Jan 24 2008 sending spam
0:16:ce:37:3b:13 July 17 2007 as per IT Policy Advisor mail
0:16:ce:55:c8:fb Aug 7 2006 theft of service
0:16:ce:77:62:7b August 8 2009 blocked as per IT Policy Advisor mail
0:16:ce:e:62:57 Aug 2 2006 rogue DHCP server
0:16:d3:2:c8:6d Nov 16 2007 excessive ICMP traffic
0:16:d4:96:9a:16 Sep 25 2008 sending erroneous DHCP traffic
0:16:d4:c:b:90 Sep 20 2006
0:17:3f:42:f0:ff June 29 2007 malfunctioning DHCP client
0:17:3f:af:99:f7 March 11 2008 rogue DHCP server
0:17:3f:fc:e6:dd Nov 26 2007 stealing IP address
0:17:f2:31:c6:e2 Jan 15 2007 hardware address forgery, stealing TUD IP and Mobile IP
0:17:f2:32:10:e6 August 24 2009 blocked as per IT Policy Advisor mail
0:17:f2:3f:7a:40 Nov 20 2008 running multiple DHCP clients on a single network interface
0:17:f2:3f:d3:51 August 10 2007 rogue wireless bridge stealing IP
0:17:f2:41:c:35 May 26 2007 rogue wireless bridge stealing IP
0:17:f2:42:1f:55 June 24 2008 as per IT Policy Advisor mail
0:17:f2:42:7d:98 June 12 2008 as per IT Policy Advisor mail
0:17:f2:42:c9:e1 Oct 8 2008 running multiple DHCP clients on a single network interface simultaneously
0:17:f2:48:50:d7 Sep 11 2007 rogue wireless bridge stealing IP
0:17:f2:48:9a:eb April 18 2007 rogue wireless bridge stealing IP
0:17:f2:4b:cc:5e August 20 2008 rogue wireless bridge stealing IP
0:17:f2:4c:17:db August 7 2009 erroneously forwarding some broadcast traffic
0:17:f2:4c:5b:75 Sep 14 2007 rogue wireless bridge stealing IP
0:17:f2:4c:e8:76 Nov 3 2006 rogue wireless bridge stealing IP
0:17:f2:4d:60:92 March 29 2008 as per IT Policy Advisor mail
0:17:f2:4e:7f:94 May 13 2007 rogue wireless bridge stealing IP
0:17:f2:4e:ec:b1 Oct 2 2006 rogue wireless bridge stealing IP
0:17:f2:4e:ed:c0 Jan 15 2007 hardware address forgery, stealing TUD IP and Mobile IP
0:17:f2:4f:14:1d August 15 2008 repeated hardware address forgery
0:17:f2:50:c5:53 Nov 9 2006 rogue wireless bridge, also stealing IP
0:17:f2:52:eb:bf April 19 2007 rogue wireless bridge stealing IP
0:17:f2:97:ea:14 July 8 2008 rogue wireless bridge stealing IP
0:17:f2:c5:29:59 August 17 2008 connected via rogue wireless bridge
0:17:f2:d3:a8:8c August 9 2008 as per IT Policy Advisor mail
0:17:f2:e6:c5:c6 Nov 16 2007 rogue wireless access bridge
0:17:f2:e6:e7:54 May 2 2008 rogue wireless bridge stealing IP
0:17:f2:e7:c:e9 August 17 2008 rogue wireless bridge stealing IP
0:17:f2:e7:ee:dc Dec 11 2006 rogue wireless bridge
0:17:f2:e9:52:5d October 13 2009 blocked as per IT Policy Advisor mail
0:17:f2:eb:34:6 August 24 2009 blocked as per IT Policy Advisor mail
0:17:f2:eb:b5:f3 Jan 25 2007 rogue wireless bridge stealing IP
0:17:f2:eb:f7:15 March 31 2009 blocked as per IT Policy Advisor mail
0:17:f2:ec:24:bc Dec 14 2006 rogue wireless bridge
0:17:f2:ee:33:eb March 9 2007 rogue wireless bridge stealing IP
0:18:24:63:38:c7 Aug 22 2008 as per IT Policy Advisor mail
0:18:2:45:d6:fa July 26 2007 misconfigured DHCP client
0:18:39:3f:10:7c March 5 2008 rogue DHCP server
0:18:39:d8:7b:c2 July 18 2009 connected via rogue wireless bridge
0:18:39:f1:98:e3 Sep 9 2007 rogue DHCP server
0:18:41:4:a8:7 July 12 2008 rogue DHCP server
0:18:8b:db:39:7d September 8 2009 blocked as per IT Policy Advisor mail
0:18:92:3a:20:2a August 3 2008 rogue wireless bridge stealng IP
0:18:de:14:48:a6 August 12 2008 as per IT Policy Advisor mail
0:18:de:26:fb:f6 Oct 29 2008 as per IT Policy Advisor mail
0:18:de:32:8:10 November 4 2008 rogue wireless bridge stealing IP
0:18:de:71:6d:e4 Feb 24 2007 rogue wireless bridge stealing IP
0:18:de:86:99:b0 June 24 2008 running multiple DHCP clients on one interface
0:18:de:8a:16:6a Jan 20 2008 using many incorrect IP addresses
0:18:e4:60:84:60 June 11 2008 connected via rogue wireless bridge
0:18:e7:29:9:c8 Jan 12 2008 rogue DHCP server
0:18:e7:5:6d:25 Feb 18 2008 rogue DHCP server
0:18:e7:b:4c:d8 August 2 2007 banned from network
0:18:e7:b:4c:d9 August 2 2007 banned from network
0:18:f8:ad:86:10 July 4 2007 as per IT Policy Advisor mail
0:19:79:99:2:17 July 7 2009 forwarding broadcast traffic
0:19:7d:3:e5:44 July 24 2008 compromised
0:19:7d:3a:6a:18 July 13 2009 configured to steal IP address
0:19:7d:58:d9:41 August 3 2008 rogue wireless bridge stealing IP
0:19:7e:72:b0:30 July 24 2008 as per IT Policy Advisor mail
0:19:7e:79:18:f5 June 17 2008 as per IT Policy Advisor mail
0:19:7e:86:54:78 September 8 2009 blocked as per IT Policy Advisor mail
0:19:7e:90:ca:5 May 2 2009 rogue wireless bridge stealing IP
0:19:7e:c4:2:9 Sep 10 2007 rogue DHCP server
0:19:b9:81:f7:b7 Oct 18 2007 as per IT Policy Advisor mail
0:19:d2:2c:5a:24 July 15 2008 as per IT Policy Advisor mail
0:19:d2:6d:20:b7 March 31 2008 as per IT Policy Advisor mail
0:19:d2:70:1d:38 March 17 2007 rogue DHCP server
0:19:d2:79:28:c4 March 24 2007 rogue DHCP server
0:19:d2:a:1a:b0 June 30 2008 rogue DHCP server
0:19:d2:c7:20:25 Oct 27 2007 rogue wireless bridge stealing IP
0:19:d2:d5:81:92 June 24 2008 stole IP address
0:19:e3:07:a4:23 June 2 2008 rogue wireless bridge stealing IP
0:19:e3:0:db:e3 March 26 2009 rogue wireless bridge stealing IP
0:19:e3:43:8d:ff August 24 2009 using incorrect IP addresses
0:19:e3:4:2c:23 Nov 5 2008 rogue wireless bridge stealing IP
0:19:e3:4:44:55 October 24 2009 configured to steal IP addresses
0:19:e3:4:8c:8f July 7 2008 as per IT Policy Advisor mail
0:19:e3:6:3:87 Feb 14 2007 rogue wireless bridge stealing IP
0:19:e3:6:72:fb May 5 2008 as per IT Policy Advisor mail
0:19:e3:6:86:26 August 1 2007 rogue wireless bridge stealing IP
0:19:e3:7:a:d6 June 17 2009 rogue wireless bridge stealing IP
0:19:e3:9:2:7d May 11 2007 rogue wireless bridge stealing IP
0:19:e3:d4:13:64 Jan 26 2008 rogue wireless bridge stealing IP
0:19:e3:d7:47:bc March 22 2007 rogue wireless bridge stealing IP
0:19:e3:d8:cf:65 August 9 2008 as per IT Policy Advisor mail
0:1:2:31:e9:e0 May 13 2004 compromised
0:1:2:94:a4:cd Dec 21 2004 compromised
0:1:3:25:b7:66 Feb 17 2005 compromised
0:1:3:d0:d3:8d Jan 4 2005 compromised
0:1:4a:1d:8f:11 Aug 22 2008 hardware address forgery
0:1a:4d:46:27:11 March 29 2008 hardware address forgery
0:1a:73:29:c2:94 August 1 2007 as per IT Policy Advisor mail
0:1a:73:3:6f:2d August 14 2009 blocked as per IT Policy Advisor mail
0:1a:73:66:71:2b Sep 25 2007 rogue wireless bridge stealing IP
0:1a:73:74:3e:6 Aug 22 2008 as per IT Policy Advisor mail
0:1a:73:93:e8:71 July 18 2008 as per IT Policy Advisor mail
0:1a:73:b7:59:23 Sep 16 2008 rogue DHCP server
0:1a:73:c4:80:1a July 24 2008 as per IT Policy Advisor mail
0:1a:92:bb:70:24 October 23 2008 IP address theft
0:1a:92:bb:70:25 October 23 2008 IP address theft
0:1b:11:26:de:10 October 24 2008 rogue DHCP server
0:1b:11:e7:bd:b3 Jan 28 2009 running multiple DHCP clients on a single network interface
0:1b:24:b7:71:62 Sep 16 2008 rogue DHCP server
0:1b:24:ba:53:42 October 6 2009 configured to steal IP addresses
0:1b:2f:6e:b6:f0 May 11 2009 poorly-behaved DHCP client
0:1b:38:95:3a:ca July 24 2008 as per IT Policy Advisor mail
0:1b:38:c6:bf:99 Aug 22 2008 as per IT Policy Advisor mail
0:1b:63:0:fc:6c March 20 2008 rogue wireless bridge stealing IP
0:1b:63:25:2e:52 August 9 2008 configured to steal an IP address
0:1b:63:95:10:7d June 20 2008 rogue DHCP server
0:1b:63:bf:fe:7f Jan 4 2008 rogue wireless bridge stealing IP
0:1b:63:c4:21:6e June 20 2008 rogue DHCP server
0:1b:63:c8:9c:49 August 7 2007 rogue wireless bridge stealing IP
0:1b:63:c8:ad:e May 7 2008 as per IT Policy Advisor mail
0:1b:63:c8:f4:6b May 12 2009 blocked as per IT Policy Advisor mail
0:1b:63:ca:14:c6 Dec 8 2007 rogue wireless bridge stealing IP
0:1b:63:cd:c0:2d Sep 25 2008 rogue wireless bridge stealing IP
0:1b:63:ce:47:fd August 24 2009 using incorrect IP addresses
0:1b:63:d5:f:b7 June 14 2009 rogue DHCP server
0:1b:63:de:9a:8 Dec 31 2008 rogue DHCP server
0:1b:6f:69:32:1d March 9 2007 connected via rogue wireless bridge
0:1b:77:1c:8d:c8 Dec 16 2008 malfunctioning DHCP client
0:1b:77:21:4:a4 Sep 17 2008 excessive DNS traffic
0:1b:77:9c:59:d8 Oct 18 2007 as per IT Policy Advisor mail
0:1b:77:a7:c4:86 June 17 2008 as per IT Policy Advisor mail
0:1b:77:c1:f4:4a October 19 2009 rogue wireless bridge stealing IP
0:1b:77:c2:64:26 Dec 2 2007 broken DHCP client
0:1b:9e:29:29:ea July 7 2008 as per IT Policy Advisor mail
0:1c:23:4d:b:57 July 24 2008 compromised
0:1c:23:59:2e:d4 Oct 28 2008 configured to steal IP
0:1c:42:19:2b:d4 October 17 2009 connected via rogue wireless bridge
0:1c:42:1a:2a:a8 May 11 2009 connected via rogue wireless bridge
0:1c:42:1c:5d:44 Jan 26 2008 connected via rogue wireless bridge
0:1c:42:33:a2:51 November 13 2009 connected via rogue wireless bridge
0:1c:42:38:88:b9 October 29 2009 connected via rogue wireless bridge
0:1c:42:44:55:73 October 17 2009 connected via rogue wireless bridge
0:1c:42:48:db:9b August 6 2008 connected via rogue wireless bridge
0:1c:42:58:95:9e March 20 2008 connected via rogue wireless bridge
0:1c:42:67:41:6 Nov 21 2008 connected via rogue wireless bridge
0:1c:42:69:32:b8 June 11 2008 connected via rogue wireless bridge
0:1c:42:6f:39:39 November 11 2008 connected via rogue wireless bridge
0:1c:42:92:49:35 Sep 18 2008 obtaining service via rogue wireless bridge
0:1c:42:cb:43:7e Dec 6 2007 connected via rogue wireless bridge
0:1c:42:ea:d9:a0 July 9 2009 connected via rogue wireless bridge
0:1c:42:eb:24:a4 Jan 4 2008 connected via rogue wireless bridge
0:1c:42:fb:e9:3f Dec 6 2008 connected via rogue wireless bridge
0:1c:42:ff:1e:bf August 7 2007 connected via rogue wireless bridge
0:1c:b3:b7:c:9f August 6 2008 rogue wireless bridge stealing IP
0:1c:b3:b8:70:94 March 29 2009 blocked as per IT Policy Advisor mail
0:1c:b3:ba:18:c8 June 1 2009 rogue wireless bridge stealing IP
0:1c:b3:ba:ef:1b May 28 2008 as per IT Policy Advisor mail
0:1c:b3:bc:e4:9f November 13 2009 rogue wireless bridge stealing IP
0:1c:b3:c0:b7:4f March 29 2009 broken DHCP client
0:1c:b3:c4:3:f7 Oct 21 2008 malfunctioning DHCP client
0:1c:b3:c4:3:f8 Oct 21 2008 malfunctioning DHCP client
0:1c:b3:c5:4d:a5 June 1 2008 as per IT Policy Advisor mail
0:1c:bf:2d:e:b2 June 23 2009 blocked as per IT Policy Advisor mail
0:1c:bf:be:c2:bf August 10 2009 blocked as per IT Policy Advisor mail
0:1c:bf:ce:ae:ad Aug 22 2008 as per IT Policy Advisor mail
0:1c:bf:d6:1b:9f October 12 2009 excessive DNS traffic
0:1c:bf:d6:2f:de October 12 2009 excessive DNS traffic
0:1c:cc:94:b4:ac Dec 18 2008 malfunctioning DHCP client
0:1c:cc:d4:7a:4f Oct 21 2008 malfunctioning DHCP client
0:1c:cc:e7:57:f8 August 21 2008 broken DHCP client
0:1c:df:5d:f0:8d July 30 2008 rogue DHCP server
0:1c:f0:fe:c4:9d October 14 2009 rogue wireless bridge, and defective DHCP client
0:1d:4f:27:e1:7 July 15 2009 configured to steal IP address
0:1d:4f:35:30:3d June 11 2008 connected via rogue wireless bridge
0:1d:4f:d8:4a:47 October 6 2009 using IP address not assigned for its use
0:1d:4f:e8:7e:a5 July 27 2009 broken DHCP client
0:1d:4f:f5:4d:cd July 26 2008 involved in IP address theft
0:1d:4f:f6:1a:35 August 2 2088 stealing IP address
0:1d:4f:fe:91:46 Nov 21 2008 rogue wireless bridge stealing IP
0:1d:9:45:ab:ac Aug 22 2008 as per IT Policy Advisor mail
0:1d:9:a6:41:dc July 23 2009 blocked as per IT Policy Advisor mail
0:1d:d9:e0:9f:74 July 3 2008 rogue DHCP server
0:1d:d:73:e1:4a August 1 2008 ignores DHCP lease expiration
0:1d:e0:34:ac:b1 June 5 2009 blocked as per IT Policy Advisor mail
0:1d:e0:b2:71:cf Jan 27 2009 rogue wireless bridge stealing IP
0:1e:2a:9:da:a6 September 13 2009 rogue DHCP server
0:1e:3a:98:e6:57 July 24 2008 compromised
0:1e:4c:29:34:bd Dec 16 2007 rogue wireless bridge stealing IP
0:1e:52:72:c1:48 Dec 6 2007 rogue wireless bridge stealing IP
0:1e:52:73:bf:c1 October 29 2009 rogue wireless bridge stealing IP
0:1e:52:74:b5:46 Nov 11 2008 rogue wireless bridge stealing IP
0:1e:52:75:72:bd April 4 2009 rogue wireless bridge stealing IP
0:1e:52:92:72:71 July 15 2009 configured to steal IP address
0:1e:52:c5:9d:55 Dec 6 2008 rogue wireless bridge stealing IP
0:1e:52:e:2b:7d March 8 2009 running multiple DHCP clients on a single network interface
0:1e:58:e1:c:ba June 4 2008 malfunctioning NAT
0:1e:8c:37:33:ad July 23 2009 blocked as per IT Policy Advisor mail
0:1e:8c:d:e4:c6 Sep 25 2008 as per IT Policy Advisor mail
0:1e:c2:26:b0:62 Jan 17 2009 rogue DHCP server
0:1e:c2:31:47:7a Sep 24 2008 stealing IP address
0:1e:c2:5b:8:31 Jan 14 2009 manually configured to steal an IP address
0:1e:c2:6f:e9:5 April 2 2009 stealing IP address
0:1e:c2:a0:9d:45 May 11 2009 rogue wireless bridge stealing IP
0:1e:c2:a3:d1:f4 July 24 2008 using inappropriate IP addresses
0:1e:c2:aa:1a:62 June 24 2008 as per IT Policy Advisor mail
0:1e:c2:b3:63:84 Nov 12 2008 rogue wireless bridge stealing IP
0:1e:c2:b9:6f:f Dec 7 2008 rogue wireless bridge stealing IP
0:1e:c2:d9:a7:38 March 30 2009 rogue DHCP server
0:1e:c2:ef:36:cc Jan 16 2009 rogue DHCP server
0:1e:e5:4b:a2:f3 August 6 2008 rogue DHCP server
0:1e:ec:20:c6:e3 August 8 2009 blocked as per IT Policy Advisor mail
0:1e:ec:82:c6:97 August 7 2008 configure to steal IP address
0:1e:ec:d2:39:45 July 23 2009 blocked as per IT Policy Advisor mail
0:1f:33:2a:b3:47 October 16 2009 malfunctioning NAT
0:1f:3a:12:75:f3 July 15 2008 rogue wireless bridge stealing IP
0:1f:3a:3e:95:28 Aug 22 2008 as per IT Policy Advisor mail
0:1f:3a:70:93:7a August 8 2009 blocked as per IT Policy Advisor mail
0:1f:3a:a:96:41 August 7 2008 compromised
0:1f:3a:a:9b:41 August 7 2008 compromised
0:1f:3b:16:ce:4f August 5 2008 rogue DHCP server
0:1f:3b:46:9b:39 November 2 2008 running multiple DHCP clients on a single network interface
0:1f:3b:7b:2e:ad March 27 2009 rogue DHCP server
0:1f:3b:e:2e:b1 June 18 2009 blocked as per IT Policy Advisor mail
0:1f:3c:1a:a2:37 November 9 2009 blocked as per IT Policy Advisor mail
0:1f:3c:93:59:78 October 19 2009 rogue DHCP server
0:1f:5b:40:ac:50 Jan 6 2009 running multiple DHCP clients on a single network interface
0:1f:5b:68:8c:3f May 16 2009 rogue DHCP server
0:1f:5b:b8:a9:e9 June 24 2008 as per IT Policy Advisor mail
0:1f:5b:b9:cb:e7 October 17 2009 rogue wireless bridge stealing IP
0:1f:5b:ba:c:51 September 8 2009 blocked as per IT Policy Advisor mail
0:1f:5b:be:7e:1b August 19 2009 blocked as per IT Policy Advisor mail
0:1f:5b:c1:a6:c9 May 5 2009 blocked as per IT Policy Advisor mail
0:1f:5b:ed:63:b6 July 24 2008 using inappropriate IP addresses
0:1f:a7:20:d8:13 August 17 2008 ignores DHCP lease expiration
0:1f:de:19:11:9b September 17 2009 erroneous forwarding some broadcast traffic
0:1f:de:19:43:c4 August 3 2009 erroneously forwarding some broadcast traffic
0:1f:de:19:6b:87 August 12 2009 erroneously forwarding some broadcast traffic
0:1f:e1:57:de:a0 August 17 2009 using many inappropriate IP addresses
0:1f:e1:c3:a:17 Nov 30 2008 malfunctioning DHCP client
0:1f:f3:1:e5:5e May 17 2008 malfunctioning DHCP client, rogue network bridge
0:1f:f3:1:e5:5f May 17 2008 malfunctioning DHCP client, rogue network bridge
0:1f:f3:c7:67:dd Oct 10 2008 rogue DHCP server
0:1f:f3:c8:f4:35 Nov 30 2008 rogue DHCP server
0:20:0:34:34:30 Nov 9 2008 broken DHCP client
0:20:78:c8:a5:72 March 27 2009 rogue DHCP server
0:20:78:cf:aa:cd August 5 2008 rogue DHCP server
0:20:a6:4b:fc:f9 June 14 2006 rogue network bridge
0:20:e0:64:2f:d8 Feb 28 2005 compromised
0:20:e0:6a:a9:5f Oct 18 2005 compromised
0:20:e0:8f:86:c7 June 9 2005 running multiple DHCP client instances
0:20:e0:8f:ad:60 Nov 2 2007 rogue DHCP server
0:21:29:f2:ae:4 November 8 2009 rogue DHCP server
0:21:5c:21:e6:cd May 5 2009 blocked as per IT Policy Advisor mail
0:21:5c:84:a1:5 June 1 2009 compromised
0:21:5d:6b:16:b0 April 2 2009 rogue wireless bridge stealing IP
0:21:5d:8:57:ae November 16 2009 blocked as per IT Policy Advisor mail
0:21:5d:a0:8e:fc July 22 2009 rogue wireless bridge stealing IP
0:21:5d:ca:c7:b4 Feb 23 2009 running multiple DHCP clients on a single network interface
0:21:6:88:a1:bd May 11 2009 poorly-behaved DHCP client
0:21:6b:4d:1c:74 Jan 17 2009 rogue DHCP server
0:21:70:d0:22:76 Feb 23 2009 running multiple DHCP clients on a single network interface
0:21:85:7b:64:9c May 26 2009 blocked as per IT Policy Advisor mail
0:21:9b:d7:ff:c1 Nov 30 2008 malfunctioning DHCP client
0:21:9b:dc:de:bd September 12 2009 rogue DHCP server
0:21:d1:1b:5e:5e October 8 2009 ignores DHCP lease expiration
0:21:e9:14:68:b6 Nov 4 2008 running multiple DHCP clients on a single network interface
0:21:e9:1c:c5:5d June 19 2009 rogue DHCP server
0:21:e9:31:a8:72 Jan 9 2009 rogue DHCP server
0:21:e9:45:45:62 August 2 2009 rogue DHCP server
0:21:e9:5d:37:79 Oct 9 2008 rogue DHCP server
0:21:e9:98:17:b8 Nov 23 2008 badly-behaved BootP client
0:21:e9:a0:88:c5 June 18 2009 rogue DHCP server
0:21:e9:a3:37:26 November 5 2009 rogue DHCP server
0:21:e9:de:b9:ce Feb 26 2009 blocked as per IT Policy Advisor mail
0:21:e9:df:8:4f October 14 2009 blocked as per IT Policy Advisor mail
0:22:15:5b:7f:d8 November 12 2009 rogue DHCP server
0:22:41:0:22:45 Nov 4 2008 running multiple DHCP clients on a single network interface
0:22:41:93:79:b6 Oct 2 2008 stealing IP address
0:22:41:a6:e0:d9 October 16 2009 blocked as per IT Policy Advisor mail
0:22:41:bf:1d:f2 May 11 2009 stealing IP address
0:22:41:f7:31:83 September 2 2009 malfunctioning DHCP client
0:22:41:fa:37:77 October 17 2009 rogue wireless bridge stealing IP
0:22:43:47:7e:5f July 28 2009 rogue wireless bridge stealing IP
0:22:fa:9e:3:6a August 6 2009 rogue DHCP server
0:23:12:1f:b7:57 May 27 2009 rogue wireless bridge stealing IP
0:23:12:4:23:22 April 1 2009 blocked as per IT Policy Advisor mail
0:23:12:58:6f:50 Feb 18 2009 blocked as per IT Policy Advisor mail
0:23:12:75:a1:2e Jan 14 2009 rogue DHCP server
0:23:12:95:92:c8 May 27 2009 rogue DHCP server
0:23:12:9a:d2:b6 August 10 2009 rogue DHCP server
0:23:12:a1:ea:e8 Nov 10 2008 running multiple DHCP clients on a single network interface
0:23:12:be:a0:b2 Nov 5 2008 rogue DHCP server
0:23:32:d3:60:1e October 16 2009 malfunctioning NAT software
0:23:4e:12:ee:9c July 23 2009 blocked as per IT Policy Advisor mail
0:23:4e:c2:ab:1c August 18 2009 blocked as per IT Policy Advisor mail
0:23:4e:c9:6a:b4 July 23 2009 blocked as per IT Policy Advisor mail
0:23:6c:19:61:aa Nov 8 2008 rogue DHCP server
0:23:6c:31:a:e9 Jan 23 2009 rogue DHCP server
0:23:6c:4d:77:c3 Feb 20 2009 running multiple DHCP clients on a single network interface
0:23:6c:84:87:19 June 15 2009 blocked as per IT Policy Advisor mail
0:23:6c:87:1:8f October 16 2009 malfunctioning NAT software
0:23:6c:90:41:79 July 7 2009 blocked as per IT Policy Advisor mail
0:23:6c:90:79:6d Feb 11 2009 rogue wireless bridge stealing IP
0:23:7a:3f:24:66 Feb 5 2009 running multiple DHCP clients on a single network interface
0:23:8:4f:69:6d September 3 2009 rogue DHCP server
0:23:8:5e:be:ca July 23 2009 erroneously forwarding some broadcast traffic
0:23:8b:64:a:3c July 23 2009 blocked as per IT Policy Advisor mail
0:23:df:28:96:84 May 18 2009 rogue DHCP server
0:23:df:70:82:a4 March 25 2009 rogue DHCP server
0:23:df:74:da:f9 June 8 2009 rogue DHCP server
0:23:df:9:a7:95 Feb 1 2009 rogue DHCP server
0:23:df:d:96:9c Jan 8 2009 rogue DHCP server
0:24:2b:87:ea:45 July 14 2009 blocked as per IT Policy Advisor mail
0:24:2c:2b:4a:a5 June 16 2009 rogue DHCP server
0:24:36:21:68:ed June 30 2009 rogue DHCP server
0:24:36:51:a6:40 October 3 2009 rogue DHCP server
0:24:36:5a:c9:b9 June 8 2009 rogue DHCP server
0:24:36:64:88:29 May 12 2009 rogue DHCP server
0:24:36:a3:d2:1e October 27 2009 rogue DHCP server
0:25:0:44:7:a4 July 9 2009 rogue wireless bridge stealing IP
0:25:0:44:96:89 October 16 2009 blocked as per IT Policy Advisor mail
0:25:0:7b:ba:ff May 1 2009 rogue DHCP server
0:25:0:88:6b:54 May 28 2009 rogue DHCP server
0:25:0:f6:ec:f0 October 10 2009 blocked as per IT Policy Advisor mail
0:25:4b:67:da:21 May 23 2009 rogue DHCP server
0:25:4b:89:5f:28 September 22 2009 blocked as per IT Policy Advisor mail
0:25:4b:d2:8e:4a August 13 2009 using incorrect IP address
0:25:56:7b:c7:8b November 20 2009 reportedly compromised
0:25:bc:13:04:f1 June 1 2009 persistently stealing IP address
0:25:d0:15:d2:6e October 8 2009 erroneous forwarding some broadcast traffic
0:26:4a:4f:c8:51 October 29 2009 rogue DHCP server
0:26:4a:f1:fc:5a October 11 2009 rogue DHCP server
0:26:8:70:ba:f9 September 19 2009 rogue DHCP server
0:26:8:71:61:75 June 30 2009 stealing TVWNA IP address
0:26:8:8a:4b:8d September 8 2009 rogue DHCP server
0:26:8:de:c:d1 August 13 2009 using incorrect IP address
0:26:b0:b0:cf:ae August 10 2009 rogue DHCP server
0:26:b0:bf:ac:ca November 11 2009 rogue DHCP server
0:26:bb:6a:f9:88 October 25 2009 rogue DHCP server
0:26:bb:6b:6:4 September 26 2009 rogue DHCP server
0:26:bb:e:25:70 November 9 2009 rogue wireless bridge stealing IP
0:2:2d:23:3a:1 May 7 2009 blocked as per IT Policy Advisor mail
0:2:2d:35:b6:b9 June 30 2007 rogue DHCP server
0:2:2d:46:ec:2f July 8 2008 stealing TVWNA IP address
0:2:2d:7c:1e:69 Dec 22 2007 running two DHCP clients on one interface
0:2:2d:81:91:c7 Jan 15 2007 hardware address forgery, stealing TUD IP and Mobile IP
0:2:2d:92:dc:bc Nov 29 2005 compromised and theft of service
0:2:2d:b8:41:ca Nov 12 2003 theft of service
0:2:3f:24:61:4f Nov 8 2005 using IP addresses not belonging to it
0:2:3f:64:6a:aa Apr 1 2005 compromised
0:2:3f:6f:f6:73 Sep 17 2007 compromised
0:2:3f:70:5e:b Oct 18 2005 compromised
0:2:3f:70:b8:a9 Oct 17 2005 compromised
0:2:47:7a:29:7a September 24 2009 erroneous forwarding some broadcast traffic
0:2:6f:62:e:79 October 14 2009 connected via rogue wireless bridge and stealing IP
0:2:78:f0:0:d8 June 4 2006 broken DHCP client
0:2:8a:35:e8:c5 June 9 2005 running multiple DHCP client instances
0:2:8a:57:ba:9f March 21 2009 rogue wireless bridge stealing IP
0:2:8a:57:bc:b2 October 27 2009 overstaying DHCP lease
0:2:8a:94:85:ce July 23 2008 running two DHCP clients on same interface
0:2:96:0:84:b6 Oct 18 2006 compromised
0:2:a5:9d:73:f3 July 16 2007 compromised
0:2:a5:a4:29:7d Feb 21 2005 compromised
0:2:a8:c7:7d:ef September 13 2009 stealing IP address
0:2a:1c:57:f:42 Nov 16 2007 connected via rogue wireless bridge
0:30:13:8a:39:8f Jan 28 2009 compromised
0:30:4:7:d7:56 May 31 2005 broken DHCP client
0:30:65:27:75:3e Dec 4 2006 broken DHCP client
0:30:65:f9:3a:1c July 26 2007 stole IP address
0:30:ab:21:17:cf Jan 10 2007
0:30:bd:f0:c5:28 June 1 2008 ignores DHCP lease time
0:32:fa:dc:8c:bc Dec 22 2007 connected via rogue wireless bridge
0:37:34:59:71:58 Feb 7 2007 connected via rogue wireless bridge
0:39:ad:58:5d:ac Feb 27 2008 connected via rogue wireless bridge
0:3:47:76:57:bb Aug 19 2005 compromised
0:3:47:8d:fb:51 Oct 18 2005 compromised
0:3:47:90:44:c Mar 22 2005 running multiple DHCP client instances
0:3:47:90:51:82 Sep 28 2005 compromised
0:3:47:90:64:cb Feb 24 compromised
0:3:47:90:6a:9a Jan 28 2005 compromised
0:3:47:90:a3:36 Nov 21 2008 compromised
0:3:58:0:0:1 Oct 4 2007 rogue DHCP server
0:3:60:21:18:5d September 16 2009 erroneous forwarding some broadcast traffic
0:3:93:4c:49:24 August 5 2009 erroneously responding to broadcast traffic
0:3:93:a1:5f:80 Oct 18 2007 compromised
0:3:d:13:59:e1 March 16 2009 rogue DHCP server
0:3:ff:56:ba:9f March 21 2009 connected via rogue wireless bridge
0:3:ff:91:ca:5 May 2 2009 connected via rogue wireless bridge
0:3:ff:91:f1:32 August 3 2008 connected via rogue wireless bridge
0:3:ff:97:bb:cc Mar 26 2005 theft of service
0:3:ff:a2:8b:e1 Dec 18 2008 connected via rogue wireless bridge
0:3:ff:c0:f4:4a October 19 2009 connected via rogue wireless bridge
0:3:ff:c3:e2:a0 Oct 6 2007 connected via rogue wireless bridge
0:3:ff:cc:8d:db Nov 5 2007 rogue DHCP server
0:3:ff:d0:8d:bb Nov 8 2007 connected via rogue wireless bridge
0:3c:9f:12:1b:f5 Sep 14 2007 connected via rogue wireless bridge
0:40:10:0:e7:ec Feb 15 2005 compromised
0:40:45:2a:cd:b March 14 2009 using IP address not assigned for its use
0:40:5:25:2b:44 Oct 26 2005 broken IP stack
0:40:5:b9:dd:ef August 1 2007 as per IT Policy Advisor mail
0:40:5a:23:a4:40 September 20 2009 rogue DHCP server
0:40:ca:6e:42:13 June 27 2006 stealing TVWNA IP Addresses
0:41:48:d6:55:f2 March 22 2007 connected via rogue wireless bridge
0:41:74:65:5:2f May 16 2007 connected via rogue wireless bridge
0:41:fe:82:1f:bd Feb 28 2007 connected via rogue wireless bridge
0:43:4f:4e:45:30 Jan 17 2005 stealing TUD IP addresses
0:43:97:c0:42:88 March 26 2009 connected via rogue wireless bridge
0:44:10:9a:cf:a2 August 5 2008 connected via rogue wireless bridge
0:4:1f:9:c8:81 Feb 16 2006 banned from network
0:4:23:49:41:71 Feb 16 2004 theft of service
0:4:23:5d:de:8 Apr 1 2005 compromised
0:4:23:60:b7:d6 Sep 20 2005 compromised
0:4:23:62:ae:c4 June 25 2007 rogue DHCP server
0:4:23:64:4a:9 Oct 18 2007 compromised
0:4:23:67:a2:5d September 15 2009 overstayed DHCP leases on TVWNA
0:4:23:79:9:66 Feb 27 2008 manually configured to steal IP address
0:4:23:8d:df:f3 April 30 2008 stole IP address
0:4:23:93:0:f7 Aug 28 2006 rogue network bridge
0:4:23:a0:da:3c Nov 7 2008 compromised
0:4:35:28:35:4b September 21 2009 erroneous forwarding some broadcast traffic
0:4:5a:29:76:17 Sep 9 2007 rogue DHCP server
0:4:5a:55:dc:7c May 11 2004 compromised
0:4:5a:6d:e2:cc June 10 2004 source of attack
0:4:5a:9b:74:ea Jan 26 2005 compromised
0:4:5a:a2:61:a7 Aug 5 2005 compromised
0:4:5a:db:b5:a1 Oct 7 2006 rogue DHCP server
0:4:5a:db:b5:a2 Oct 7 2006 rogue DHCP server
0:4:66:d7:44:1c September 22 2009 erroneous forwarding some broadcast traffic
0:4:6:56:d0:4e Sep 25 2008 connected via rogue wireless bridge
0:4:76:34:f4:36 Nov 10 2005 ignores DHCP lease time
0:4:76:3f:39:76 August 20 2008 as per IT Policy Advisor mail
0:4:e2:1b:ce:c7 Dec 12 2003 broken DHCP client
0:4b:fd:f7:8e:92 August 1 2007 connected via rogue wireless bridge
0:50:4:6f:85:80 Feb 21 2007 compromised
0:50:4:a5:71:99 Jan 29 2007 compromised
0:50:4:df:2d:67 July 30 2003 theft of service
0:50:ba:60:79:6b Jan 28 2005 compromised
0:50:ba:cc:1f:63 May 1 2009 source of malicious DNS traffic
0:50:bf:ab:6f:c9 October 16 2009 compromised
0:50:da:18:61:12 April 2 2007 compromised
0:50:da:21:50:48 Aug 12 2005 compromised
0:50:da:6a:62:2 Oct 18 2006 compromised
0:50:da:eb:f0:dd Oct 12 2005 compromised
0:50:f2:79:ce:96 Mar 27 2003 broken DHCP client
0:53:99:46:4a:a1 Oct 8 2006 connected via rogue wireless bridge
0:58:92:5:b7:2c April 18 2007 connected via rogue wireless bridge
0:59:9d:54:e2:d8 June 4 2007 connected via rogue wireless bridge
0:5:1b:0:4b:49 Sep 29 2006 compromised
0:5:30:45:72:4f September 11 2009 erroneously forwarding some broadcast traffic
0:5:30:55:91:5f September 8 2009 erroneously forwarding some broadcast traffic
0:5:3c:3:b3:aa April 24 2007 compromised
0:5:3c:3:b4:bb Sep 28 2005 compromised
0:5:3c:3:d3:9c Nov 17 2005 compromised
0:5:3c:4:c6:34 July 22 2008 malfunctioning DHCP client
0:5:3c:6:4e:1 Oct 1 2005 compromised
0:5:3c:6:dd:2e June 29 2005 compromised
0:5:3c:7:bc:62 Jan 28 2005 compromised
0:5:4e:47:ad:80 Apr 14 2005 disrupted campus network
0:5:4e:4a:2e:30 May 10 2006 forging DHCP chaddr
0:60:1d:f0:58:66 Mar 25 2005 broken DHCP client
0:60:97:c7:c7:38 Nov 28 2005 compromised
0:60:b3:2d:cf:b3 March 20 2008 broken DHCP client
0:60:b3:67:42:e6 Oct 9 2008 compromised
0:66:6b:61:f4:21 August 10 2007 connected via rogue wireless bridge
0:68:b1:c4:e0:b Dec 14 2006 connected via rogue wireless bridge
0:68:bd:ce:a4:8f Jan 25 2007 connected via rogue wireless bridge
0:6:25:11:b1:83 July 20 2003 wireless ethernet bridge
0:6:25:3:dd:68 Feb 9 2005 theft of service
0:6:25:aa:6a:21 Aug 25 2005 compromised
0:6:5b:39:49:fe Jan 4 2007 compromised
0:6:5b:39:49:ff Jan 4 2007 compromised
0:6:5b:79:b6:25 March 15 2007 compromised
0:6:5b:89:19:a August 19 2009 compromised
0:6:5b:bb:38:c0 Sep 27 2005 compromised
0:6:5b:c2:48:21 Jan 4 2005 compromised
0:6:5b:d4:12:98 Feb 21 2007 compromised
0:6:5b:de:76:5b June 11 2008 compromised
0:6:f4:5:1d:34 June 19 2007 trying to steal DHCP offers
0:71:e1:31:ad:6e June 2 2008 connected via rogue wireless bridge
0:7:68:0:e0:46 March 15 2007 stole IP address
0:7:b8:0:19:6 July 29 2004 source of attack
0:7:e0:28:34:eb Dec 12 2007 broken DHCP client
0:7:e9:6f:55:8e Nov 30 2004 compromised
0:7:e9:7b:a7:a5 July 1 2008 compromised
0:7:e9:94:ea:cd Aug 7 2003 ignores DHCP lease time
0:7:e9:d9:12:88 May 9 2007 as per IT Policy Advisor mail
0:80:45:45:8:e2 Aug 28 2006 rogue network bridge
0:80:ad:77:8:4b Oct 24 2005 compromised
0:80:c6:f9:78:6f Feb 21 2005 compromised
0:8:2:7d:d1:f7 October 16 2009 compromised
0:8:2:e7:82:bc August 17 2008 rogue DHCP server
0:8:2:f3:b5:8b October 11 2006 rogue network bridge
0:8:2:f3:b5:8c June 14 2006 rogue network bridge
0:8:74:12:6f:f July 26 2006 compromised
0:8:74:3a:8d:ab Mar 25 2005 broken DHCP client
0:8:74:4:6f:e9 July 19 2005 compromised
0:8:a1:11:69:c5 July 1 2004 compromised
0:8:a1:22:d3:ed Oct 18 2006 compromised
0:8:d:76:7:53 Jan 15 2007 hardware address forgery, stealing TUD IP and Mobile IP
0:8:d:98:16:51 June 4 2009 malfunctioning NAT
0:8:d:a3:40:f1 August 12 2009 using incorrect IP address
0:90:27:7c:e:2a Feb 5 2004 compromised
0:90:27:de:2b:9d Dec 17 2007 compromised
0:90:4b:16:b3:94 April 13 2006 misconfigured DHCP client
0:90:4b:2c:ad:50 Feb 20 2007 broken DHCP client
0:90:4b:2d:5e:98 Dec 7 2007 rogue DHCP server
0:90:4b:36:34:16 Oct 8 2004 broken DHCP client, steals IP
0:90:4b:3b:7e:1f April 2 2007 running multiple DHCP clients on one interface
0:90:4b:73:5f:93 Dec 26 2007 stole IP address
0:90:4b:a8:cc:9b Nov 16 2007 as per IT Policy Advisor mail
0:90:4b:b2:d8:d0 Oct 18 2007 compromised
0:90:4b:b3:85:3f Oct 19 2007 compromised
0:90:4b:be:88:6f Sep 18 2007 rogue DHCP server
0:90:4b:d4:51:d3 July 15 2008 as per IT Policy Advisor mail
0:90:4b:d6:77:1a June 19 2007 running two simultaneous DHCP clients on one network interface
0:90:4b:db:5b:d3 March 27 2009 rogue DHCP server
0:90:4b:f1:f9:50 June 17 2008 as per IT Policy Advisor mail
0:90:4b:f3:9a:ae April 5 2007 malfunctioninng DHCP client
0:90:4b:f8:9:37 April 22 2008 as per IT Policy Advisor mail
0:90:7f:33:1b:e1 April 20 2009 blocked as per IT Policy Advisor mail
0:90:96:c2:e2:a0 Oct 6 2007 rogue wireless bridge stealing IP
0:90:96:ce:d0:6a October 8 2009 rogue DHCP server
0:90:9e:7c:cc:5e Oct 31 2006 connected via rogue wireless bridge
0:90:c9:1:72:80 Dec 7 2008 rogue wireless bridge stealing IP
0:90:f5:e:6e:78 Jan 19 2006 compromised
0:92:58:9f:c4:6b May 2 2008 connected via rogue wireless bridge
0:93:ef:bd:d7:82 Dec 1 2006 connected via rogue wireless bridge
0:96:9c:4:3f:7d April 19 2007 connected via rogue wireless bridge
0:97:c0:dd:57:db March 4 2008 connected via rogue wireless bridge
0:99:f:16:83:73 Dec 11 2006 connected via rogue wireless bridge
0:9:2d:ea:41:a0 Dec 10 2007 broken DHCP client
0:9:5b:3:5:e July 6 2006 broken DHCP client
0:9:5b:d1:8:19 June 14 2004 broken DHCP client, ignores lease expiration time
0:9:5b:ff:8b:a Oct 27 2005 broken IP stack
0:9:5b:ff:8b:b Oct 27 2005 broken IP stack
0:9:6b:10:a1:70 Jan 14 2005 compromised
0:9:6b:2:47:4e Aug 24 2006 malfunctioning DHCP client
0:9:6b:2:a5:f5 Oct 1 2005 compromised
0:9:6b:2d:fc:c2 Sep 20 2005 compromised
0:9:6b:42:1f:92 Jan 28 2005 compromised
0:9:6b:50:3b:3a Oct 11 2005 compromised
0:9:6b:90:55:1e Sep 15 2004 compromised
0:9:6b:90:5a:3f April 24 2007 compromised
0:9:6b:90:5b:7b Sep 28 2005 compromised
0:9:6b:90:c6:5f Oct 10 2008 broken DHCP client
0:9:6b:93:96:41 May 30 2003 disrupted Reunions 2003 Network Service due to SQL Slammer Worm
0:9:6b:a0:25:24 June 29 2005 compromised
0:9:6b:e0:0:3f Nov 17 2005 compromised
0:9:6b:e0:80:b3 July 22 2008 malfunctioning DHCP client
0:9a:90:92:de:8 Jan 15 2007 hardware address forgery, stealing TUD IP and Mobile IP
0:9f:51:f3:19:e5 Feb 15 2007 connected via rogue wireless bridge
0:a0:42:a0:0:c October 16 2009 blocked as per IT Policy Advisor mail
0:a0:c9:85:6a:3e March 15 2007 compromised
0:a0:c9:8d:66:73 Jan 26 2006 compromised
0:a0:c9:9a:b1:3a May 5 2004 compromised
0:a0:cc:e4:7f:1a June 1 2006 compromised
0:a0:d1:23:1d:f3 Oct 22 2007
0:a0:d1:8b:d2:51 July 30 2008 source of erroneous DHCP traffic
0:a0:d1:b6:9:37 July 26 2007 misconfigured DHCP client
0:a:95:b3:e0:4c August 7 2008 forwarding broadcast traffic
0:a:95:e6:81:d0 May 18 2005 compromised
0:a:95:e9:cc:4c Oct 18 2005 broken DHCP client
0:a:95:ed:4:c2 August 22 2007 configured to steal IP address
0:ad:2e:64:50:11 Nov 3 2006 connected via rogue wireless bridge
0:b0:1e:4e:0:6d Oct 2 2006 connected via rogue wireless bridge
0:b0:d0:1d:3d:87 Sep 27 2004 compromised
0:b0:d0:1d:87:1b March 9 2005 compromised
0:b0:d0:42:96:b8 Nov 29 2004 compromised
0:b0:d0:42:ba:57 March 15 2007 compromised
0:b0:d0:95:23:66 May 17 2005 compromised
0:b0:d0:95:23:91 May 25 2004 compromised
0:b0:d0:c3:da:aa Jan 26 2006 compromised
0:b0:d0:c4:a7:31 Mar 22 2005 compromised
0:b0:d0:c4:a7:e Feb 21 2006 compromised
0:b0:d0:c7:3b:73 April 20 2006 stealing IP address
0:b0:d0:cc:3a:f0 Sep 26 2006 compromised
0:b0:d0:da:7f:1b Feb 12 2007 compromised
0:b0:d0:e4:a3:66 March 6 2006 compromised
0:b0:d0:f2:f8:be Feb 28 2008 rogue DHCP server
0:b:13:2d:e1:c9 Nov 30 2006 connected via rogue wireless bridge
0:b:5d:4f:a0:aa Oct 21 2007
0:b:7d:10:60:42 April 22 2008 rogue DHCP server
0:b:7d:20:2e:4f Dec 2 2007 rogue DHCP server
0:b:cd:a5:a:dc June 8 2006 compromised
0:b:cd:a7:9:c4 April 2 2008 compromised
0:b:cd:e8:8a:b9 Oct 18 2007 compromised
0:b:db:95:9a:d0 August 1 2007 compromised
0:b:db:9a:1:23 Aug 5 2005 broken DHCP client
0:b:db:a6:29:32 June 8 2007 rogue DHCP server
0:b:db:a7:bc:93 Nov 1 2004 compromised
0:b:db:bf:5c:4b August 1 2007 as per IT Policy Advisor mail
0:b:db:d8:b6:bf Feb 20 2007 broken DHCP client
0:b:db:dd:9e:8a Oct 27 2004 compromised
0:b:db:e7:2b:78 Sep 10 2005 compromised
0:c0:4f:18:33:65 Jan 26 2006 compromised
0:c0:4f:1c:17:78 March 10 2005 compromised
0:c0:4f:22:18:e3 Mar 23 2005 compromised
0:c0:4f:22:18:ff June 7 2005 compromised
0:c0:4f:22:a1:18 Nov 11 2005 compromised
0:c0:4f:2c:d5:47 March 10 2005 compromised
0:c0:4f:33:c7:d8 August 24 2009 compromised
0:c0:4f:46:79:2c Feb 2 2007 compromised
0:c0:4f:47:4d:c7 Nov 1 2004 compromised
0:c0:4f:65:74:83 Dec 4 2006 compromised
0:c0:4f:6:ad:2b Nov 16 2005 compromised
0:c0:4f:7f:9f:93 April 24 2007 banned from network
0:c0:4f:8d:30:2f July 6 2006 compromised
0:c0:4f:8d:3e:fe Apr 30 2004 compromised
0:c0:4f:8e:ba:5b Feb 21 2007 compromised
0:c0:4f:98:6a:ec Dec 16 2005 compromised
0:c0:4f:98:70:f3 May 26 2005 compromised
0:c0:4f:b0:12:d2 Feb 25 2008 forging DHCP chaddr value
0:c0:4f:b0:14:b Aug 5 2005 compromised
0:c0:4f:d:34:5d July 25 2006 compromised
0:c0:9f:34:84:ad Oct 1 2007 misconfigured DHCP client
0:c0:9f:ab:e8:5e April 5 2007 malfunctioning DHCP client
0:c0:9f:b:42:2e Sep 9 2004 compromised
0:c0:9f:cc:dc:6 Oct 25 2008 running multiple DHCP clients on a single network interface
0:c0:9f:ef:dc:52 July 24 2008 excessive DNS traffic
0:c0:9f:f2:37:b Nov 16 2007 as per IT Policy Advisor mail
0:c0:a8:8c:a4:8c Aug 19 2005 compromised
0:c0:a8:ae:20:1f November 5 2009 broken DHCP client
0:c0:a8:be:c6:75 May 5 2008 as per IT Policy Advisor mail
0:c0:b6:2:b5:9a May 19 2006 compromised
0:c0:b7:80:27:8c Feb 13 2007 broken DHCP client
0:c0:b7:80:97:e1 Feb 13 2007 broken DHCP client
0:c0:ca:19:1b:f3 June 12 2006 broken NAT
0:c0:ca:1e:54:22 Nov 7 2008 rogue DHCP server
0:c:29:1d:c:ce May 21 2009 connected via rogue wireless bridge
0:c:29:29:c2:c2 Sep 6 2008 connected via rogue wireless bridge
0:c:29:2b:73:a7 Oct 27 2007 connected via rogue wireless bridge
0:c:29:2c:8e:bf July 28 2009 connected via rogue wireless bridge
0:c:29:36:fd:1a Dec 7 2008 connected via rogue wireless bridge
0:c:29:44:b5:db March 19 2008 connected via rogue wireless bridge
0:c:29:4b:fe:c4 Feb 24 2007 connected via rogue wireless bridge
0:c:29:4f:5c:6f Feb 19 2008 connected via rogue wireless bridge
0:c:29:52:f3:58 Nov 12 2008 connected via rogue wireless bridge
0:c:29:5e:e7:3b November 4 2008 connected via rogue wireless bridge
0:c:29:69:9f:db Oct 14 2008 connected via rogue wireless bridge
0:c:29:6c:a9:ab July 22 2009 connected via rogue wireless bridge
0:c:29:70:5a:7e June 1 2009 connected via rogue wireless bridge
0:c:29:82:17:de August 3 2008 connected via rogue wireless bridge
0:c:29:a3:af:b9 April 4 2009 connected via rogue wireless bridge
0:c:29:ae:e:a1 Dec 16 2007 connected via rogue wireless bridge
0:c:29:bb:79:9b Jan 27 2009 connected via rogue wireless bridge
0:c:29:bd:44:af August 3 2008 connected via rogue wireless bridge
0:c:29:c5:98:8 Feb 8 2008 connected via rogue wireless bridge
0:c:29:c8:14:ca Dec 8 2007 connected via rogue wireless bridge
0:c:29:c:aa:4a April 2 2009 connected via rogue wireless bridge
0:c:29:d6:94:f1 Oct 4 2006 connected via rogue wireless bridge
0:c:29:d6:d9:49 Feb 11 2009 connected via rogue wireless bridge
0:c:29:d:81:e4 Jan 21 2009 connected via rogue wireless bridge
0:c:29:de:88:41 Sep 25 2007 connected via rogue wireless bridge
0:c:29:df:a7:df August 13 2008 connected via rogue wireless bridge
0:c:29:e0:d2:8c Feb 17 2008 connected via rogue wireless bridge
0:c:29:e0:f:2 August 13 2008 connected via rogue wireless bridge
0:c:29:e4:43:ca May 27 2009 connected via rogue wireless bridge
0:c:29:e6:73:80 November 9 2009 connected via rogue wireless bridge
0:c:29:ea:1:f4 Feb 20 2008 connected via rogue wireless bridge
0:c:29:f9:b9:32 June 17 2009 connected via rogue wireless bridge
0:c:29:fa:ea:dc July 15 2008 connected via rogue wireless bridge
0:c:41:22:7a:df Oct 5 2004 compromised
0:c:41:26:84:4b Sep 14 2004 compromised
0:c:41:70:99:29 Aug 7 2006 theft of service
0:c:41:b5:b8:ce July 28 2006 compromised
0:c:6e:50:c:b1 Sep 18 2006 compromised
0:c:f1:14:f7:28 Aug 23 2006 theft of service
0:c:f1:1c:c2:6c July 8 2007 running two simultaneous DHCP clients
0:c:f1:1f:48:49 August 12 2009 using incorrect IP address
0:c:f1:27:e4:5 Jan 9 2008 running two DHCP clients on one interface
0:c:f1:36:50:d0 September 19 2009 rogue DHCP server
0:c:f1:3:da:73 Oct 1 2007 misconfigured DHCP client
0:c:f1:41:9b:30 August 17 2008 rogue DHCP server
0:c:f1:49:3a:e4 October 16 2009 broken DHCP client
0:c:f1:49:99:67 August 5 2008 as per IT Policy Advisor mail
0:c:f1:92:3d:fc Dec 15 2005 compromised
0:c:f1:a7:a:56 May 31 2007 compromised
0:cf:30:36:39:36 Dec 7 2008 connected via rogue wireless bridge
0:d0:59:44:b3:e0 Feb 26 200 theft of service
0:d0:59:61:49:b2 Mar 1 2004 compromised
0:d0:b5:16:ed:e7 July 8 2008 connected via rogue wireless bridge
0:d0:c9:9d:17:ce Feb 28 2008 compromised
0:d2:7d:6e:85:67 Nov 15 2006 connected via rogue wireless bridge
0:d5:24:2b:6e:7d Sep 11 2007 connected via rogue wireless bridge
0:d:4b:36:95:64 Oct 16 2008 malfunctioning DHCP client
0:d:4b:36:95:65 Oct 16 2008 malfunctioning DHCP client
0:d:4b:3a:b:ab Feb 12 2009 broken DHCP client
0:d:4b:3d:7f:cc October 16 2009 defective DHCP client
0:d:4b:3d:7f:cd October 16 2009 defective DHCP client
0:d:56:30:a6:b5 June 4 2008 rogue DHCP server
0:d:56:35:23:27 Nov 29 2005 compromised and theft of service
0:d:56:35:7a:39 July 18 2007 ignores DHCP lease time
0:d:56:35:8e:2e July 12 2004 banned from network
0:d:56:5e:26:c4 May 30 2007 compromised
0:d:56:dc:e:de Aug 23 2006 theft of service
0:d:56:e0:dd:ea Oct 18 2007 compromised
0:d:60:74:f1:37 September 25 2009 overstayed DHCP lease
0:d:60:8d:47:4f Mar 25 2005 broken DHCP client
0:d:93:2d:ae:c4 July 2 2007 malfunctioning DHCP client
0:d:93:40:aa:6e Aug 22 2005 disruptive device
0:d:93:60:a2:7e March 9 2007 connected via rogue wireless bridge
0:d:93:81:d:4e August 7 2008 other interface of device forwarding broadcast traffic
0:d:93:84:45:b2 July 2 2007 malfunctioning DHCP client
0:d:93:c2:1b:70 Feb 16 2005 theft of service
0:d:9d:1d:a8:30 Oct 12 2008 manually configured to steal IP address
0:d:9d:84:6c:94 Jan 18 2005 compromised
0:d:b:c:2f:6f Feb 2 2006 stole IP address
0:e0:0:58:ca:2e Aug 12 2005 compromised
0:e0:0:88:1e:8f October 2 2009 compromised
0:e0:0:c3:19:4a Oct 18 2006 compromised
0:e0:11:4:b3:3a April 14 2008 malfunctioning NAT
0:e0:11:5:c4:76 Sep 14 2007 rogue DHCP server
0:e0:18:25:c0:4d Nov 22 2004 compromised
0:e0:18:2a:a1:0 Mar 24 2005 compromised
0:e0:18:2d:4f:d3 Oct 19 2006 compromised
0:e0:29:6f:9a:63 Nov 29 2007 compromised
0:e0:29:9e:e4:5d March 7 2006 broken NAT, banned
0:e0:81:21:3a:7f Dec 4 2008 broken DHCP client
0:e0:98:71:8d:c4 Mar 27 2003 broken DHCP client
0:e0:98:8e:ea:44 Jan 28 2005 banned from network
0:e0:b8:90:59:4f August 7 2008 as per IT Policy Advisor mail
0:e0:dd:28:9c:a2 April 28 2009 connected via rogue wireless bridge
0:e5:4b:22:8:1f Feb 14 2007 connected via rogue wireless bridge
0:e6:f9:da:54:3f Jan 23 2008 connected via rogue wireless bridge
0:e:2c:0:b8:60 September 13 2009 ignores DHCP lease times
0:e:2c:1:1b:80 September 24 2009 ignores DHCP lease time
0:e:2e:3e:cf:c5 Feb 26 200 theft of service
0:e:35:15:e6:b Sep 18 2007 denial of service, theft of IP addresses, impersonation of other customers
0:e:35:22:29:b8 Jan 17 2009 blocked as per IT Policy Advisor mail
0:e:35:38:0:f4 September 25 2009 overstayed DHCP lease
0:e:35:41:72:68 Oct 21 2007
0:e:35:53:88:1d Jan 12 2009 blocked as per IT Policy Advisor mail
0:e:35:7b:c9:67 July 30 2009 compromised
0:e:35:9:83:f3 October 13 2009 blocked as per IT Policy Advisor mail
0:e:35:ab:b8:e2 August 11 2007 rogue DHCP server
0:e:35:b:a7:6e Nov 8 2005 using IP addresses not belonging to it
0:e:35:be:22:20 Aug 22 2008 hardware address forgery
0:e:35:c7:38:62 Aug 31 2005 rogue DHCP server
0:e:35:d:84:a9 Oct 12 2008 rogue DHCP server
0:e:35:f0:9c:fb Aug 22 2008 using inappropriate IP addresses
0:e:7b:20:59:de June 22 2009 rogue DHCP server
0:e:8:bc:12:71 Dec 5 2007 stealing IP address
0:e:9b:d6:e8:95 March 24 2008 as per IT Policy Advisor mail
0:ea:86:1c:1a:89 Nov 5 2008 connected via rogue wireless bridge
0:ea:fc:77:10:64 May 13 2007 connected via rogue wireless bridge
0:ed:c7:15:a:dc Nov 30 2006 connected via rogue wireless bridge
0:f6:f1:c:65:59 May 26 2007 connected via rogue wireless bridge
0:f:1f:20:b3:f1 August 7 2008 as per IT Policy Advisor mail
0:f:1f:23:7f:23 Aug 5 2005 compromised
0:f:1f:74:f0:d2 August 20 2008 excessive DHCPINFORM traffic
0:f:1f:a1:df:74 Oct 19 2007 compromised
0:f:1f:bd:6e:d1 August 5 2008 as per IT Policy Advisor mail
0:f:1f:c0:60:bf Oct 9 2006 stealing router's IP address
0:f:20:29:bc:3b August 7 2008 configured to steal an IP address
0:f:3d:4b:3f:a3 June 29 2005 theft of service, broken IP stack
0:f:3d:4b:3f:aa June 29 2005 theft of service, broken IP stack
0:f:3d:4d:3c:9 Aug 4 2006 running two simultaneous DHCP clients
0:f:66:13:90:a4 Dec 12 2008 persistently overstays DHCP lease
0:f:66:a4:c4:3f Sep 10 2008 rogue DHCP server
0:f:b0:3a:8d:d8 Nov 28 2005 theft of service
0:f:b0:8:ec:3 Nov 16 2007 as per IT Policy Advisor mail
0:f:b0:c3:6c:87 Aug 2 2006 broken DHCP client
0:f:b0:e3:17:d2 Nov 7 2008 rogue DHCP server
0:f:b5:8:e6:a9 March 15 2007 compromised
0:f:b5:97:dd:6e May 9 2007 as per IT Policy Advisor mail
0:f:b5:bc:c0:7 March 9 2009 incorrectly responding to IP broadcast traffic
0:f:b5:d5:d9:f2 Sep 2 2008 rogue DHCP server
0:f:b5:eb:2f:b8 May 15 2006 rogue network bridge, also stealing DHCP offers
0:f:db:f9:56:2d August 18 2009 rogue DHCP server
16:92:54:13:61:72 August 19 2009 blocked as per IT Policy Advisor mail
2:1a:4d:46:27:11 March 29 2008 hardware address forgery
2:80:45:45:8:e2 Sep 27 2006 rogue network bridge
34:4f:2:ee:58:30 Jan 17 2009 blocked as per IT Policy Advisor mail
44:2:93:68:83:e5 July 4 2006 rogue DHCP server
4:62:65:87:3e:f9 June 20 2006 rogue DHCP server
7a:79:5:aa:59:c4 May 31 2007 forged address
80:0:60:f:e8:0 May 31 2007 forged address
8:0:1f:b1:24:ba Feb 26 200 theft of service
8:0:20:88:f7:55 Feb 21 2007 compromised
8:0:20:fd:6a:86 Apr 15 2005 compromised
8:0:46:2a:89:87 May 15 2006 rogue network bridge, also stealing DHCP offers
8:0:46:40:c3:fc Dec 1 2006 rogue network bridge
8:0:46:59:dd:fa Sep 18 2006 compromised
8:0:46:99:4c:42 October 27 2009 overstaying DHCP lease
8:0:46:aa:54:ea July 23 2008 running two DHCP clients on same interface
8:0:46:cb:4e:78 Oct 13 2008 malfunctioning NAT
8:0:46:e4:ce:6 Sep 18 2007 denial of service, theft of IP addresses, impersonation of other customers
8:0:7:bf:47:f7 Jan 22 2004 broken DHCP client
90:e6:ba:19:fe:2f November 22 2009 rogue DHCP server
a:2b:3c:4f:0:23 July 26 2008 stealing IP addresses
c2:97:a4:ee:52:5b Dec 1 2006 rogue network bridge


Notes

Client's Hardware Address
This is the hardware (e.g. Ethernet or Wireless) address of the client's device.

Date
This is the date the client was declared ineligible.

Reason Ineligible
When present, this may contain a brief description of the reason the client was declared ineligible.

A hardware address may appear simultaneously in the tables above and in the Current Visitor IP Address Assignments. This can happen when the device's last DHCP lease is still valid (it has not yet expired and the client hasn' t tried to renew it yet). After the lease expires (or the client tries to renew it), the client will not receive VIP service, and will no longer appear in the list of current VIP Address assignments.


A service of OIT Network Systems
The Office of Information Technology,
Princeton University