[pfSense-discussion] problem with vlans
I'm running 0.86 on a generic pc with 3 x dual FE cards. Similar errors with 0.85.2 as well. When I configure vlans, I get the following errors : ifconfig: interface vlan0 does not exist ifconfig: interface vlan0 does not exist ifconfig: interface vlan1 does not exist ifconfig: interface vlan1 does not exist The vlans I defined are numbered 20 and 30. In the system logs I get the following error : php: : There were error(s) loading the rules: pfctl: DIOCSETSTATUSIF - The line in question reads [ DIOCSETSTATUSIF]: and this too : Warning: implode(): Bad arguments. in /usr/local/www/fbegin.inc on line 50 The pertinent config : - interfaces - lan iffxp2/if ipaddr192.168.199.254/ipaddr subnet24/subnet media / mediaopt / bandwidth100/bandwidth bandwidthtypeMb/bandwidthtype /lan - wan iffxp0/if mtu / ipaddrdhcp/ipaddr subnet / gateway / blockprivon/blockpriv dhcphostname / media / mediaopt / bandwidth100/bandwidth bandwidthtype / spoofmac / schedulertypepriq/schedulertype /wan - opt1 iffxp3/if descrM_server/descr bridge / enable / bandwidth100/bandwidth bandwidthtypeMb/bandwidthtype ipaddr192.168.200.254/ipaddr subnet24/subnet gateway / spoofmac / mtu / /opt1 - opt2 iffxp1/if descrFE_Server/descr bridge / enable / bandwidth100/bandwidth bandwidthtypeMb/bandwidthtype ipaddr172.100.100.254/ipaddr subnet24/subnet gateway / spoofmac / mtu / /opt2 - opt3 iftl0/if descrOPT3/descr /opt3 - opt4 iftl1/if descrOPT4/descr /opt4 - opt5 descrOPT5/descr ifvlan0/if /opt5 - opt6 descrOPT6/descr ifvlan1/if /opt6 /interfaces - vlans - vlan iffxp1/if tag20/tag descrFE_Server_download/descr /vlan - vlan iffxp1/if tag30/tag descrFE_server_webserver/descr /vlan /vlans -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
Re: [pfSense-discussion] problem with vlans
At 04:38 PM 10/5/2005, you wrote: I'm running 0.86 on a generic pc with 3 x dual FE cards. Similar errors with 0.85.2 as well. When I configure vlans, I get the following errors : ifconfig: interface vlan0 does not exist ifconfig: interface vlan0 does not exist ifconfig: interface vlan1 does not exist ifconfig: interface vlan1 does not exist The vlans I defined are numbered 20 and 30. can you post the results of 'ifconfig -a'?
Re: [pfSense-discussion] problem with vlans
# ifconfig -a tl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:4d media: Ethernet autoselect (none) status: no carrier tl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:cd media: Ethernet autoselect (none) status: no carrier fxp0: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8972%fxp0 prefixlen 64 scopeid 0x3 inet 82.4.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:50:8b:68:89:72 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp1: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 172.100.100.254 netmask 0xff00 broadcast 172.100.100.255 inet6 fe80::250:8bff:fe68:8973%fxp1 prefixlen 64 scopeid 0x4 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp2: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.199.254 netmask 0xff00 broadcast 192.168.199.255 inet6 fe80::208:2ff:fede:cec4%fxp2 prefixlen 64 scopeid 0x5 ether 00:08:02:de:ce:c4 media: Ethernet autoselect (100baseTX) status: active fxp3: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.200.254 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::208:2ff:fede:cec5%fxp3 prefixlen 64 scopeid 0x6 ether 00:08:02:de:ce:c5 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 pflog0: flags=141UP,RUNNING,PROMISC mtu 33208 pfsync0: flags=41UP,RUNNING mtu 2020 pfsync: syncdev: lo0 maxupd: 128 # Hi Dan, ifconfig -a. Any idea what plip0 is ? Thanks -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
RE: [pfSense-discussion] problem with vlans
I think its for ip over parallel port (printer (LPT1)). -Original Message- From: Chun Wong [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 05, 2005 3:48 PM To: discussion@pfsense.com Subject: Re: [pfSense-discussion] problem with vlans # ifconfig -a tl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:4d media: Ethernet autoselect (none) status: no carrier tl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:cd media: Ethernet autoselect (none) status: no carrier fxp0: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8972%fxp0 prefixlen 64 scopeid 0x3 inet 82.4.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:50:8b:68:89:72 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp1: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 172.100.100.254 netmask 0xff00 broadcast 172.100.100.255 inet6 fe80::250:8bff:fe68:8973%fxp1 prefixlen 64 scopeid 0x4 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp2: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.199.254 netmask 0xff00 broadcast 192.168.199.255 inet6 fe80::208:2ff:fede:cec4%fxp2 prefixlen 64 scopeid 0x5 ether 00:08:02:de:ce:c4 media: Ethernet autoselect (100baseTX) status: active fxp3: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.200.254 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::208:2ff:fede:cec5%fxp3 prefixlen 64 scopeid 0x6 ether 00:08:02:de:ce:c5 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 pflog0: flags=141UP,RUNNING,PROMISC mtu 33208 pfsync0: flags=41UP,RUNNING mtu 2020 pfsync: syncdev: lo0 maxupd: 128 # Hi Dan, ifconfig -a. Any idea what plip0 is ? Thanks -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
Re: [pfSense-discussion] problem with vlans - with correct ifconfig -a
This looks good. Are you still reaching errors? Scott On 10/5/05, Chun Wong [EMAIL PROTECTED] wrote: Sorry guys, In my haste, I did the ifconfig -a after I had restored the previous good config - doh! fxp1 is my dmz which I would like to vlan into different subnets fxp0 is my wan fxp2 is my lan fxp3 is my lan 2 tl0 is for my wlan subnet tl1 is spare This is the correct one : login as: admin Using keyboard-interactive authentication. Password: *** This is pfSense version 0.86 - pfSense *** LAN - fxp2 - 192.168.199.254 WAN - fxp0 - dhcp OPT1 - fxp3 - 192.168.200.254(M_server) OPT2 - fxp1 - 172.100.100.254(FE_Server) OPT3 - tl0 - (OPT3) OPT4 - tl1 - (OPT4) OPT5 - vlan0 - (OPT5) OPT6 - vlan1 - (OPT6) pfSense console setup *** 0) Logout (SSH only) 1) Assign Interfaces 2) Set LAN IP address 3) Reset webGUI password 4) Reset to factory defaults 5) Reboot system 6) Halt system 7) Ping host 8) Shell 9) PFtop 10) Traffic Logs Enter an option: 8 # ifconfig -a tl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:4d media: Ethernet autoselect (none) status: no carrier tl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:cd media: Ethernet autoselect (none) status: no carrier fxp0: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8972%fxp0 prefixlen 64 scopeid 0x3 inet 82.4.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:50:8b:68:89:72 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp1: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8973%fxp1 prefixlen 64 scopeid 0x4 inet 172.100.100.254 netmask 0xff00 broadcast 172.100.100.255 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp2: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.199.254 netmask 0xff00 broadcast 192.168.199.255 inet6 fe80::208:2ff:fede:cec4%fxp2 prefixlen 64 scopeid 0x5 ether 00:08:02:de:ce:c4 media: Ethernet autoselect (100baseTX) status: active fxp3: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.200.254 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::208:2ff:fede:cec5%fxp3 prefixlen 64 scopeid 0x6 ether 00:08:02:de:ce:c5 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 pflog0: flags=141UP,RUNNING,PROMISC mtu 33208 pfsync0: flags=41UP,RUNNING mtu 2020 pfsync: syncdev: lo0 maxupd: 128 vlan0: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 20 parent interface: fxp1 vlan1: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 30 parent interface: fxp1 # --- Ursprüngliche Nachricht --- Von: Scott Ullrich [EMAIL PROTECTED] An: discussion@pfsense.com Betreff: Re: [pfSense-discussion] problem with vlans Datum: Wed, 5 Oct 2005 16:51:40 -0400 Yes, please make sure they are assigned correctly. If they are let me know and I'll dive into the code. Scott On 10/5/05, Dan Swartzendruber [EMAIL PROTECTED] wrote: if you did create the vlans, you don't seem to have assigned them as interfaces. e.g. when you are in the console menu and see option #1 (assign interfaces), you want to assign vlan0 and/or vlan1 as LAN, or OPT or whatever. as is, you have the IP addresses assigned to the real interfaces. At 04:47 PM 10/5/2005, you wrote: # ifconfig -a tl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:4d media: Ethernet autoselect (none) status: no carrier tl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:cd media: Ethernet autoselect (none) status: no carrier fxp0: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8972%fxp0 prefixlen 64 scopeid 0x3
Re: [pfSense-discussion] problem with vlans - with correct ifconfig -a
the vlan0 and vlan1 interfaces don't have IP addresses, but the physical interface (fxp1) does. Mixing and matching real interfaces and vlan interfaces doesn't seem right... At 05:06 PM 10/5/2005, you wrote: This looks good. Are you still reaching errors? Scott On 10/5/05, Chun Wong [EMAIL PROTECTED] wrote: Sorry guys, In my haste, I did the ifconfig -a after I had restored the previous good config - doh! fxp1 is my dmz which I would like to vlan into different subnets fxp0 is my wan fxp2 is my lan fxp3 is my lan 2 tl0 is for my wlan subnet tl1 is spare This is the correct one : login as: admin Using keyboard-interactive authentication. Password: *** This is pfSense version 0.86 - pfSense *** LAN - fxp2 - 192.168.199.254 WAN - fxp0 - dhcp OPT1 - fxp3 - 192.168.200.254(M_server) OPT2 - fxp1 - 172.100.100.254(FE_Server) OPT3 - tl0 - (OPT3) OPT4 - tl1 - (OPT4) OPT5 - vlan0 - (OPT5) OPT6 - vlan1 - (OPT6) pfSense console setup *** 0) Logout (SSH only) 1) Assign Interfaces 2) Set LAN IP address 3) Reset webGUI password 4) Reset to factory defaults 5) Reboot system 6) Halt system 7) Ping host 8) Shell 9) PFtop 10) Traffic Logs Enter an option: 8 # ifconfig -a tl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:4d media: Ethernet autoselect (none) status: no carrier tl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:cd media: Ethernet autoselect (none) status: no carrier fxp0: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8972%fxp0 prefixlen 64 scopeid 0x3 inet 82.4.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:50:8b:68:89:72 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp1: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8973%fxp1 prefixlen 64 scopeid 0x4 inet 172.100.100.254 netmask 0xff00 broadcast 172.100.100.255 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp2: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.199.254 netmask 0xff00 broadcast 192.168.199.255 inet6 fe80::208:2ff:fede:cec4%fxp2 prefixlen 64 scopeid 0x5 ether 00:08:02:de:ce:c4 media: Ethernet autoselect (100baseTX) status: active fxp3: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.200.254 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::208:2ff:fede:cec5%fxp3 prefixlen 64 scopeid 0x6 ether 00:08:02:de:ce:c5 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 pflog0: flags=141UP,RUNNING,PROMISC mtu 33208 pfsync0: flags=41UP,RUNNING mtu 2020 pfsync: syncdev: lo0 maxupd: 128 vlan0: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 20 parent interface: fxp1 vlan1: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 30 parent interface: fxp1 # --- Ursprüngliche Nachricht --- Von: Scott Ullrich [EMAIL PROTECTED] An: discussion@pfsense.com Betreff: Re: [pfSense-discussion] problem with vlans Datum: Wed, 5 Oct 2005 16:51:40 -0400 Yes, please make sure they are assigned correctly. If they are let me know and I'll dive into the code. Scott On 10/5/05, Dan Swartzendruber [EMAIL PROTECTED] wrote: if you did create the vlans, you don't seem to have assigned them as interfaces. e.g. when you are in the console menu and see option #1 (assign interfaces), you want to assign vlan0 and/or vlan1 as LAN, or OPT or whatever. as is, you have the IP addresses assigned to the real interfaces. At 04:47 PM 10/5/2005, you wrote: # ifconfig -a tl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:4d media: Ethernet autoselect (none) status: no carrier tl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:cd media: Ethernet autoselect (none
Re: [pfSense-discussion] problem with vlans
Hmm, strange, no errors after I restored. I have gone on to set the ip address of the vlans. Dan, I have used virtual and physical interfaces on other firewalls (Nokia running CP NG), I treat the physical as vlan 1. If I get a chance, I'll try it again and see if I can repeat it. Regards Chun --- Ursprüngliche Nachricht --- Von: Dan Swartzendruber [EMAIL PROTECTED] An: discussion@pfsense.com Betreff: Re: [pfSense-discussion] problem with vlans - with correct ifconfig -a Datum: Wed, 05 Oct 2005 17:11:55 -0400 the vlan0 and vlan1 interfaces don't have IP addresses, but the physical interface (fxp1) does. Mixing and matching real interfaces and vlan interfaces doesn't seem right... At 05:06 PM 10/5/2005, you wrote: This looks good. Are you still reaching errors? Scott On 10/5/05, Chun Wong [EMAIL PROTECTED] wrote: Sorry guys, In my haste, I did the ifconfig -a after I had restored the previous good config - doh! fxp1 is my dmz which I would like to vlan into different subnets fxp0 is my wan fxp2 is my lan fxp3 is my lan 2 tl0 is for my wlan subnet tl1 is spare This is the correct one : login as: admin Using keyboard-interactive authentication. Password: *** This is pfSense version 0.86 - pfSense *** LAN - fxp2 - 192.168.199.254 WAN - fxp0 - dhcp OPT1 - fxp3 - 192.168.200.254(M_server) OPT2 - fxp1 - 172.100.100.254(FE_Server) OPT3 - tl0 - (OPT3) OPT4 - tl1 - (OPT4) OPT5 - vlan0 - (OPT5) OPT6 - vlan1 - (OPT6) pfSense console setup *** 0) Logout (SSH only) 1) Assign Interfaces 2) Set LAN IP address 3) Reset webGUI password 4) Reset to factory defaults 5) Reboot system 6) Halt system 7) Ping host 8) Shell 9) PFtop 10) Traffic Logs Enter an option: 8 # ifconfig -a tl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:4d media: Ethernet autoselect (none) status: no carrier tl1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:80:5f:a7:83:cd media: Ethernet autoselect (none) status: no carrier fxp0: flags=9943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8972%fxp0 prefixlen 64 scopeid 0x3 inet 82.4.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:50:8b:68:89:72 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp1: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::250:8bff:fe68:8973%fxp1 prefixlen 64 scopeid 0x4 inet 172.100.100.254 netmask 0xff00 broadcast 172.100.100.255 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active fxp2: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.199.254 netmask 0xff00 broadcast 192.168.199.255 inet6 fe80::208:2ff:fede:cec4%fxp2 prefixlen 64 scopeid 0x5 ether 00:08:02:de:ce:c4 media: Ethernet autoselect (100baseTX) status: active fxp3: flags=9843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.200.254 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::208:2ff:fede:cec5%fxp3 prefixlen 64 scopeid 0x6 ether 00:08:02:de:ce:c5 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 pflog0: flags=141UP,RUNNING,PROMISC mtu 33208 pfsync0: flags=41UP,RUNNING mtu 2020 pfsync: syncdev: lo0 maxupd: 128 vlan0: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 20 parent interface: fxp1 vlan1: flags=8842BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:50:8b:68:89:73 media: Ethernet autoselect (100baseTX full-duplex) status: active vlan: 30 parent interface: fxp1 # --- Ursprüngliche Nachricht --- Von: Scott Ullrich [EMAIL PROTECTED] An: discussion@pfsense.com Betreff: Re: [pfSense-discussion] problem with vlans Datum: Wed, 5 Oct 2005 16:51:40 -0400 Yes, please make sure they are assigned correctly. If they are let me know and I'll dive
Re: [pfSense-discussion] problem with vlans
At 05:30 PM 10/5/2005, you wrote: Hmm, strange, no errors after I restored. I have gone on to set the ip address of the vlans. Dan, I have used virtual and physical interfaces on other firewalls (Nokia running CP NG), I treat the physical as vlan 1. this is not nokia :) not saying it can't work, but i'm surprised if it does.
Re: [pfSense-discussion] problem with vlans
you're right, its me being defensive ;0) at the moment the vlans are working ok, even in my strange setup! now I am learning the way pfsense handles rules, esp. the implied ones. Cheers Chun Dan, I have used virtual and physical interfaces on other firewalls (Nokia running CP NG), I treat the physical as vlan 1. this is not nokia :) not saying it can't work, but i'm surprised if it does. -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
Re: [pfSense-discussion] problem with vlans
On 10/5/05, Chun Wong [EMAIL PROTECTED] wrote: now I am learning the way pfsense handles rules, esp. the implied ones. heh, that's something I plan on eventually providing more visibility into - we're just not there yet :) --Bill