Anonymous | Login | 2024-11-22 23:37 EST |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0001060 | PacketFence | dhcp | public | 2010-09-08 11:55 | 2014-12-04 07:52 | |||
Reporter | obilodeau | |||||||
Assigned To | jsemaan.inverse | |||||||
Priority | normal | Severity | feature | Reproducibility | N/A | |||
Status | closed | Resolution | fixed | |||||
Platform | OS | OS Version | ||||||
Product Version | ||||||||
Target Version | Fixed in Version | |||||||
Summary | 0001060: pfdhcplistener: DHCP Vendor support | |||||||
Description | More and more DHCP fingerprints are duplicated for completely separate devices (even device types). A look at the Vendor code could be an easy way to tie break the choice between two devices. Look at the dhcp option RFC to find more about dhcp option 43 and dhcp option 60. 43: vendor specific information 60: vendor id For a given fingerprint, we should be able to say if DHCP Vendor is X then it's OS Y but there should also be a default fallback. Also, looking at DHCP Vendor alone could be interesting or at least storing it and uploading it along with the unknown fingerprints. Specifically this would help for the Xbox 360, currently identified as an OEM Wireless router. | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
Relationships | ||||||||||||||||
|
Notes | |
(0002620) rgraves (reporter) 2012-03-19 17:45 |
A possible workaround without changing pfdhcplistener would be to hack at dhcpd.conf. class "embedded-class" { match pick-first-value (option vendor-class-identifier, host-name); } subclass "embedded-class" "Xbox 360"; subclass "embedded-class" "Nintendo 3DS"; subclass "embedded-class" "Wii"; subclass "embedded-class" "NintendoDS"; And then split the pool, with deny/allow members of "embedded-class"; as appropriate. Then vlan::custom would need to know the IP address. Currently, it does not. |
(0003030) obilodeau (reporter) 2012-09-07 13:14 |
Encountered another case pushing for this feature today: PS3 when doing initial broadcast DHCP request does send its option 55 but when doing unicast DHCP Requests afterwards it is not sending option 55. Vendor field is properly populated with PS3 all along. |
(0003619) jsemaan.inverse (administrator) 2014-12-04 07:52 |
This is not relevant anymore with the new version of fingerbank. Closing |
Issue History | |||
Date Modified | Username | Field | Change |
2010-09-08 11:55 | obilodeau | New Issue | |
2010-09-08 11:55 | obilodeau | Status | new => assigned |
2010-09-08 11:55 | obilodeau | Assigned To | => obilodeau |
2010-09-08 12:08 | obilodeau | Relationship added | related to 0001062 |
2010-11-19 14:25 | obilodeau | Target Version | 1.10.0 => 2.0.0 |
2011-01-18 09:30 | obilodeau | Target Version | 2.0.0 => 2.1.0 |
2011-03-03 15:16 | obilodeau | Target Version | 2.1.0 => +1 |
2011-03-03 15:18 | obilodeau | Target Version | +1 => +2 |
2012-03-19 17:45 | rgraves | Note Added: 0002620 | |
2012-04-20 09:44 | obilodeau | Relationship added | related to 0001428 |
2012-09-07 13:12 | obilodeau | Relationship added | related to 0001061 |
2012-09-07 13:14 | obilodeau | Note Added: 0003030 | |
2012-10-19 13:47 | fgaudreault | Assigned To | obilodeau => |
2012-10-19 13:47 | fgaudreault | Target Version | long-term => general |
2014-12-04 07:52 | jsemaan.inverse | Note Added: 0003619 | |
2014-12-04 07:52 | jsemaan.inverse | Status | assigned => closed |
2014-12-04 07:52 | jsemaan.inverse | Assigned To | => jsemaan.inverse |
2014-12-04 07:52 | jsemaan.inverse | Resolution | open => fixed |
Copyright © 2000 - 2012 MantisBT Group |