PfSense 2.3 Issue Creating LAGG
-
Good Evening all,
I've recently decided to take a more active interest in my home network setup, as it's been about 10 years since I did any serious networking in college. With that in mind, I recently purchased a used HP Procurve 1810-24G (V1) and decided to try my hand at creating a LACP LAGG group…
A step back, my pfSense box is a repurposed XBMC box running an integrated Celeron 1007D. This board has 2 Realtek 8111 gigabit ports on board, and I've since purchased a third nic to round out the pfSense box. I realize that Realtek is not ideal, but in this case I'm recycling old parts... and while I do have quite a few Intel NIC's lying around, they're all PCI-e and the board only has a PCI expansion slot.
I will say that I had been running this setup just fine using the 2 onboard NIC's for the last couple of years, so I figured this would be an easy experiment. I also realize that in a small home environment, what I'm trying to do is uneeded, but I'm more after this as a learning experience.
Ok, so I read the information I could find about creating a LAGG, and went ahead and did it. No go, I have no network connectivity, though I can ping the outside world from the command line of the pfSense box. Try a few different things to no avail. I then do some more reading and discover that FreeBSD 10 defaults to active LACP instead of passive. I believe the 1810 only supports passive, so after some more digging I find the advanced setting within pfSense to enable it to be passive.
Try again, and no luck. I continue to get "Apr 25 07:08:59 kernel re1: Interface stopped DISTRIBUTING, possible flapping" in the logs (and after laughing because I misread flapping), I go back to the drawing board. It's at this time I notice that both my onboard NIC's have the same MAC address, which should not be the case... and this is despite me destroying the LAGG. Do some more troubleshooting and determine that even the bios is seeing them having the same MAC... weird. So I try to change it within pfSense and it seems to work... check the bios and somehow my change has stuck there as well... even weirder.
Anyways, try setting up the LAGG again... feeling good about it... and nothing. Same behavior, I lose network connectivity, but can ping the outside world from the pfSense box. So I'm at a loss, and looking for some guidance. Any help would be appreciated!
~Spritz
PS - I'll probably cross post on the pfSense subreddit.
EDIT - Because I nearly forgot, if I try to go back to my 'old' setup (one onboard nic as WAN, and one as LAN), I also am unable to contact any resources on my local network, but I don't see anything in the logs to indicate why.
-
So the plot thickens. Did a fresh install of 2.2.6 and I am still unable to get an IP on one of my onboard NIC's. The system see's the NIC fine, but regardless of whether it's LAN or WAN it won't grab an IP.
One thing to note, is that I noticed my OpenWRT WAP was running an IPv6 DHCP server… I disabled this, but it was the last thing I did last night before I called it.
I'm starting to think I have a hardware failure... but it seems odd that I would have a failed onboard NIC out of the blue.
~Spritz