On 08/09/2014 16:50, Niklas Fondberg wrote:
I'm not criticizing your choice configuration, there is absolutely no reason not to use VLANs, however, in your design you appear to have a number of VLANs, but I didn't see that (at the moment) you actually showed a need to be using them (4 interfaces in total, one I assume is a WAN interface, three interfaces remaining, you say you are not using the default VLAN, and you have two VLANs plus an ILO subnet - so you could just use physical interfaces). dot1Q VLAN trunks on your interfaces is a good design, especially if you might want to add later VLANs to the design...Hello Giles,I am grateful for your concern regarding my ip-design. We are however content with it and we don’t have any plans to change it. I need VLAN either configured in the switch or in the machine and I prefer to configure it in the machines. All interfaces are VLAN separated in the same switch infrastructure, this is quite common for new fabric switches which are extendable (hence the VLAN1, VLAN2 and VLAN10) The ILO interface is just named ILO, it has nothing to do with integrated lights out from HP other than that we have some servers connected on VLAN1 (default VLAN) which can remotely managed through their ILO.If I read you correctly it seems like the VLANs are creating a problem with the routing in pfSense? If this is the case I guess I can configure the switches instead but I am confused why this should be a problem.Can anyone shed some light on this topic? Kindest regards, Niklas
VLANs complexify your needed configuration, and might be where other admins could trip up.
Might be good to have a look at your routing table, on the diagnostics menu in the Web interface.
-- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7584 634135 http://www.coochey.net http://www.netsecspec.co.uk [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
