lostsoul

I've not got specific experience with Ruckus, have you reconfigured the switch ports? Is VLAN 5 still untagged on the AP? Can you restore from a configuration backup?

These instructions look quite good: How Can I Configure my Vigor Router in "Bridged Mode" - Powered by Kayako Help Desk Software Maybe give it a hard reset and start from scratch if you haven't tried that.

Have you put the draytek in bridge mode?

As it's on hyper-v, can you grab a backup using the free version of veeam? Then if things go south with with the RAID, you have a reasonably quick way to get it back up and running.

You need to set up a dynamic DNS updater: http://chasechristian.com/blog/2013/02/palo-alto-networks-using-a-dynamic-public-ip-address/

I use a Vigor 130 with a Mikrotik router, it's a transparent bridge, so you should just be able to plug it into your routing device and be good to go. I also set up a NAT rule on my router so I could still access the web config page from my internal network when connected to the internet (useful to see modem stats). I'm very happy with the performance and reliability.

You say smoothwall was doing radius, was it just wireless clients authenticating against that? are you still using radius? Can you quickly set up a PSK on you wireless controller to rule that out?

Yes. What was the reasoning for removing the VLANS? You now have a massive flat network that contains all devices? Seems like a backward step to me. I'm assuming you've modified your dhcp scopes to reflect the new setup?

What happens if you give a laptop a static address on the network?

I think your best bet is to just add the zone internally and add the required DNS entries to make everything work. This is called split brain DNS, and is the normal way to accomplish what you want.

Can you not just add a firewall rule to allow the PCs access to the DMZ resource? Multi-homing PCs is not something I would do.

All working now. Turns out the integration services on the VMs needed an update.

Does anyone have any experience with this software? We have been evaluating it with a trial license, and I have come across a problem with a couple of our hyper-v hosts. The agent installs correctly and all connection tests pass, but when a back up starts it will just hang on the creating backup snapshot stage, the timer keeps counting up indefinitely. Any other jobs against the same server started subsequently just fail with a timeout message. We have other hyper-v hosts with the same configuration that work fine. Just can't work out what the problem is.

Sorry didn't read your post properly. Should be easy then, just add both VLANs tagged on the up links. Then use untagged ports for your sender/receiver and PCs on the other vlan. Any frames coming in on an untagged port will be associated with the assigned VLAN. Layer 3 shouldn't come into it, as I assume there is no reason for the traffic to pass between the vlans?

For your uplink, just add all the vlans as tagged on the port. Obviously you need to have the same VLANs tagged on the ports at both ends. I suspect the sender and receiver device will need to be connected to a un-tagged port on the vlan at both ends, as it's unlikely they will understand vlan tags. Not sure why you need two vlans for this?