Summary: | net-mgmt/arpwatch: Bug in rc script when vlan interfaces are specified | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Daniel Duerr <dd> | ||||
Component: | Individual Port(s) | Assignee: | Kurt Jaeger <pi> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Some People | CC: | pi | ||||
Priority: | --- | Keywords: | easy, patch | ||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Comitted, thanks! A commit references this bug: Author: pi Date: Sun Jul 20 19:38:27 UTC 2014 New revision: 362360 URL: http://svnweb.freebsd.org/changeset/ports/362360 Log: net-mgmt/arpwatch: handle some variant of vlan interfaces When configuring arpwatch_interfaces, /usr/local/etc/rc.d/arpwatch failed if you use VLAN interfaces, e.g.: arpwatch_interfaces="em0.1 em0.2 em0.3" PR: 191344 Submitted by: dd@gizmocreative.com Changes: head/net-mgmt/arpwatch/files/arpwatch.in Over to ports-secteam for MFH It's already in the quarterly since a long time. My bad, just realised Kurt assigned himself an issue he committed in 2014 :) Nothing to see here. |
Created attachment 144103 [details] Patch to /usr/local/etc/rc.d/arpwatch When configuring arpwatch_interfaces, the script breaks if you use VLAN interfaces, e.g.: arpwatch_interfaces="em0.1 em0.2 em0.3" I've attached a patch that fixes it for me. There might be a cleaner way to do this, but this definitely works.