Unknown DHCP ping

deleted

This post is deleted!

deleted

Yes, the connection is connected to a LAN switch.
It is a Cat 6a patch cable.

(Have a little patience. If I try to post everything at once it will be marked as spam.)

ix0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: server
	options=48138b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
	ether 3c:ec:ef:bf:98:ba
	inet 192.168.7.1 netmask 0xfffffff8 broadcast 192.168.7.7
	inet6 fe80::3eec:efff:febf:98ba%ix0 prefixlen 64 scopeid 0x1
	media: Ethernet autoselect (10Gbase-Twinax <full-duplex,rxpause,txpause>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
ix1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: thc
	options=48138b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
	ether 3c:ec:ef:bf:98:bb
	inet 192.168.8.1 netmask 0xfffffffc broadcast 192.168.8.3
	inet6 fe80::3eec:efff:febf:98bb%ix1 prefixlen 64 scopeid 0x2
	media: Ethernet autoselect
	status: no carrier
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
igb0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: media
	options=48120b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
	ether 3c:ec:ef:bd:09:48
	inet 192.168.6.1 netmask 0xfffffff0 broadcast 192.168.6.15
	inet6 fe80::3eec:efff:febd:948%igb0 prefixlen 64 scopeid 0x3
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: office
	options=48120b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
	ether 3c:ec:ef:bd:09:49
	inet 192.168.9.1 netmask 0xfffffff8 broadcast 192.168.9.7
	inet6 fe80::3eec:efff:febd:949%igb1 prefixlen 64 scopeid 0x4
	media: Ethernet autoselect
	status: no carrier
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
igb2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=48120b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
	ether 3c:ec:ef:bd:09:4a
	media: Ethernet autoselect
	status: no carrier
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
igb3: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=48120b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
	ether 3c:ec:ef:bd:09:4b
	media: Ethernet autoselect
	status: no carrier
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
igb4: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG>
	ether 3c:ec:ef:be:04:b4
	inet6 fe80::3eec:efff:febe:4b4%igb4 prefixlen 64 scopeid 0x7
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
igb5: flags=1008943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: lan01
	options=48120b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,HWSTATS,MEXTPG>
	ether 3c:ec:ef:be:04:b5
	inet 192.168.1.1 netmask 0xfffffff0 broadcast 192.168.1.15
	inet6 fe80::3eec:efff:febe:4b5%igb5 prefixlen 64 scopeid 0x8
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
enc0: flags=0 metric 0 mtu 1536
	options=0
	groups: enc
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet 127.0.0.1 netmask 0x0
	inet 10.10.10.1 netmask 0xffffffff
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

stephenw10

So none of those interfaces.

The 1537 has a dedicated NIC for IPMI. Is that connected to the switch? I'd bet that's the MAC you're seeing.

By default we ship those with the IPMI isolated but it is possible to set it up to share a port. You should check that in the bios/ipmi setup.

deleted

That's right, this is also the MAC of the BNC.

That was also my first thought, that something was wrong there.
But I have checked the bios / settings several times and can confirm that only the static IPv4 is active.

Okay, but if you can rule out the source of the error in the pfSense, thank you for looking.

johnpoz

@deleted Do you use this feature? If not just unplug it. But it does seem handy

For sure @stephenw10 would be the guy to help you with how to change it so it doesn't send that out, maybe if it shares a port?

I don't see any instruction on how to change IPv6 here

https://docs.netgate.com/pfsense/en/latest/solutions/xg-1537/ipmi-access.html#reset-ipmi-network-configuration

Or in the info with gui.. in the netgate manuals - but I did lookup manual from supermicro, and see this

Are you saying you don't see anything for IPv6? Maybe some firmware just needs to be updated?

Other way to skin the cat would be to just not log the noise.. If you check that box to allow IPv6 then those block rules would not be created.. As long as you don't setup or allow IPv6 - its not going to do anything.. And if your still logging it with normal default log, you could create a specific rule not to log that traffic.

I mean the correct fix would be to disable IPv6 in the ipmi software.. But there are normally multiple ways to skin the cat.

Another option would be to turn off logging of default deny log, and then create your own rules to log what you want to see for deny. Not logging this traffic.

stephenw10

Just to be clear is the dedicated IPMI port actually connected to anything?

https://docs.netgate.com/pfsense/en/latest/solutions/xg-1537/io-ports.html#other-ports

If it's not then it pretty much has to be the shared port setting.

But, yes, either way you should be able to set the IPMI module to not use IPv6 at all as @johnpoz shows above.

deleted

Thank you for your efforts.

Yes, the function is good but not important for my scenario.

However, I have just checked again exactly where your arrow is in the menu. No IPv6 active.

And I can definitely confirm that it is the IPMI connection.
After I removed the cable, the entries stop.

Then it can only be a bug in the bios. I have checked all settings several times and will look in this right.

Thanks again.

stephenw10

@deleted said in Unknown DHCP ping:

I have just checked again exactly where your arrow is in the menu. No IPv6 active.

It's specifically set to 'Disabled' there?

deleted

Everything that can be off is off.

Something doesn't fit. When I have the solution, I'll let you know.

johnpoz

@deleted the manual I found had a disable option - not sure if for same version of ipmi you are running.. But with that setting of dhcpv6 - I would expect it to yeah send out dhcpv6. Its like yours is missing the disabled option