On Tue, Jun 15, 2010 at 2:16 PM, LeviaComm Networks NOC <n...@leviacomm.net> wrote: > > I just wanted to eliminate as much as possible before spending too much time > on the problem. I have a few questions about your setup:
No problem. > How is your switch configured? Is this the only switch? It's a stack of six Enterasys C3G124-48P switches (which appears as one logical switch), totalling 288 GigE ports. It's connected via GigE fibre to approximately 24 other switches/switch stacks across our campus, as well as a few hundred network devices in this particular building. Our gear is mostly Enterasys, though we have some ancient Nortel Baystacks, some old Cisco, and (unfortunately) a few Linksys switches. > If not, is it > getting VLAN information from any other network appliance? Nope. All our VLANs are defined statically. We don't use VTP or anything similar. The switch the router is connected to is our core switch, and is unusual in that it sees every VLAN on the network - a distribution switch will only see the 4-5 VLANs required for the particular building it services. > I take it from > the fact that you are using a server in a router-on-a-stick configuration, > your switches can't do routing, so, What are you using for routing? What > routing protocols are you using? Or are you just using static routes on > everything? We just use static routing internally. We do router-on-a-stick because we have about 30-40 VLANs I would like to route between, and 30-40 NICs in a server gets pricey :) The OpenBSD box, the Linux router it is replacing, and a couple of Linux edge routers doing BGP to two ISPs are the only routers on our network. My aim is to replace the Linux box with two OpenBSD routers running CARP. What may also be significant was that when I was having the issue yesterday, I had a roundrobin trunk configured from two interfaces on the OpenBSD box back to the switch. > OpenBSD may be running the network in promiscuous mode, which would be why > it is responding to MACs that it shouldn't. If you aren't running a clean > installation, I would recommend turning off everything except routed, > including sshd and just use the console for now. I would also recommend > removing all your VLAN interfaces and reconnect only 2 then test with that, > slowly adding VLANs back as they work. I'll give this a try. The switch has started behaving correctly now (I've got a suspicion the switch's issue was related to LACP being enabled and a roundrobin trunk on OpenBSD), so I'm having some trouble making OpenBSD in turn break. I might try inserting a hub and a couple of test hosts and see what happens. Cheers, Patrick -- http://www.labyrinthdata.net.au - WA Backup, Web and VPS Hosting
