VLAN

[grant4790]

could any of these settings be affecting it? or the fact that it is a hyper v vm? i mean that NIC port on the server is dedicated to just the VM and nothing else

[Seimus]

could any of these settings be affecting it? or the fact that it is a hyper v vm? i mean that NIC port on the server is dedicated to just the VM and nothing else

These should be at default in most case of the scenarios. No need to play with them

show mac address-table interface tenGigabitEthernet1/1/3
          Mac Address Table
-------------------------------------------

Vlan    Mac Address       Type        Ports
----    -----------       --------    -----
   1    1418.7762.dcff    DYNAMIC     Te1/1/3



Here is the mac address table table for the interface facing opnsense, I have the windows machine ip to 192.168.10.101 and pinging 10.1 continuously.

Well here we have the problem.

As you can see your MAC (VLAN inherits its MAC from parent) 14:18:77:62:dc:ff is seen only advertised under VLAN1 but not under VLAN10.

You should see here an entry for 14:18:77:62:dc:ff in VLAN10 as well. Thats the reason you can not ping, or reach at all the OPN GW, as from perspective of the Switch no device on VLAN10 is seen on the TRUNK port.

Regards,
S.

[grant4790]

Great we found the issue thank you for the help! But how do I fix it?

[Seimus]

Sadly I do not run my OPN  in Virtual setup, only as baremetal.

You will need to dig more into the VM configuration probably, or hopefully somebody who uses OPN as VM can help.


From network perspective aka Switch side, as long you have the port configured as TRUNK and Allow proper VLANs it should be OK.

Regards,
S.

[Seimus]

Maybe this will help?

https://www.youtube.com/watch?v=M8PLt5-dmoA

Also check the Hyper V documentation for VLAN and Trunking.

Regards,
S.

[netnut]

* Your Trunk ports are missing encap config

Code: [Select]

switchport trunk encapsulation dot1q

This command will not work per Interface on 3650 and other legacy switches. These command is for MLS switches.

3650 already by default supports 802.1Q and its the only encapsulation it supports by default.

I stand corrected. Last Cisco switch I touched was a 3750 a few decades ago , "switched" to another platform and never looked back...

I see the OP is in good hands with you!

[grant4790]

Thank you all for all your help! I am going to try that video I just watched it and it looks promising!! Thank you guys so much I will update you all when I get a chance!

[Seimus]

I stand corrected. Last Cisco switch I touched was a 3750 a few decades ago , "switched" to another platform and never looked back...

I see the OP is in good hands with you!

3750 was a good switch, basically a simple MLS, it was one of the first switches to support as well IPbase images and routing with possibility of multiple L2 encapsulations.

I see the OP is in good hands with you!

Well just a casual network guy here

Thank you all for all your help! I am going to try that video I just watched it and it looks promising!! Thank you guys so much I will update you all when I get a chance!

For sure let us know. Cause it seems you maybe are missing proper vSwitch configuration on the Hyper V.

Regards,
S.

[grant4790]

UPDATE: yes the video worked that was indeed the issue!!! however I have a new one now...

I messed up and changed the listening interface for the webgui I still have SSH however it seems like everything I change on there does not fix my issue does anyone know how to change the listening interface via SSH

[Seimus]

Glad it helped you so indeed you had miss-configured Hyper V.

In regards of Webgui access, ah those sweet beginner mistakes. Try this
https://docs.opnsense.org/troubleshooting/webgui.html

Otherwise you can rollback config to the last working one via ssh.

Regards,
S.

[grant4790]

gorgeous thank you! worked like a charm!

[Seimus]

Glad we were able to fix all your problems. If all is fixed please update your thread name with [SOLVED], lets keep this forum clean!

P.S. Always consult documentation, and check your MAC address tables on Switches and ARP tables on routers > Networking 101

P.P.S Migrate your NOT tagged OPNGW to a proper VLAN TAGGED GW so you can get rid of that VLAN1 and let it be. You have a nice switch capable to do VLANs so why not to use it.

Regards,
S.