Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 5371 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ISP required VLAN Tag to connect

Mark Stoker

Our ISP requires us to supply a VLAN TAG on the WAN connection. 

From other discussions I have seen that I need to create a VLAN onto the interface. This I have done and it now seems to connect ok. However I'm not sure what I need to configure for the actual interface PORT - I have used LAN and DHCP - is this correct.

 

Using this configuration I cannot access the local LAN remotely - do I need a FIREWALL RULE as well ?

Thanks

 

Mark



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Deo Angelo Lim

    I think I have figured this out.

     

    I need to set the Physical port to WAN and not LAN. It then connect to the ISP and behaves like a 'normal' WAN interface except it has a VLAN tag. 

     

    What confused me is the WAN Link manager was showing the VLAN interface as connected but the DHCP WAN Interface on the same port as NOT CONNECTED - apparently this is how it should be.

  • 0 in reply to Mark Stoker

    Hi,

    Good day!


    Good for you mate. Anyways on the WAN link manager part. You may change the Fail over rules on your DHCP WAN. It might not satisfied to the condition(Default rule is to ping the gateway) .


    Warm Regards,

    Deo