Using SFP port as WAN2 on 100D

[daccu]

Here' s my situation: I set up the WAN2 interface to prepare for a secondary Internet connection. The new Internet connection turned out to be fiber, so now I' m going to use an SFP in Port 15 on the 100D for the secondary WAN connection. What I' m wanting to do is assign port 15 to the WAN2 interface, so essentially the WAN2 and Port 15 physical ports would both behave in exactly the same way: if I wanted to use a copper connection I' d plug into WAN2 and if I wanted to use fiber I' d plug in to the SFP on Port 15. My questions are: 1. What is the best way to go about this? I would have assumed that I could just add Port 15 to the WAN2 interface/zone but it doesn' t look like it works that way. 2. Are there any security concerns with using port 15 rather than the dedicated WAN2 port for an Internet connection?

[rwpatterson]

You could create a zone (But I wouldn' t call it WAN2, maybe WAN-SFP) and place port 15 into it. Then all policies would be to WAN-SFP. The labels are for human happiness. Any port can server any purpose: DMZ2, internal 2, wanx, etc.

[netmin]

For the secondary ISP being connected either via SFP or copper (not both), I would try to configure it just on port15 too as it should be a shared media - copper port15 / SFP port15.

[Phill_Proud]

Just start thinking of port15 as WAN2. It' s just a name. Put the name of the secondary ISP in the alias.

[ede_pfau]

If you use a zone, put both WAN2 and port15 into it, of course. One advantage of a zone is that the zone name completely replaces the port name whereas an alias is showing up as a suffix (like in ' port15 (WAN2)' . Just because of this I' ve used a zone with just one port in it. If port15 is a combo port then pushing in an SFP should disconnect the copper port (transceiver takes precedence). In combination with ' zone renaming' IMHO the most elegant solution. if only more fixes were solvable as easy as this...