OIT Network Systems

Devices Blocked from OIT Wireless Service

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

For information about the service, see OIT Wireless Service.

The same hardware address may appear more than once, because it may be blocked in multiple ways, or for multiple reasons.

Contents

  1. Devices Declared Completely Ineligible for OIT Wireless Service
  2. Devices Declared Partially Ineligible for OIT Wireless Service
  3. Other Devices Ineligible for All Wireless Services

This document is updated several times each day; it was last updated at Mon Nov 23 12:51:49 2009.


Devices Declared Completely Ineligible for OIT Wireless Service

The devices listed below have been declared completely ineligible for OIT Wireless Service. (By "completely ineligible", we mean "from all OIT Wireless Access Points." That's as opposed to being declared "partially ineligible"; i.e. from only certain OIT Wireless Access Points.)

Hardware Address Hostname Date Reason Ineligible
0:1d:7e:9a:58:b7 pha-9d4clf1.princeton.org
0:1e:4f:bd:e1:23 pha-9d4clf1.princeton.org

Devices Declared Partially Ineligible for OIT Wireless Service

The devices listed below have been declared partially ineligible for OIT Wireless Service. (By "partially ineligible", we mean "from certain OIT Wireless Access Points." That's as opposed to being declared "completely ineligible"; i.e. from all OIT Wireless Access Points.)

Hardware Address Hostname Date Access Points Reason Ineligible
0:11:2f:50:bd:e nlmpc airo-0830, airo-0835
0:11:43:3e:d0:5f mol-cs-laptop7 airo-0392, airo-0435
0:11:43:50:2a:84 ath-2p27871 airo-0796
0:12:f0:32:bb:52 ath-2p27871 airo-0796
0:16:6f:56:f7:b2 hou-3sha5dyaqs airo-0999
0:1d:ba:24:d6:6c rel-abardelm airo-0667
0:21:5d:7:b3:6c rel-abardelm airo-0667
0:2:3f:fd:6:d6 hou-3sha5dyaqs airo-0999
0:30:65:d:e8:68 mol-teaching-ibook4 airo-0084
0:a:95:e2:ba:ba mol-teaching-ibook4 airo-0084
0:c:41:b6:c6:a3 Feb 26 2004 airo-0491, airo-0810,airo-0131 malfunctioning network software or rogue wireless bridge
0:e:35:44:5a:64 nlmpc airo-0830, airo-0835
0:e:35:bf:f8:47 mol-cs-laptop7 airo-0392, airo-0435

Other Devices Ineligible for All Wireless Services

The devices listed below are ineligible for OIT Wireless Service because they have been declared ineligible for all wireless services provided by OIT.

Hardware Address Hostname Date Reason Ineligible
0:0:0:0:0:a pu116088.student
0:0:0:60:4a:27 Oct 18 2007 compromised
0:0:39:56:3a:e9 July 6 2005 compromised
0:0:39:73:7:8d Nov 14 2005 compromised
0:0:aa:c2:6c:1f Feb 27 2009 ignores DHCP lease time
0:0:d8:60:ff:55 August 1 2008 running multiple DHCP clients on one interface
0:0:e2:a2:3a:a9 pu107272.student
0:0:f0:6e:eb:8d pu109106.student
0:10:5a:aa:9d:e7 phy-atchouvi1
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:16:84:1d wos-visit-2
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:8b:e4:71 freneau
0:10:c6:ce:4d:92 pu104653.student
0:11:11:2a:1f:d5 Oct 19 2006
0:11:24:3a:b6:56 art-072805a
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:9f:12:fe July 18 2007 malfunctioning DHCP client
0:11:24:a4:58:7d November 18 2009 malfunctioning DHCP client
0:11:24:a4:d6:1e hva-g85351s3ru0
0:11:24:be:8:dd art-072805a
0:11:24:c4:56:73 July 3 2008 as per IT Policy Advisor mail
0:11:24:cc:a1:6 hva-g85351s3ru0
0:11:24:da:d4:52 November 18 2009 malfunctioning DHCP client
0:11:24:f:ed:8e hva-g85351s3ru0
0:11:25:2f:bb:6 pu117657.student
0:11:2f:28:48:e3 July 28 2006 compromised
0:11:2f:4f:b5:b9 Oct 14 2005 compromised
0:11:2f:db:17:71 phy-abhay
0:11:43:5f:3b:58 Jan 7 2007 stealing TUD IP
0:11:43:61:4c:38 pu110965.student
0:11:43:6d:51:5d pu117130.student
0:11:43:7a:9c:e2 Dec 10 2007 compromised
0:11:43:d9:5a:b3 mol-wingreen1
0:11:50:70:f1:98 August 7 2008 as per IT Policy Advisor mail
0:11:50:7:e2:66 Sep 11 2006 stealing IP address
0:11:85:c4:dd:b2 pu116088.student
0:11:95:69:15:a6 Aug 15 2006 rogue DHCP server
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: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:c5:41:40 September 23 2009 wireless bridge used by customer to extend University wireless services
0:12:3:c2:e5:b6 August 10 2007 configured to steal IP address
0:12:3f:0:de:d3 pu117573.student
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:52:25:2c chm-sooslab-1
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:37:54:f6 Jan 10 2007 compromised
0:12:f0:7a:b6:5b Dec 10 2007 compromised
0:12:f0:83:55:e6 pu117573.student
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: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:2f:6:ea pu106109.student
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:47:94:e1 gen-jasmine-laptop
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:2:cc:92:fe rossinina
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:a9:a5:1e:86 chm-vavilala
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:5:22:83 commnet2.ee
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:17:63:69 pu110965.student
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:e8:e3:89 dms-stevewar
0:13:e8:f6:bc:d1 Dec 18 2008 rogue wireless bridge stealing IP
0:13:f7:4a:1f:a3 psy-chlds01
0:13:f7:64:cc:55 pu114909.student
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:f2:57:ac pu106109.student
0:14:22:f6:1:cb Oct 18 2007 as per IT Policy Advisor mail
0:14:51:ed:2a:da Aug 2 2006 wireless bridge, stole IP address, and broken DHCP client
0:14:51:ef:ea:8c August 13 2008 rogue wireless bridge stealing IP
0:14:6c:1c:a8:45 phy-nat-eplab
0:14:a4:26:9e:fa pu104653.student
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:82:3c:12 May 4 2006 rogue DHCP server
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:d:bb:14 July 16 1006 rogue DHCP server
0:14:bf:e3:4d:1a July 18 2009 rogue wireless bridge stealing IP
0:14:fd:12:7a:28 hylabhome
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: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:15:f2:5a:10:94 pu105114.student
0:16:36:53:c1:32 pu117042.student
0:16:36:7e:76:ce pu111705.student
0:16:36:87:e9:68 August 1 2007 malfunctioning DHCP client software
0:16:36:95:64:7e pu117282.student
0:16:36:b6:ef:2e art-102209a
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:72:2e:20 pu117042.student
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:6f:cc:95:d5 crestronair
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:9c:1c:2c hdmac-georges
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:bc:94:22 gen-sepmacbook
0:16:cb:bf:a:40 Feb 7 2007 rogue wireless bridge stealing IP
0:16:cb:cb:c5:bb gen-sepmacbook
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: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:d3:9d:3b:97 pu119962.student
0:16:d4:96:9a:16 Sep 25 2008 sending erroneous DHCP traffic
0:16:d4:c:b:90 Sep 20 2006
0:16:d4:c:b:90 gen-jasmine-laptop
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:42:3d:45:29 pu117740.student
0:17:a4:f0:ce:78 chm-qtof-25f
0:17:ee:8:a3:dc Feb 26 2008 banned from the network
0:17:ee:8:a3:dd Feb 26 2008 banned from the network
0:17:f2:2b:4b:ce pu102488.student
0:17:f2:32:10:e6 August 24 2009 blocked as per IT Policy Advisor mail
0:17:f2:32:10:e6 August 24 2009 blocked as per IT Policy Advisor mail
0:17:f2:35:eb:a1 hdmac-georges
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:4a:33:3d pu102488.student
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:4c:f6:77 oracle3
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: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:c4:9e:57 dragoon
0:17:f2:c5:29:59 August 17 2008 connected via rogue wireless bridge
0:17:f2:c8:d6:74 ryu-macbook
0:17:f2:cd:76:70 mol-cd7670
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: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:ec:24:bc ryu-macbook
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:41:68:78:b4 pu118812.student
0:18:41:7:96:9b pu120563.student
0:18:41:9d:aa:53 pu124633.student
0:18:41:ad:2a:9f pu120202.student
0:18:41:d2:1a:4a pu112205.student
0:18:41:dc:71:1f Feb 16 2009 using incorrect IP addresses
0:18:41:df:3f:c4 Feb 18 2009 using incorrect IP addresses
0:18:41:e7:12:b5 Feb 16 2009 using incorrect IP addresses
0:18:4d:ba:1e:99 mol-ba1e99
0:18:70:0:0:ff pu120960.student
0:18:8b:87:ef:17 mzondlo-homepc
0:18:8b:db:39:7d September 8 2009 blocked as per IT Policy Advisor mail
0:18:8b:de:4:49 oracle3
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:53:77:d3 pu117282.student
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:de:be:7c:3a art-102209a
0:18:de:d5:36:e7 gen-cafe-laptop
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:15:93:d6:2a pu123699.student
0:19:79:99:2:17 July 7 2009 forwarding broadcast traffic
0:19:79:99:f3:6f pu115630.student
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:41:9:b6 pu112807.student
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 August 25 2009 blocked 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: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:6e:d7:30 chm-vavilala
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:9f:2d:d3 Jan 16 2008 rogue wireless bridge stealing IP
0:19:d2:a:1a:b0 June 30 2008 rogue DHCP server
0:19:d2:c0:53:7d pu117740.student
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: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:2d:9a mol-cd7670
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:4a:1d:8f:11 Aug 22 2008 hardware address forgery
0:1:4a:25:a8:b9 commnet2.ee
0:1:e6:9e:e2:1 Apr 4 2005 broken DHCP client
0:1a:6b:35:3:a7 pu112807.student
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:81:90:42 phy-jlehners
0:1a:73:90:82:4b b311e-hp.ee
0:1a:73:90:df:9 pu120960.student
0:1a:73:93:e8:71 July 18 2008 as per IT Policy Advisor mail
0:1a:73:b4:88:90 pu116250.student
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:88:82:c5 phy-jlehners
0:1b:24:96:11:d7 b311e-hp.ee
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:2f:ab:10:74 Jan 13 2009 DHCP client overstaying lease
0:1b:2f:ab:12:ab Jan 21 2009 DHCP client problem
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:93:34:e3 dev-mac02
0:1b:63:95:10:7d June 20 2008 rogue DHCP server
0:1b:63:97:ab:c mjsouza-mac
0:1b:63:98:72:f5 phi-mcgrathimac
0:1b:63:9f:af:7a pu112271.student
0:1b:63:a7:ad:3f arc-dorkand-s2009
0:1b:63:a9:d3:7 eas-w8742dt7x85
0:1b:63:b1:b7:94 pu118063.student
0:1b:63:bf:49:72 dev-mac02
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: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:1b:d3:39:5d:c1 tfranz-toughbook
0:1b:fc:c1:23:7d March 12 2008 malfunctioning NAT attached via TVWNA
0:1c:23:4d:b:57 July 24 2008 compromised
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:31:e4:f May 5 2008 malfunctioning DHCP client
0:1c:b3:47:46:c7 October 22 2009 connects and disconnects too rapidly
0:1c:b3:71:f7:60 mjsouza-mac
0:1c:b3:75:1d:1a phi-mcgrathimac
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:bd:1b:3 pu112271.student
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:b3:c5:bb:46 arc-dorkand-s2009
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:1d:92:f1 July 31 1009 ineligible for wireless as per customer request
0:1c:cc:6a:25:17 mmmiller-bb
0:1c:cc:79:e1:98 July 31 1009 wireless client connection flapping
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:e6:e9:24 aksay-blackberry
0:1c:cc:e7:57:f8 August 21 2008 broken DHCP client
0:1c:cc:ef:d9:bc July 31 1009 wireless client connection flapping
0:1c:df:1:13:21 pu111705.student
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:d0:20:c3 pu115666.student
0:1d:4f:d1:2:ad pu119809.student
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:f2:8a:e Oct 1 2008 running multiple DHCP clients simultaneously
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:f6:c1:a6 eas-w8742dt7x85
0:1d:4f:fe:91:46 Nov 21 2008 rogue wireless bridge stealing IP
0:1d:60:b7:62:eb pu114465.student
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:7e:1a:79 pu111964.student
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:33:67:af:69 chm-kaneko
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:4f:c9:6a:b0 exia.ee
0:1e:52:22:82:13 humansky-mobile
0:1e:52:71:f:2e pu118063.student
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:c0:84:e7 pu118802.student
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:68:5f:e8:18 yaffeom.ee
0:1e:68:b5:b7:7e pu120144.student
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:53:90:a3 pu116121.student
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: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:c2:60:9 yaffeom.ee
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:b4:5f:43 littewhite
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:be:7e:1b August 19 2009 blocked as per IT Policy Advisor mail
0:1f:5b:c1:62:1 machinery2
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:5b:f8:8b:4f littewhite
0:1f:a7:20:d8:13 August 17 2008 ignores DHCP lease expiration
0:1f:c6:e4:22:4 pu111964.student
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:7b:b8:61 spa-f8j673217
0:1f:e1:c3:a:17 Nov 30 2008 malfunctioning DHCP client
0:1f:f3:1:e5:5e May 17 2008 Wireless Access Point with malfunctioning DHCP client, also acting as rogue network bridge
0:1f:f3:1:e5:5f May 17 2008 Wireless Access Point with malfunctioning DHCP client, also acting as rogue network bridge
0:1f:f3:45:5b:ee demo-mini
0:1f:f3:46:bd:7a ftang
0:1f:f3:c8:f4:35 Nov 30 2008 rogue DHCP server
0:1f:f3:d7:28:f5 machinery2
0:1f:f3:fb:18:81 demo-mini
0:20:0:34:34:30 Nov 9 2008 broken DHCP client
0:20:0:3b:77:7 pu124597.student
0:20:4a:52:bc:43 mec-cscs-apog71
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: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:20:e0:98:43:cb pu120501.student
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:43:65:4 July 31 1009 wireless client connection flapping
0:21:6:4b:66:84 pu119296.student
0:21:6:86:b5:50 pu119962.student
0:21:6:88:a1:bd May 11 2009 poorly-behaved DHCP client
0:21:6:cb:c2:23 November 2 2009 keeps connecting and losing its wireless connection too rapidly
0:21:6:de:bf:86 September 20 2009 keeps losing wireless connected then reconnecting
0:21:6b:4d:1c:74 Jan 17 2009 rogue DHCP server
0:21:70:5b:ce:d0 pu124832.student
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: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:23:24 April 1 2009 DHCP Client Identifier doesn't match hardware address
0:21:e9:5d:37:79 Oct 9 2008 rogue DHCP server
0:21:e9:7b:70:22 pu118877.student
0:21:e9:98:17:b8 Nov 23 2008 trying to use BootP on TVWNA, also 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:ac:30:cf august-iphone2
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:21:e9:e2:97:fc gen-apetti
0:22:15:5b:7f:d8 November 12 2009 rogue DHCP server
0:22:19:e0:75:c3 pu123413.student
0:22:41:0:22:45 Nov 4 2008 running multiple DHCP clients on a single network interface
0:22:41:1d:fa:dc rollsroyce
0:22:41:23:41:55 gen-apetti
0:22:41:5f:86:cc pu119139.student
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:2b:b3:f4 pu121116.student
0:22:43:47:7e:5f July 28 2009 rogue wireless bridge stealing IP
0:22:64:da:34:ea pu124059.student
0:22:69:1e:26:98 pu120144.student
0:22:fa:9e:3:6a August 6 2009 rogue DHCP server
0:22:fa:d0:df:4c tfranz-toughbook
0:22:fb:12:e8:6a pu123413.student
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:2f:0:84 rollsroyce
0:23:32:91:8a:df falkirk
0:23:32:d3:60:1e October 16 2009 malfunctioning NAT software
0:23:32:da:c:fc math-fcpkwon
0:23:4d:41:1e:17 chm-kaneko
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: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:2b:c3:c0 pu115503.student
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:7b:b7:9 ftang
0:23:6c:84:87:19 June 15 2009 blocked as per IT Policy Advisor mail
0:23:6c:86:1e:e5 math-fcpkwon
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:0:0:1 pu124010.student
0:23:7a:3d:f7:2a pu120949.student
0:23:7a:3f:24:66 Feb 5 2009 running multiple DHCP clients on a single network interface
0:23:7a:60:a8:de pu124010.student
0:23:7a:61:f:72 September 3 2009 wireless client connection flapping
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:24:9f:a7:36:2c pu123516.student
0:24:9f:cc:49:90 pu124569.student
0:24:e8:2a:b5:77 pu123678.student
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:8f:b9:41 llilly
0:25:4b:b1:6:2a llilly
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:57:c4:22:70 pu122681.student
0:25:57:ec:e4:72 pu124185.student
0:25:64:45:b0:4a gen-8bb0sk1
0:25:bc:13:04:f1 June 1 2009 persistently stealing IP address
0:25:bc:2a:b5:bb pu123821.student
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:f0:17:1e pu124425.student
0:26:4a:f1:fc:5a October 11 2009 rogue DHCP server
0:26:5e:31:44:a6 gen-8bb0sk1
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:5d:53:bb pu119156.student
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:26:bb:f1:b6:6f pu118487.student
0:2:0:f9:5:67 pu120949.student
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:6d:cc:d2 pu104693.student
0:2:2d:7c:1e:69 Dec 22 2007 running two DHCP clients on one interface
0:2:2d:92:dc:bc Nov 29 2005 compromised and theft of service
0:2:2d:b2:c3:8b July 23 2006 rogue DHCP server
0:2:3f:24:61:4f Nov 8 2005 using IP addresses not belonging to it
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:8a:dc:3b:cb pu124336.student
0:2:96:0:84:b6 Oct 18 2006 compromised
0:2:a5:9d:73:f3 July 16 2007 compromised
0:2:a5:a6:4d:d3 Apr 19 2004 theft of service
0:2:a8:c7:7d:ef September 13 2009 stealing IP address
0:2:b3:a3:64:57 afm.ee
0:2:dd:32:8c:e9 Mar 25 2003 rogue DHCP server
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:48:72:ce:ee psg7
0:30:4:7:d7:56 May 31 2005 broken DHCP client
0:30:65:20:d0:97 Apr 11 2005 broken DHCP client
0:30:65:27:75:3e Dec 4 2006 broken DHCP client
0:30:65:2:c3:81 Dec 16 2002 broken DHCP client
0:30:65:6:a1:a4 Mar 30 2004 broken DHCP client
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:25:3e:4:ab dms-stevewar
0:3:47:76:57:bb Aug 19 2005 compromised
0:3:47:8d:fb:51 Oct 18 2005 compromised
0:3:47:90:51:82 Sep 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:6d:1a:bd:b7 mbntsrv1
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: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:2b:67:25:ca rayleigh
0:40:2b:71:2a:5d pu101539.student
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:29:88 September 14 2009 rogue DHCP server
0:40:5a:23:a4:40 September 20 2009 rogue DHCP server
0:40:96:30:a:e1 Dec 9 2002 theft of service
0:40:ca:6e:42:13 June 27 2006 wireless bridge, 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: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 May 24 2004 theft of service
0:4:23:49:42:a2 May 17 2003 rogue DHCP server
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:79:9:66 Feb 27 2008 manually configured to steal IP address
0:4:23:7d:a3:92 pu111013.student
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:23:a8:b9:23 bach
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:a2:61:a7 Aug 5 2005 compromised
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:75:f7:5b:3d butlervolmer
0:4:76:30:26:e qsu2.ee
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:2a:27:3b knite-smc-wireless
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:8d:f3:dc:d2 pu119908.student
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:cd:17:f3 xray7
0:50:da:eb:f0:dd Oct 12 2005 compromised
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:8a:59 Nov 5 2002 rogue DHCP server
0:5:3c:3:b3:78 Jan 10 2007 compromised
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:3:d3:ab Apr 9 2003 rogue DHCP server
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:4e:47:ad:80 Apr 14 2005 disrupted campus network
0:5:4e:4a:2e:30 May 10 2006 forging DHCP chaddr
0:5:4e:4b:b1:ea pu117657.student
0:5:5d:f2:33:99 Nov 10 2003 theft of service
0:5:5d:fa:6f:d3 Nov 10 2003 theft of service
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:1b:cf:6e:f2 pu120501.student
0:6:25:aa:6a:21 Aug 25 2005 compromised
0:6:2a:db:a0:c falkirk
0:6:5b:17:49:44 psy-chlds01
0:6:5b:17:4d:d1 psy-3nlds01
0:6:5b:1:77:d5 phi-johno-340
0:6:5b:29:ed:f0 chm-orgo2
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:89:19:a August 19 2009 compromised
0:6:5b:a9:f7:af mol-j736f11
0:6:5b:bb:38:c0 Sep 27 2005 compromised
0:6:5b:cf:7d:85 arc-6d9wq11
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:40:d8:8c:83 butlervolmer
0:7:68:0:e0:46 March 15 2007 stole IP address
0:7:e0:28:34:eb Dec 12 2007 broken DHCP client
0:7:e9:7b:a7:a5 July 1 2008 compromised
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: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:4:6f:e9 July 19 2005 compromised
0:8:74:4a:6:40 pu104693.student
0:8:74:f8:a:73 psy-8mq9r21
0:8:a1:1e:55:5 highpress
0:8:a1:22:d3:ed Oct 18 2006 compromised
0:8:d:a3:40:f1 August 12 2009 using incorrect IP address
0:90:27:de:2b:9d Dec 17 2007 compromised
0:90:4b:2c:ad:50 Feb 20 2007 broken DHCP client
0:90:4b:2d:5e:98 Dec 2007 rogue DHCP server
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:7e:ef:58 Jan 16 2006 rogue DHCP server on TVWNA
0:90:96:c1:f2:11 shua.ee
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 pda219.ee
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:2:47:4e Aug 25 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:50:3b:3a Oct 11 2005 compromised
0:9:6b:90:5a:3f April 24 2007 compromised
0:9:6b:90:5b:7b Sep 28 2005 compromised
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: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:57:df:76 stokes
0:a0:c9:85:6a:3e March 15 2007 compromised
0:a0:c9:8d:66:73 Jan 26 2006 compromised
0:a0:c9:b7:54:ed old-whigclio
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:c9:41:c4 June 8 2007 forged
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:14:de:50 csn-112100a
0:b0:d0:22:cc:5 curie
0:b0:d0:42:ba:57 March 15 2007 compromised
0:b0:d0:95:23:66 May 17 2005 compromised
0:b0:d0:c3:da:aa Jan 26 2006 compromised
0:b0:d0:c4:a7:e Feb 21 2006 compromised
0:b0:d0:c4:e0:96 tin-58svh01
0:b0:d0:ca:e8:1 geo-9b8yl01
0:b0:d0:ca:e8:3 geo-jw8yl01
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:e7:3a:51 eco-grfl-kiosk
0:b0:d0:f2:f8:be Feb 28 2008 rogue DHCP server
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:be:85:5:3d July 8 2008 stealing TVWNA IP address
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:40:fb:c rel-12ky131
0:b:db:59:15:d4 eco-8zlsh31
0:b:db:6f:d5:3e geraldine
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: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:dc:ae:74 pu111013.student
0:b:db:e7:2b:78 Sep 10 2005 compromised
0:c0:4f:18:33:65 Jan 26 2006 compromised
0:c0:4f:22:18:ff June 7 2005 compromised
0:c0:4f:22:a1:18 Nov 11 2005 compromised
0:c0:4f:33:77:50 daimler
0:c0:4f:33:c7:d8 August 24 2009 compromised
0:c0:4f:33:c7:d8 August 24 2009 compromised
0:c0:4f:46:79:2c Feb 2 2007 compromised
0:c0:4f:65:74:83 Dec 4 2006 compromised
0:c0:4f:6:ad:2b Nov 16 2005 compromised
0:c0:4f:8d:30:2f July 6 2006 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:98:dc:8b mae013098
0:c0:4f:a8:96:3f mol-bfbq0
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:bd:61:e7 che-rar-16
0:c0:4f:c:8b:87 bellini
0:c0:4f:d:34:5d July 25 2006 compromised
0:c0:4f:e:d2:f9 corrosionii
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: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: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:c0:f0:5c:20:e6 tamarin.ee
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:7b:b9:33 Jan 16 2008 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:b:45:69 hdmac-georgesvm
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:4e:7b:7d romalisb22router
0:c:41:6a:6a:46 eco-grfl-kiosk
0:c:41:b5:b8:ce July 28 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:23:c4:e4 Sep 14 2006 rogue DHCP server
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:4:bc:e5 Sep 18 2006 rogue DHCP server
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:4b:84:be:ce mol-wang-nas
0:d0:59:c8:ae:9c Jan 20 2003 theft of service
0:d0:b5:16:ed:e7 July 8 2008 connected via rogue wireless bridge
0:d0:b7:ae:5c:d mol-rye-lab1
0:d0:c9:9a:1f:9b arc-invision1
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:35:63:5e pu118363.student
0:d:4b:35:8f:42 pu118803.student
0:d:4b:35:8f:43 pu118803.student
0:d:4b:36:4c:86 pu119752.student
0:d:4b:36:4c:87 pu119752.student
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:3b:ab:10 ebouzeid-tv
0:d:4b:3b:ab:11 ebouzeid-tv
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:4b:43:2e:d0 pu115151.student
0:d:4b:43:2e:d1 pu115151.student
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: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:56:fe:bd:d8 pupdc2.pupwin
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:60:f8:4d:9b pu124336.student
0:d:88:e9:9:22 Aug 25 2006 rogue DHCP server
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:9d:1d:a8:30 Oct 12 2008 manually configured to steal IP address
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:11:5:c4:76 pu114620.student
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: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:14:7:7:70 btjadwin
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: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:2c:2d:28 phy-abhay
0:e:35:32:1c:42 Jan 10 2007 compromised
0:e:35:38:0:f4 September 25 2009 overstayed DHCP lease
0:e:35:39:46:8 pu103086.student
0:e:35:3d:24:2b kornfelljsa
0:e:35:3f:6f:62 Sep 1 2006 rogue DHCP server
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:73:ff:8d pablo-laptop
0:e:35:7b:c9:67 July 30 2009 compromised
0:e:35:9:21:b Jan 12 2007 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:ad:8a:25 Jan 15 2007 compromised
0:e:35:af:19:cf June 14 2006 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:e6:bf:4f pu117130.student
0:e:35:f0:9c:fb Aug 22 2008 using inappropriate IP addresses
0:e:3b:1e:b:46 pu123626.student
0:e:7b:20:59:de June 22 2009 rogue DHCP server
0:e:7b:7c:a5:14 kornfelljsa
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: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: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:8e:80:52 congress
0:f:1f:a1:df:74 Oct 19 2007 compromised
0:f:1f:b5:6b:24 pu103086.student
0:f:1f:bd:6e:d1 August 5 2008 as per IT Policy Advisor mail
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:3d:a8:bd:af August 29 2009 overstaying DHCP lease
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:66:ec:1c:be pu114465.student
0:f:b0:37:ec:94 shua.ee
0:f:b0:42:51:51 pablo-laptop
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
16:92:54:13:61:72 August 19 2009 blocked as per IT Policy Advisor mail
2:0:0:0:0:31 pu119139.student
2:0:0:11:23:58 pu120563.student
2:0:0:4b:66:84 pu119296.student
2:0:0:87:90:2 pu118802.student
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
34:80:23:79:40:29 pu115630.student
44:2:93:68:83:e5 July 4 2006 rogue DHCP server
4:62:65:87:3e:f9 June 20 2006 rogue DHCP server
52:8c:5a:a9:50:d4 July 16 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:20:88:f7:55 Feb 21 2007 compromised
8:0:46:18:bb:dc mamatore
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: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:69:a:75:f3 old-chem1
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
c:c:c:c:c:1 August 3 2007 forged hardware address
d8:f4:f4:d0:89:98 August 1 2007 forged hardware address


Notes

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

You may click on the hardware address to try to look it up in the Princeton University Host Database. The ability to perform this lookup is restricted to those computers that are members of the Princeton.EDU DNS domain. (If the entry was added, changed, or deleted from the Host Database within the last few hours, an accurate lookup may not be possible yet.)

A hardware address may appear multiple time if it is blocked via more than one mechanism.

Hostname
This is the hostname of the client's device, as it appears in the Princeton University Host Database. This field is not always present because some hardware addresses have been marked ineligible for OIT Wireless Service (or all wireless services) regardless of whether or not they are in the Host Database, thus may have no hostnames.

If this field is present, you may click on it to try to look it up in the Host Database. The ability to perform this lookup is restricted to those computers that are members of the Princeton.EDU DNS domain. (If the entry was added, changed, or deleted from the Host Database within the last few hours, an accurate lookup may not be possible yet.)

Date
This is the date that the device was declared ineligible.

The field is usually available for hardware addresses not present in the Host Database. It is usually unavailable for devices present in the Host Database; the persons responsible for the device were notified at the time it was declared ineligible.

Access Points
This field appears only in the table of devices declared partially ineligible for OIT Wireless Service. The client is ineligible to use the service from these specific Access Points. The client may still be eligible to use the service from other Wireless Access Points.

Reason Ineligible
This is the reason that the client was declared ineligible.

The field is usually available for hardware addresses not present in the Host Database. It is usually unavailable for devices present in the Host Database; in those cases, a reason was already communicated to the persons responsible for the device at the time it was declared ineligible, if it was registered in the Host Database at that time.


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