similar to: NUT with pfsense 2.0.1

I used a brazilian UPS from "TS-Shara" which uses the megatec serial protocol and it works perfectly. Now I have another one from the same brand (TS-Shara) and it uses a USB cable. I found the following: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0483 ProdID=0035 Rev= 2.00 S:

2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hi, > > I had an issue where after returning the power from a shutdown.return the > ups would do another shutdown.return during the boot, and kept this forever. > After some investigation I found the problem is a bug on the ups - TSSHARA > model, driver nutdrv_qx: every time I shutdown with return, and

Hello, I think that on this file nutdrv_qx_megatec.c the definition for shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m while on the megatec protocol description ( http://networkupstools.org/protocols/megatec.html) the command is just "S%s\r". When I changed it my system was abe to at least stay off, and stopped making an instant power recycling.

Hi, I had an issue where after returning the power from a shutdown.return the ups would do another shutdown.return during the boot, and kept this forever. After some investigation I found the problem is a bug on the ups - TSSHARA model, driver nutdrv_qx: every time I shutdown with return, and reconnect the usb after the power is back it would start another shudown.return cycle. When I used my

[please keep the discussion on the nut-upsdev list. thanks!] On Jan 30, 2014, at 10:20 AM, Jos? Sosa wrote: > Dear Mr. Lepple > > I am Leonardo Sosa and I am watching this issue with Rodolfo and Ronaldo. (in copy) > > See below our answers of your questions. > > What should I do now in order to include our code sgs_command in your code blazer_usb.c? As I mentioned to

Answers bellow. 2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>: > 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > > Hi, > > > > I had an issue where after returning the power from a shutdown.return the > > ups would do another shutdown.return during the boot, and kept this > forever. > > After some

Hi Rodolfo, [please reply to <nut-upsdev at lists.alioth.debian.org>, not nut-upsdev-owner, and if you have large attachments, upload them to a web server and post the URL. Thanks!] On Jan 29, 2014, at 7:59 AM, rodolfo at tsshara.com.br wrote: > <blazer_usb.c.txt> > Sorry, we forgot to send another file. We developed this code (blazer_usb.c.txt) so that your software is able

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hello people. My name is Rub?n. Firts, excuse me for my bad english. I run Debian 6.0.6, kernel 2.6.32-5-amd64 in my machine. I bought a ISB Sola basic UPS, model Micro SR inet, with usb conection. I Configure the nut.conf file in standalone mode and I install de isbmex driver. The ups.conf: [ISB_sola-basic] driver = isbmex port = auto With de command upsdrvctl start the

Alexander Gordeev wrote: > Author: agordeev-guest > Date: Mon Aug 13 13:09:43 2007 > New Revision: 1049 > > Log: > drivers/megatec_usb.c: added credits to the banner message. Is this really needed/desirable? I think this kind of information needs to be put in the AUTHORS document. There are many more people on this list that put a lot of effort in NUT, without claiming credit

I got a UPS Sola Basic but it is not working, I'm providing the details. I hope that someone can help me to get it working. Please let me know if there is some other information that I should provide :) OS name and version Ubuntu 12.04 $ uname -a Linux olimpo 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Exact NUT version, 2.7.1

Hi all, My name is Sergio Penen and I'd like to contribute to the project by developing a new driver for TS SHARA SOHO II usb ups. I'm almost done decoding the protocol and already have some basic functionality working with NUT. However I've some doubts on how to integrate this driver with NUT and I wonder if you could give me some guidance in that sense. To be more specific: In order

2018-02-28 21:11 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hello, > > I think that on this file nutdrv_qx_megatec.c the definition for > shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m > while on the megatec protocol description ( > http://networkupstools.org/protocols/megatec.html) the command is just > "S%s\r".

Other SIP clients behind the firewall (not using STUN, work). We have a SIP client using STUN and ICE behind a pfSense firewall. The firewall is behaving oddly. REGISTER packets work fine. But when the client tries to make a call, the first INVITE packet from the client pass through the firewall and makes it to the Asterisk server. The Asterisk server sends back a 401 client sends ACK,

Hi Everyone, Just trying to connect the Zoiper Communicator to connect to Asterisk which is behind Pfsense. Here is what I get at debug and it doesn't register. Error code 16. Can someone please let me know their firewall, NAT, outbound 1-to-1 pfsense settings as it seems to me I am doing something wrong on the firewall? *Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX

I am trying to setup a VPN using tinc and pfsense to bridge routers and share a lan segment. I was reading through the documentation and had a number of questions. I was wondering if anyone had experience with this and could offer some help. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi. I've a strange problem with networking and a KVM virtualized pfsense firewall. My hw host is Ubuntu 12.04 fully updated, with two bridges br0 (LAN) and br1 (WAN). pfSense is a KVM guest with the two interfaces in virtio mode. When I run pfSense as fw, the host doesn't seem capable of doing tcp connections outside. I can ping any internal and exernal host, but when I try telnetting

I have pfsense set as the NUT master and my Synology NAS as a slave client. I tried recreating a shutdown sequence by issuing a /usr/local/sbin/upsmon -c fsd command in pfsense (so as to preserve battery lifetime while testing all these) but the weird thing is that my Syno doesn't seem to get a hold of the FSD event. My pfsense master and UPS shuts down properly though. As soon as I issue the

On Mon, Oct 23, 2017 at 6:38 PM, Darren Mobley <corpdecker at gmail.com> wrote: > I've tried IRC in #tinc and #pfsense on freenode for this, not luck yet, > figured I'd try the mailing list. > > A summary of my problem is here: > > https://www.reddit.com/r/PFSENSE/comments/789xus/tinc_vpn_can_do_everything_but_be_accessed/ > > If there are any details I can