Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ojessie

#1
fixed. It was a cable mismatch ... sorry for bothering you.
#2
Hi,
my story actually starts here https://forum.opnsense.org/index.php?topic=37114.0 in the meantime many things are working und my knowledge is fast increasing ... but still I'm having a problem which I cannot understand.

Setup:
opn subnet (vlan 40) 192.168.40
to
Cisco SG200-26 Port 25 in (Trunk: 10T,20T30T,40T50T100T,1PVID001): Port 8 out (Trunk 30T,40T,1001UP)
to
Cisco SG200-08 Port 1 in (Trunk 30T,40T1001UP): Port 2 out (Access 40U)
everything works!
By just connecting it to another pysical port (Port 8 on Cisco26 wich was copied from the working port 7) all vlans are gone.
the remarkable thing is that when connected on the working port 8 th switch registers itself in 192.168.1.x on the copied not working port 7 it registers in 192.168.40.x
Thats is the reason why its not working, But why?

Any hint / advice, whatsoever is highly appreciated.
Thanks
#3
Hi, I'm not going for the simple things ;-) ... I'm running 4 SSID on Tomato. It's already working but I'm afraid the HW of my Asus N66 is not capable to handle it. It seems very instable sometimes I'm not able to login. To you have any experience here?
#4
oh my goodness ;-) it's working!!! This is for all the beginners more or less on the same level as I'm.
I believed the OPS is kind of broadcasting all Vlans in the network and on the access port you "just" have to specify which Vlan should get access. This is wrong.

What is working in my case, hopefully it's kind of right and secure, the port towards the OPS needs to be specified as trunk including all the Vlans which are used in this switch. On the "access" port where the PC is connected this sport needs to be configured with the unique Vlan ID and as access port defined.

thanks @cookiemonster for your support ... next challange is to get my Wlan AP with Tomato connected.
#5
I'm afraid, I think I'm heading in the totally wrong direction ... or the more I tig into Vlan the more confused I get.
Just read the end devices like a PC cannot handle / understand Vlan (tagged information on a swich)? Is this true?
#6
the nics in my opnsense hw are Intel I210 ... so I believe there is not the problem
#7
the remarkable thing is, after a while, I'm getting the private IP 169.254.10.205/16 .... any clue?
#8
...that's why I think, OPS is not publishing the Vlan to the switch
#9
Highly appreciate your support!
Well the problem is that VLan is not working.
I followed your recommend thread but still the same.
Changed the default to 1001 and the tagged Vlan is 10. So on port GE 8 (see the picture) I'm getting the IP from my "standard" LAN 192.168.1.xx. When excluding the default 1001 from GE 8 I'm getting no connection to Vlan VID 10 / HDCP on OPS.
Any clue?
#10
dump question ... is it possible that my nic's are not supporting Vlan? I'm running opnsense on a relatively old ipfire hw. How is it possible to check?
#11
opnsense new flash ... starting from scratch ... I'm doing a fundmental failure. As before everything works, but no VLAN. Anyone is having an idea what I'm doing wrong?
#12
General Discussion / Vlan / HTPC / Cisco G200 no access
November 20, 2023, 02:54:48 PM
Hi,
sorry I'm ashamed to ask because it should be so simple and straight forward and I'm convinced the answer to my problem is several times mentioned in the forum. But obviously I'm not having the knowledge yet to fix my problem.
Since years I'm running my opnsense without any problem, flat structured. But as threats are increasing and with a bunch of IoT devices I thought it's time to improve and add some VLANs.
It's very straight forward set-up for a beginner ....
- standard LAN 192.168.1.1
- Vlan 192.168.100.1 assigned to the LAN
- vlan configured VID 100 including HTPC
- Cisco SG200 26 port GE8 configured VID 100
and no way to get this up and running. Any help ishighly appreciated. As mentioned in the beginning, I don't even know it the problem is at Cisco or opnsense.

thanks, any hint / help what so ever is highly appreciated.
#13
du bist zumindest schon um einige Schritte weiter ... ich schaffe es nicht, dass sich die FB VoIP registriert ... wie gesagt Registrierung ist nur möglich wenn die FB direkt hinter dem A1 Modem hängt.
#14
Der einzige Unterschied der mir auffällt ist dein Port Forward startet mit einem Doppel Pfeil meine mit einem Pfeil nach rechts? Kann es das sein? und falls ja was bedeutet das und wie kann ich das ändern.
#15
Update das sind meine aktuellen udp States

all    udp    10.0.0.1:5060 -> 193.81.4.68:5060    MULTIPLE:MULTIPLE    
all    udp    127.0.0.1:5060 (193.81.4.68:5060) <- 192.168.1.6:5060    NO_TRAFFIC:SINGLE    
all    udp    192.168.1.1:5060 -> 192.168.1.6:5060    MULTIPLE:MULTIPLE

10.0.0.1 ist die OPNSense, WAN
127.0.01 und 192.168.1.1 OPNsense LAN
192.168.1.6 FB