Issue #16630 has been updated by Tero Marttila.

Here's another go at quoting the `ifconfig` output with the correct 
indentations:

<pre>
...
vlan4: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr ...
        priority: 0
        vlan: 4 parent interface: em1
        groups: ...
        status: active
        inet6 ... prefixlen 64 scopeid 0x7
        inet ... netmask 0xffff0000 broadcast ...
bridge0: flags=41<UP,RUNNING>
        groups: bridge
        priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp
        vlan1 flags=3<LEARNING,DISCOVER>
                port 5 ifpriority 0 ifcost 0
        em0 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
                port 1 ifpriority 0 ifcost 0
block out on em0 src 00:24:21:ef:1b:de
pflog0: flags=41<UP,RUNNING> mtu 33152
        priority: 0
        groups: pflog
</pre>

Also added a little more context.

What seems to be the relevant ifconfig code: 
http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/ifconfig/brconfig.c?rev=1.3 
(bridge_list -> bridge_rules -> bridge_showrule -> printf).
----------------------------------------
Bug #16630: Spurious messages with OpenBSD ifconfig output with bridge rules
https://projects.puppetlabs.com/issues/16630#change-71978

Author: Tero Marttila
Status: Unreviewed
Priority: Normal
Assignee: 
Category: 
Target version: 2.0.0
Keywords: facter
Branch: 
Affected Facter version: 1.6.0


On OpenBSD 5.1 with ruby-puppet installed from packages:

`facter` displays spurious output:

    $ facter
    block: no such interface
    block: no such interface
    block: no such interface
    pcidump: /dev/pci0: Permission denied
    block: no such interface
    block: no such interface
    block: no such interface
    architecture => amd64
    
Presumeably due to the following part of `ifconfig` output:

bridge0: flags=41<UP,RUNNING>
        groups: bridge
        priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp
        vlan1 flags=3<LEARNING,DISCOVER>
                port 5 ifpriority 0 ifcost 0
        em0 flags=7<LEARNING,DISCOVER,BLOCKNONIP>
                port 1 ifpriority 0 ifcost 0
block out on em0 src 00:24:21:ef:1b:de

This comes from having a bridge device configured with ethernet-level filtering 
rules:

    ifconfig bridge0 rule block out on em0 src aa:bb:cc:dd:ee



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to