TRENDnet VLAN Config

Segg

Executive Member
Joined
Feb 25, 2012
Messages
5,452
Reaction score
2,848
Location
FAOR
Howzit Everyone!
I'm having a splendid time trying to get a Trendnet TL2-FG142 SFC switch to play nicely with VLAN's :cautious:

VLAN's are configured on PFsense, and 2 of them are running fine on a D-Link switch, however this Trendnet switch is going to go swimming pretty soon, so I hope someone can provide some wisdom. Details about this switches configuration seem to be scarce.

Diagram.JPG

The switches config is below

Capture1.JPG


Capture2.JPG

Capture3.JPG
 
Config looks good :unsure: Is the D-link trunk port setup correctly?

Perhaps remove the dlink for testing
 
Checked the manual and config seems fine. Sometimes the terminology on these can be misleading but it looks ok.

What is the actual issue you are having?
Looks like you trying to get DHCP in the 192.168.11.0/24 range? What VLAN is that on?
Does the Trendnet have any layer 3 interfaces (SVI's?)
 
Checked the manual and config seems fine. Sometimes the terminology on these can be misleading but it looks ok.

What is the actual issue you are having?
Looks like you trying to get DHCP in the 192.168.11.0/24 range? What VLAN is that on?
Does the Trendnet have any layer 3 interfaces (SVI's?)

Long story short, when I assign VLAN 11 (192.168.11.0/24) or any other VLAN to port 1 I don't get any IP addresses assigned by the DHCP server on PFsense, or any network connectivity within that specific VLAN.

If I leave the configuration as below, the test box will be assigned an IP as per the regular LAN (192.168.0.0/24)

Capture4.JPG

The second I adjust it to the below config, I lose all connectivity to my test box, and it is unable to obtain an IP address or communicate on the network.

Capture3.JPG

I'm not 100% sure if the switch has SVI's, but it does have a function I assume is similar (they call it private VLAN) but I haven't played with that.

I'm going to have a closer look at the D-Link in the morning, maybe its dropping the tags on the port as the data passes through.... :unsure:
 
What does the config on the Dlink look like?
Does DHCP on VLAN 11 work on there?

It seems like its stripping the VLAN / retagging it on VLAN1

The issue is probably on the DLINK
 
What does the config on the Dlink look like?
Does DHCP on VLAN 11 work on there?

It seems like its stripping the VLAN / retagging it on VLAN1

The issue is probably on the DLINK

You are correct!

First thing I did this morning was plug in a "dumb" switch between the D-link and the TRENDnet, and immediately the trendnet worked as configured (On port 1) The D-link seems to be stripping the VLAN tags instead of passing them on

Now to investigate why.....

The D-Link doesn't have the best interface to deal with VLAN's, they are very port centric

Capture5.JPG
 
Last edited:
Cool! Got it sorted on the D-Link

I had to manually add each VLAN and "bond" the trunks on the D-Link switch

Basically, PFsense is coming in on port 1, and the TRENDnet is going out on port 23

The terminology on this switch is the confusing part.
Untagged = access port
Tagged = trunk

Capture6.JPG
 
Last edited:
Now the TP-Link is still giving issues :cautious:

Earlier I was suddenly able to obtain 192.168.11.10 on port 1, but nothing on ports 2-7.
Now nothing is working, regardless if I use the "dumb" switch or the D-Link

God this is frustrating
 
on the TP link is there some kind of logging or monitoring where you can see what mac addresses you are learning on each port?
This might help tell you what is happening.

Give yourself a static IP and see if you can ping the DHCP server through the switch
 
on the TP link is there some kind of logging or monitoring where you can see what mac addresses you are learning on each port?
This might help tell you what is happening.

Give yourself a static IP and see if you can ping the DHCP server through the switch

Thanks I'll give this a try, I'll probably end up bringing the switch home with me on the weekend
 
Okay I finally got it working!

The issue turned out to be with the mode the router had set the SFP modules to.... I was thinking to myself, why are the copper ports letting traffic pass through without an issue, but the SFP ports aren't?

So then I changed the speed configuration from 1000 to auto and bam, everything started working :cool:

This is frustrating, as the port status indications were all normal the entire time! :mad:

Anyway, the configuration is all below if it helps anyone in future

Capture2.JPG


Capture1.JPG

Capture3.JPG
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X