|
||||||||||
> WÅ‚odzimierz FrÄ…czek wrote: >> Hello >> >> I try to use m0n0nowall ver.1.21 but have troubles on begining. >> My first m0n0 NIC ( LAN ) - 192.168.0.20 >> I create VLAN ( parent interface - LAN ) and give address 10.0.0.20 ( >> OPT1 ) >> Next I link my PC ( my address 192.168.0.100 ) to LAN >> I can ping of course to LAN and after adding a trace to the routing table >> in my Windows to OPT1 too. >> But if I change my PC adress to 10.0.0.100 for example I can't ping >> nowhere ( OPT1, LAN ) >> Please explain me why ? >> >> WF >> > > Basic reason is that your PC has not been configured to understand/work > with 802.1q (VLANS). > > Your m0n0wall's VLAN interface, listening on 10.0.0.20, will only > respond to packets that are tagged with 802.1q information for the VLAN > you have configured. Your computer is sending NON-802.1q tagged ethernet > frames, and as such your m0n0wall is seeing them on its LAN interface, > and is probably dropping them, or just allowing them to pass (default > m0n0wall LAN rule is to allow all) ---------------- As I wrote I can ping to VLAN interface ( OPT1 ) under some circumstaces : 1. My PC adress : 192.168.0.100 2. My route table entry : route add 10.0.0.0 mask 255.255.255.0 192.168.0.20 I understand that in this case my PC send packet without 802.1q frame and neverthless VLAN interface answer me. By the way, if I change one of my NIC card ( INTEL PRO/100 VE ) property ( QoS packet tagging ) I still have the same problem. -------------------- > > You will need a switch that supports VLANS (802.1q) to begin with. > > Check out the following links for more information on VLANS: > > http://www.zyxel.com/support/supportnote/ves1012/app/8021q.htm > http://en.wikipedia.org/wiki/IEEE_802.1Q > > > -- > Bill Arlofski > Reverse Polarity > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > |