Jesse Vollmar wrote:
On Wed, Aug 26, 2009 at 8:55 PM, Evgeny Yurchenko<evg.yu...@rogers.com> wrote:
May we see ifconifg and netstat -rn ?
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
I think I know why... there is no route to that on particular vlan!
all the other vlans had routes created for them but the vlan100 did
not.
$ netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 67.38.60.77 UGS 0 66215 ng0
10/24 link#1 UC 0 0 em0
10.0.0.10 00:50:8d:94:0c:36 UHLW 1 4 em0 1160
10.0.0.11 00:50:8d:94:0c:37 UHLW 1 349 em0 1164
10.0.0.15 link#1 UHLW 1 9 em0
10.0.0.250 00:01:2e:1d:2d:cb UHLW 1 2059 em0 1195
10.0.1/24 link#13 UC 0 0 vlan4
10.0.101/24 link#10 UC 0 0 vlan1
10.0.101.252 00:24:2c:24:ec:b4 UHLW 1 446 vlan1 908
10.0.102/24 link#11 UC 0 0 vlan2
10.0.103/24 link#12 UC 0 0 vlan3
66.188.33.184/30 link#3 UC 0 0 em2
66.188.33.185 00:1f:e1:4b:d7:f4 UHLW 1 275 em2 1196
99.23.221.158 lo0 UHS 0 0 lo0
127.0.0.1 127.0.0.1 UH 0 0 lo0
Can't see anything wrong here. Double check your default gateways
(routing) on workstations connected to these two vlans.
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org