[pfSense Support] snmp on pfsense 2.0

2010-10-24 Thread mayak-cq
hi chris, hi all,

i have two networks connected together with openvpn (pfsense on each
side -- 1.23 on the left side and 2.0 on the right).

i have a zenoss server on each side and each monitors devices on both
left and right sides. the left side is working perfectly as is the right
(in terms on snmp queries). the 2.0 side can monitor the 1.23, but not
the inverse ... appears that snmp queries comming from the 1.23 to the
2.0 don't make it to the lan interface correctly.

can anyone give some guidance?

thanks

m


-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



[pfSense Support] OpenVPN multi-wan in 2.0 - local port re-use?

2010-10-24 Thread Adam Thompson
Using 2.0 from a few days ago…

In the OpenVPN setup, I can (must) choose which interface each OpenVPN server 
is listening on.  I must also choose a local port number to bind to.

 

If I’m binding a specific port to a specific interface, why can’t I reuse the 
same port# on another interface?

(I tried, the gui complains that the local port is already in use.  Which is 
true, but – I think – shouldn’t matter if it’s bound to specific interfaces.)

 

Thanks,

-Adam Thompson

athom...@c3a.ca

(204) 291-7950

 



Re: [pfSense Support] OpenVPN multi-wan in 2.0 - local port re-use?

2010-10-24 Thread Chris Buechler
On Mon, Oct 25, 2010 at 12:00 AM, Adam Thompson athom...@c3a.ca wrote:
 Using 2.0 from a few days ago…

 In the OpenVPN setup, I can (must) choose which interface each OpenVPN
 server is listening on.  I must also choose a local port number to bind to.



 If I’m binding a specific port to a specific interface, why can’t I reuse
 the same port# on another interface?

 (I tried, the gui complains that the local port is already in use.  Which is
 true, but – I think – shouldn’t matter if it’s bound to specific
 interfaces.)


The management interface, which binds to 127.0.0.1, also uses that
port, which can't be re-used. I'd rather work around that in a
different fashion in the future, but that's rife with possibilities
for introducing bugs, and it's not broken, so it's not going to change
for 2.0.

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



[pfSense Support] ssh and webConfigurator traffic shaping

2010-10-24 Thread st41ker

Hello,

I wondering is there is some convenient way to shape(prioritize) ssh  
webConfigurator's traffic in the pfSense 2.0?


--
Thanks,
St41ker.


-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org