it could also be a bogus switch; it might not like you trying to run
tagged and untagged frames on the same port. I'd advise changing to use
vlan2, say, as your LAN and ensure all switch ports are marked untagged
vlan2, (or in cisco speak, in access mode, access vlan 2, and nonegotiate).
yes, play with the Interfaces-Assign menus
Paul,
Thanks for the confirmation.
In the VLAN Tab, I have:
Interface VLAN tagDescription
em2 50 NegriBossi
In the Interface Assignment Tab, I have:
Interface Network port
LAN em0
WAN bge0
OPT1
On 28/09/09 15:20, Joseph L. Casale wrote:
...
Interface VLAN tagDescription
em2 50 NegriBossi
In the Interface Assignment Tab, I have:
Interface Network port
LAN em0
WAN bge0
OPT1em1
OPT2VLAN 50 on em2
you
I have a vlan (50) setup who's parent interface is Opt2. This
parent interface is setup with a static ip of 192.168.1.1/24
and is plugged into a switch A that has that has this port
tagged into the specific vlan id of 50 as well.
Switch A has a fibre connection to another switch B and the
ports
On Fri, Sep 25, 2009 at 6:05 PM, Joseph L. Casale jcas...@activenetwerx.com
wrote:
I have a vlan (50) setup who's parent interface is Opt2. This
parent interface is setup with a static ip of 192.168.1.1/24
and is plugged into a switch A that has that has this port
tagged into the specific
Does the vlan interface have an allow rule?
You said opt2 does, but what about your vlan interface
Yes, only Opt2, I didn't know you could create rules for
the vlan interface itself? R u sure you can do this?
Thanks!
jlc
-
To
(sorry for top replying but I have gotten it to work and share my 5
cents here)
Thank you for your hints.
The problems with my setup was that pfSense GUI defaults to /32-netnask
when setting a VLAN ip address. I did not notice this at first and the
packages did not get routed as I wanted.
Fredrik Rambris wrote:
Hello
Searched through the list and found many posts on VLAN. To my knowledge
I have done what I think is correct but packages wont go through. I can
see in the pfSense logs that packages do get in on the right VLAN
interface but that's about it.
bge0 is WAN
bge1
Hi,
Le 15 oct. 08 à 14:20, Paul Mansfield a écrit :
Fredrik Rambris wrote:
Hello
Searched through the list and found many posts on VLAN. To my
knowledge
I have done what I think is correct but packages wont go through. I
can
see in the pfSense logs that packages do get in on the right
Hello
Searched through the list and found many posts on VLAN. To my knowledge
I have done what I think is correct but packages wont go through. I can
see in the pfSense logs that packages do get in on the right VLAN
interface but that's about it.
bge0 is WAN
bge1 is LAN
I have defined two
What version of pfSense are you running? 1.2-Release? 1.2.1-RC?
Fredrik Rambris wrote:
Hello
Searched through the list and found many posts on VLAN. To my
knowledge I have done what I think is correct but packages wont go
through. I can see in the pfSense logs that packages do get in on the
Hello Gary,
On C3550 Fa0/1 try switchport trunk allowed vlan 201,202 . Then see
the output sh interfaces trunk . You should see if the Fa0/1 is
trunking correctly with dot1Q encapsulation.
Cheers,
- Matej
Gary Buckmaster wrote / napísal(a):
What version of pfSense are you running?
look closely... switchport mode access command is absent
I use this way... and works ok.
interface fastethernet 0/x
switchport mode access
switchport access vlan
Regards
On Tue, Oct 14, 2008 at 4:39 PM, Matej Duracka [EMAIL PROTECTED] wrote:
Hello Gary,
On C3550 Fa0/1 try
13 matches
Mail list logo
