CARP, and multiple networks on a single interface.
-
None. This is the triple-gigabit hacom model. The only thing "different" is that on both of my boxes I've added a single 10/100 NIC to get a fourth interface. One was an rl and the other dc. (I think….I'm not at the data center right now).
You've seen this error before? Is it really required that you have an IP in the same subnet on a physical interface for a CARP virtual IP to work? Doesn't seem right to me for some reason.
Yes, it's really required.
–Bill
-
You beat me to the post by a few seconds. See my post above. How would you approach my situation?
-
Side note - I tried to alias 206.80.88.2 and .3 to the LAN interfaces on each box. pfSense's code does not recognize aliases and still states that an IP on a real interface must exist. Proxy-ARP on each box won't do it either.
-
Well, I went back to the data center, and I tell ya, I'm starting to wonder about the power supply of these Hacom boxes. I had to play musical NIC's, but I did finally get a combination of cards that seem to be stable, a single rl and de. Everything else was causing kernel panics. I'm concerned that the quad 10/100 soekris cards I just ordered will be just as unstable. :(
After having spent $700 a pop on these systems, I get the feeling I'm going to have to go with a home grown solution, which really sucks as the form factor on these is good, but if the PCI slots are useless, then the entire system is. :\
-
Contact bao from hacom concerning your (possible) powersupply issues. I'm sure he's willing to help you or give you some advice.
-
Is there anything that can be done with the network layout above? It really blows not being able to have more than one CARP-able network per interface.
-
Afaik this is a limitation of how CARP works but somebody might proof me wrong.
-
Well, a way to test it would be to not use the web interface at all, and use the console to set up a carp VIP. Then go back and try to use aliases and set up a second one. Don't have a console handy to try it at the moment, but it would be useful to know.
-
As others have already told you this will not work.
-
Sorry, wasn't trying to push my luck, was simply trying to figure out where the limitation was, whether it was with CARP or with pfSense.
That said, my "crashy"-ness appears to be part of a known bug. 2 phone calls with Bao Ha came to this:
http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/88610
They're going to try to beef up the power supply from the current 60 Watt. Going to be next week before I have further news on that front. Shame you can't use 5 or more interfaces on FreeBSD 6.0. No movement on that bug since November either.
-
Update - Bao tried a better power supply, but that doesn't appear to be the problem, there seems to be something wrong with the PCI bus, and is taking the matter up with the manufacturer in Hong Kong.
I hope he gets it resolved soon. These are pretty expensive door stops!
(I guess this became a hardware thread on me, didn't it?)
-
Another update. Hacom has pulled their boxes from their website. They've confirmed a serious issue with the PCI bus and are working to resolve the problem. They've since refunded me for my systems. Hope they get it resolved soon!
:o