@ianf: "Hi
We've noticed an issue on our firewalls where the first em device
in the system hijacks inbound port 623 tcp and udp.  The OS never
sees this traffic.  Interestingly, em1 and em2 do not appear to be
afflicted by this problem.  Some reading I've done points to a
similar conclusion:
<url>
I've looked at the bios, but I can't find any settings that remotely
hint IPMI or RMCP+ or serial-over-lan.
Does anyone know how I can stop the card or system from stealing
port 623 in hardware or must I just stop using em0 (and/or Intel NICS)?
Here's the pciconf output:
em0@pci3:4:0:   class=0x020000 card=0x10798086 chip=0x10798086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82546EB Dual Port Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet
    cap 01[dc] = powerspec 2  supports D0 D3  current D0
    cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction
    cap 05[f0] = MSI supports 1 message, 64 bit enabled with 1 message
Ian
Ian Freislich"
    @jfvogel: "<quote>
It may be that register doesnt exist on the earlier adapter, I'm not sure.
There is also a system configuration to avoid that port use by the port
mapper, although the exact way slips my mind right now.
If you can test that would be useful.
Jack"
    @jfvogel: "<quote>
This is in shared code, so let me forward the issue to the owners of
same here and see what they say.
Cheers,
Jack"
    @jfvogel: "<quote>
You dont have to do anything this crude btw, there is an setting
in rc.conf I believe to control the range, I'm rusty on the details
right now, I discovered this while working this same issue with
Yahoo, but its been 6 months or more since.
Jack"
    @jfvogel: "<quote>
I've verified that the other drivers dont do anything with this, so
its not really
something they'd let into the shared code, but the sysctl idea sounds doable,
let me think this over, I also need to check some internal docs on various
adapters to see if there's harm in any way in doing this.
Jack"
    @emaste: "<quote>
[patch omitted]
Jack, do you have any update on adding a sysctl etc. to configure the
management port hijacking?  I was just bitten by the same problem and
am going to just hardcode ~(E1000_MANC_RMCP_EN | E1000_MANC_0298_EN)
for now but would like to switch to the fix that will actually end up
in the driver.
- Ed"
{'source': 'USENET', 'other_information': '{"reply_count": 5, "forum_name": "lucky.freebsd.current.20140830.mbox"}', 'file': 'data/output/usenet-lucky.freebsd.parquet'}