News: This forum is now permanently frozen.
Pages: [1]
Topic: multivlan vlan1 problem  (Read 1390 times)
« on: February 04, 2010, 11:40:46 »
manspan *
Posts: 10

I' m using m0n0wall two years now and it is really a great firewall.
Last month due to network changes I had to replace my main switch (Nortel) with a new one (HP procurve),
so I decided to build m0n0 from the beginning using the latest release.

I have
one wan interface 195.xx.xx.xx
one lan interface 192.168.1.1
one DMZ interface 195.xx.xx.xx
and about 10 VLANs (using my dot1.q NIC I used for lan)
My old m0n0 worked just fine, but now I have problems:

when a packet from VLAN1 (10.50.11.xx) is blocked the firewall-log looks like that:
ifsource
LAN10.50.11.32

The right log should be:
ifsource
VLAN110.50.11.32

It's not only a log problem. The whole behavior is bizarre. It seems like LAN and VLAN1 is mixed up...
All the other VLANs are working with no problem.
I've tried any possible configuration on m0n0 and my new switch but still the same. Any ideas?
« Reply #1 on: February 10, 2010, 08:54:10 »
manspan *
Posts: 10

It might be the gigabit NIC I use.
« Reply #2 on: February 10, 2010, 11:17:43 »
brushedmoss ****
Posts: 446

What is your switch port configuration ?  some switches have the concept of a 'native' vlan, and packets sent from that vlan don't get tagged.

i.e. setting a native vlan on the switch to vlan 1, means packets received on that port with no vlan tag, will be destined for vlan 1, and packets sent out that were sourced from vlan 1 , leave with no vlan tag.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines