I have the same issue in the latest stable version:
built on Thu May 10 15:59:52 CDT 2018
Has this issue been resolved?
You were already informed this issue had been resolved and asked to provide more details. This is not more details. Can we get more details please?
0_1537735102218_sg1000-system.log.zip [0_1537735068661_sg1000-system.log](Uploading 100%) My SG-1000 Config:
2.4.3-RELEASE-p1 (arm) built on Thu May 10 15:59:52 CDT 2018 FreeBSD 11.1-RELEASE-p10
WAN (wan) -> cpsw0 -> v4/DHCP4: 192.168.254.197/24 v6/DHCP6: fdcb:fd40:b23b:0:528c:b1ff:fec9:a9c2/64 LAN (lan) -> cpsw1 -> v4: 172.16.100.254/24 v6/t6: fdcb:fd40:b23b:4:528c:b1ff:fec9:a9c4/62 LAN100 (opt1) -> cpsw1.100 -> v4: 172.16.1.254/24 GUEST200 (opt2) -> cpsw1.200 -> v4: 172.16.200.254/24
All appliances were restored to factory defaults before testing.
For testing I set all filters as "Pass All", I also turned off:
Block private networks and loopback addresses
Block bogon networks
In my configuration I have UniFi Switch 24 POE-250W with uplink port set as TRUNK (Native VLAN1 and Tagged VLAN100,VLAN200). Tested client was connected to port with Untagged VLAN100.
I couldn't ping pfsense box from testing PC until I set promiscuous on cpsw1 interface.
I thought that there might be some configuration error of UniFi Switch, so I connected the tested PC directly to pfsense. I couldn't ping gw despite I forced a VLAN100 on the card.
That's why in my opinion these is an issue of the SG-1000. I know that it was fixed a year ago but all symptoms are the same. In the attachment you can find system log file
I just tested this. I cannot duplicate.
If it could help I can upload config file.
After upgrade to 2.4.4 the problem seems to have corrected itself.
2.4.4-RELEASE (arm) built on Thu Sep 20 09:33:19 EDT 2018 FreeBSD 11.2-RELEASE-p3
Start a new thread for your issue. It is not the same. Post your interface settings, output from
ifconfig -a, output from
etherswitchcfgand as much information about your version as possible (
pkg info -x pfSense, etc). This thread is not the same as your issue. Similar, perhaps, but not identical. Do not assume it is the same.