RED bridge to lan
RED device does not currently bridge the existing 'internal' interface on the UTM. when you set it up you have to create a seperate ip from the 'internal' dhcp. therefore it does not show up on the same LAN. it is on a seperate LAN.
bridge to lan feature like the AP devices would be a great addition. this way everything is on the same network and can view networked drives or computers or shares.
i have made a workaround to fix it for now until there is an update. it is as follows.
make backup prior
1: add red manually.(client management) not with the deployment helper.
1a: make sure it is not turned on under red client management
2: if you have an 'internal' interface on ethX under 'interfaces and routing', you must delete this interface and everything that is associated with it.
3: you should now have two hardware you can bridge.(redsX and ethX)
3a: create new interface with type as 'ethernet bridge' and under hardware check those two devices. (ethX and redsX)
4: now create a new DHCP for whatever you named your bridge to.(br0).
4a: if you did already assign hosts and static ip under your previous internal you can just use the same subnet and gateway ip group.(10.10.100.1/24)
5: firewall rules now all need to be redone. for very short period you need to add a rule for 'bridge network'-any-any to make sure everything works on the red side then start making your new rules.
all in all this was a pita but was very successful because i could not wait the 12 hour wait time for tech to call/enough info on the web for this solution.
i have forgot to add. after you make the any any rule you can turn on the red in client management.