similar to: NUT HCL List

Displaying 20 results from an estimated 1000 matches similar to: "NUT HCL List"

2012 Jan 31
6
Shorewall and sshdfilter
Hi All! Been quite a few years and lots of water under the bridge but here I am back! I have a customer that has now decided they need a bit more bandwidth over and above their fixed line! They are not in a good area for ADSL because of copper theft and being a bit to far from the closest DSLAM! They have installed a wireless link and I have made certain that put it behind my simple iptables
2012 Feb 19
3
Shore wall and multi ISPs and ip addresses
Hi All! I only ever have complex setups. Customer site has a dedicated leased line from their ISP terminating on a Cisco router. Router is configuered with the first usable address on a /28 network - 196.x.y.73. The linux firewall is configured with the remaining 5 ip''s, 196.x.y.74 to 196.x.y.78 and 79 as the broadcast. Sounds normal but here is the twist. The primary or first ip
2011 May 17
3
Powercom issues in NUT (was: PowerCom BNT2000AT ups on nut 2.6.0 - second try)
Dino, Alexey, there are a number of users suffering issues with your Powercom devices. Could you (Dino, and Keven if possible) please have a look at the below one, from Angela, and check for a fix? I've scheduled to release 2.6.1 next week, and having that fixed is part of the list. 2011/5/16 Angela Williams <angierfw at gmail.com> > Hi All > > On Friday 13 May 2011 at
2012 Dec 04
5
Network traffic tool
Hi everybody, I have my firewall with shorewall runing and I dont have a proxy. I would like to know which tool can I use to log my web traffic from my users. I have ntop working but I dont think this tool helps me on this. Any suggestion? Thanks ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
2011 May 13
1
PowerCom BNT2000AT ups on nut 2.6.0 - second try
Hi! Normally nut was just worked and worked for me! Not this time though! Distro is Gentoo withe latest nut-2.6.0 emerged today. Linux kernel version is 2.6.36 UPS is PowerCom BNT2000AT "Driver" is powercom ups.conf looks like this! Okay so APC1 is not and APC! [APC1] driver = powercom type = BNT port = /dev/ttyS1 numOfBytesFromUPS = 16
2012 May 31
5
Shorewall + squid + multi isp
Hello all, I''m reading the nice documentation about shorewall with multi isp. And I wonder about squid (non transparent) and shorewall Can I use on same machine, squid with ldap ident, dansguardian, and shorewall with multi-isp (four or five) ? Perhaps there is a problem because squid mask source IP, shorewall can maintain and load balance sessions for the same source IP ? Thanks Fred
2013 Aug 22
1
SNMPv3
Updating an old thread. History here. http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html On Fri, 1 Feb 2013, Tim Rice wrote: [snip] > > In all my testing I discovered the APC AP9630 is kind of flaky when >
2014 Mar 31
2
AP9630 AES Support
Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the AES protocol, though in my set up it works with
2014 Apr 04
0
AP9630 AES Support
On Mar 30, 2014, at 10:39 PM, Shade Alabsa wrote: > Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the
2016 Dec 20
2
NUT Client shuts down when performing runtime calibration on APC UPS
Hello, I am using an APC UPS (Smart-UPS 2200 RM) to secure my SAN. The SAN runs on FreeBSD 9.1-RELEASE-p5 and is using NUT 2.6.5 version 2. Since the UPS has also a Network card AP9630 I am using the snmp-ups driver to connect the SAN to the UPS for signaling. Last week I need to change the battery pack and then I needed to perform a runtime calibration. I used the web interface of the AP9630
2014 Feb 19
0
snmp-ups shutdowns
Hi Jim, On Tue, 18 Feb 2014, Jim Klimov wrote: > Hello all, > > I was asked about a proper way to ensure powerfail shutdown of a blade > server fed off an APC SmartUPS, which is monitored by all hosts over > SNMP. In particular, they'd like to avoid the "untimely" return of > utility power - when the OSes are already shutting down, and would > stay down
2016 Apr 19
1
APC AP9630 support AES ?
Hello: I have APC AP9630 UPS, use nut, but the execution failed, my ups.conf setting right? thank! nut2.7.3 net-snmp5.2.1 openssl0.9.8 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20160419/032eedd5/attachment.html> -------------- next part -------------- A non-text attachment was
2013 Oct 09
2
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc
2012 Mar 05
0
masq and snat
Hi! Progress is much better now with my new install with not many problems left! I just have a simple - I hope - question. I have a few users that need access to the net via masquerade rules. The rest have to go via squid on the firewall. That all works well. I also have two windows servers that also need access to the net but they have to each use a specific outgoing ip address. I add two
2011 May 09
0
PowerCom BNT2000AT ups on nut 2.6.0
Hi! Normally nut was just worked and worked for me! Not this time though! Distro is Gentoo withe latest nut-2.6.0 emerged today. Linux kernel version is 2.6.36 UPS is PowerCom BNT2000AT "Driver" is powercom ups.conf looks like this! Okay so APC1 is not and APC! [APC1] driver = powercom type = BNT port = /dev/ttyS1 numOfBytesFromUPS = 16
2013 Oct 09
0
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a
2018 Dec 06
1
battery.runtime
That's an idea Charlie. The APC UPS I am using has an AP9630 card in it and pfSense is grabbing the snmp. I could try to use the USB cable on the FreeNAS so both could be masters. ----- Original Message ----- From: "Charles Lepple" <clepple at gmail.com> To: "Danny Siminiuk" <daniel at siminiuk.com> Cc: "nut-upsuser" <nut-upsuser at
2005 Mar 23
9
multiple vpn connections out via shorewall
Hi All, Just joined the list to try and solve a problem. To show that I''ve read the rules I''ll start with the requested info os linux kernel-2.4.27 with latest netfilter pom for gre and pptp conntrack etc iptables is 1.3.0 - downloaded and compiled with the pom stuff and the 2.4.27 kernel shorewall version shorewall-2.2.1-2 from rpm ip addr show [root@squid3 root]# ip addr
2013 Jan 29
1
SNMPv3
nut-2.6.5 Scientific Linux 6.3 APC AP9630 management card My basic question is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5
2018 Mar 30
2
Trying to update the official docs for nut on FreeNAS - help needed to ensure it's written correctly
This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes