Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 5 subscribers
  • Views 20515 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

Configuring Vlan beetween Tplink TL-SG108E and Sophos UTM home V9

emanueleanni

hi all,

i have a few problems with the configuration of a vlan beetween sophos utm home and the tplink switch.

my sophos has two ethernet interface, one is for ppoe and the other for the local network and the vlan, i set the vlan id at 100 and do the same in the switch tplink, putting the port connected to sophos eth 2 in tagged and the others untagged.

I connect my laptop set the ip to the class of the vlan and when i try to ping my utm it doesn't respond and i can't even ping my modem and surfing internet.

what i'm doing wrong? is the switch not compatible with the vlan methods of sophos or i miss something?

The vlan i created is 101 and it's ip address is 192.168.10.254/24.

Thanks in advice



This thread was automatically locked due to age.
Parents
  • 0
    Emanuel,
    i suspect you have set the switch wrongly or have a misconception about vlans, let's recap:

    on UTM side:
    1) You have a LAN interface untagged, let's say eth2 i think with a certain IP address(different from the vlan)
    2) you have a ethernet VLAN on the same eth2 with tag 100 and 192.168.10.254/24 (why do you say you've created 101 if before that you say you have 100)

    on the switch:
    1) the port connected to the sophos eth2 needs to be set for tagged VLAN 100 and also untagged as well(for regular lan, usually vlan id 0).
    2) simply putting whatever IP belongs to the VLAN won't work, vlans dont work like that. For the ports that connect to computers, you have to decide wheter they belong to a specific vlan or are tagged as well, for example:
    you want port 8 to be vlan 100, then you have to set that port as untagged member of vlan 100 (it was 0 before), that port WONT be able to access the other VLAN.
    OR you want to chose which vlan to access because your NIC in the PC/notebook has VLAN tagging capability, then you set that port exactly as the one for the UTM (untagged0, tagged 100), then changing the properties of your NIC in windows you chose which VLAN to access, if you set 100 it will access 100, if you don't put anything it will go to 0)
Reply
  • 0
    Emanuel,
    i suspect you have set the switch wrongly or have a misconception about vlans, let's recap:

    on UTM side:
    1) You have a LAN interface untagged, let's say eth2 i think with a certain IP address(different from the vlan)
    2) you have a ethernet VLAN on the same eth2 with tag 100 and 192.168.10.254/24 (why do you say you've created 101 if before that you say you have 100)

    on the switch:
    1) the port connected to the sophos eth2 needs to be set for tagged VLAN 100 and also untagged as well(for regular lan, usually vlan id 0).
    2) simply putting whatever IP belongs to the VLAN won't work, vlans dont work like that. For the ports that connect to computers, you have to decide wheter they belong to a specific vlan or are tagged as well, for example:
    you want port 8 to be vlan 100, then you have to set that port as untagged member of vlan 100 (it was 0 before), that port WONT be able to access the other VLAN.
    OR you want to chose which vlan to access because your NIC in the PC/notebook has VLAN tagging capability, then you set that port exactly as the one for the UTM (untagged0, tagged 100), then changing the properties of your NIC in windows you chose which VLAN to access, if you set 100 it will access 100, if you don't put anything it will go to 0)
Children
No Data
Unfiltered HTML