Bug #2971
closed
Can not get SNMP information Use IPSENSE connection
0%
Description
To connect a PFSENSE When I use IPSEC
I can not get SNMP information when the SNMP Service "Bind Interface"select ALL
But I chose a LAN can be normal to receive information
Please fix this problem
Thank you
My PFSESNE IS
2.0.3-RELEASE (i386)
built on Fri Apr 12 10:22:57 EDT 2013
Files
| bad.PNG (57.6 KB) bad.PNG | SNMP Service chose "Bind Interface" select ALL | ||
| ok.PNG (64.3 KB) ok.PNG | SNMP Service chose "Bind Interface" select LAN | ||
| noanswer.PNG (79.4 KB) noanswer.PNG | ERROR |
Updated by Jim Pingle over 11 years ago
- Status changed from New to Rejected
The binding option is the correct workaround.
Failing that, see: http://doc.pfsense.org/index.php/Why_can%27t_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewall_itself_over_IPsec_VPN%3F
Nothing more can be done.
Updated by X.Z. Lin over 11 years ago
- File noanswer.PNG noanswer.PNG added
I tested PING normal
Firewall through
SNMP data is not ALL
This is normal?
[2.1-BETA1][root@pfsense.mec.hc]/root(3): ping S 172.30.34.254 192.168.139.254 192.168.139.254 ping statistics ---
PING 192.168.139.254 (192.168.139.254) from 172.30.34.254: 56 data bytes
64 bytes from 192.168.139.254: icmp_seq=0 ttl=64 time=45.884 ms
64 bytes from 192.168.139.254: icmp_seq=1 ttl=64 time=44.356 ms
64 bytes from 192.168.139.254: icmp_seq=2 ttl=64 time=44.798 ms
64 bytes from 192.168.139.254: icmp_seq=3 ttl=64 time=45.990 ms
64 bytes from 192.168.139.254: icmp_seq=4 ttl=64 time=45.901 ms
^C
--
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 44.356/45.386/45.990/0.676 ms
[2.1-BETA1][root@pfsense.mec.hc]/root(4):
d:\>ping 192.168.139.254
Ping 192.168.139.254 (使用 32 位元組的資料):
回覆自 192.168.139.254: 位元組=32 時間=45ms TTL=63
回覆自 192.168.139.254: 位元組=32 時間=45ms TTL=63
回覆自 192.168.139.254: 位元組=32 時間=45ms TTL=63
回覆自 192.168.139.254: 位元組=32 時間=46ms TTL=63
192.168.139.254 的 Ping 統計資料:
封包: 已傳送 = 4，已收到 = 4, 已遺失 = 0 (0% 遺失)，
大約的來回時間 (毫秒):
最小值 = 45ms，最大值 = 46ms，平均 = 45ms
d:\>
Updated by Jim Pingle over 11 years ago
The ticket system is not a place for an in-depth discussion on the topic. Please start a forum thread if you need more information.
It is normal due to how the OS sources UDP replies when multiple interfaces exist on the same system. Other protocols do not behave this way, only UDP.
Updated by X.Z. Lin over 11 years ago
I know you want to discuss issues go to the forum
But I think this should be a BUG
Select ALL can not get the information to choose LAN can
Road ALL does not mean that all I recognized this is not a bug, but my question
Thank you!
Updated by Jim Pingle over 11 years ago
It is not a bug in pfSense. It is an known, expected, and documented behavior of FreeBSD and other Operating Systems with UDP traffic sourcing on multi-homed systems. If you want to take up the issue with FreeBSD, feel free, but there is nothing we can do about that. If you need more information on the issue, it belongs in the forum.
Updated by X.Z. Lin over 11 years ago
OK!Thank you
When the last time you told
I have simultaneous release to the forum to ask!
Updated by X.Z. Lin over 11 years ago
Updated by X.Z. Lin over 11 years ago
BTW.
So ALL easily lead to misunderstanding, I guess I will not be the last person to raise this issue!