similar to: Driver for Tripp Lite SmartPro SLT

I'm running Ubuntu 5.10, featuring a patched kernel 2.6.12. I have a Tripp Lite SmartPro SLT ups connected via USB. I have cleanly compiled and installed the new nut 2.0.3. I do have the "extras", like libusb, installed too. I need some USB advice- that is, I'm not sure what a normal baseline should look like. At boot, the modules usb_core and uhci_hcd are loaded. dmesg

Well, I have good news and bad news. I have a Tripp Lite SmartPro UPS attached to a Linux server running Ubuntu 5.10, and I'm running the just-released nut 2.0.3. I had error -71 from the UPS, which Charles Lepple correctly called out as a likely cable problem (thank you, Charles.) The cable provided with the UPS by Tripp Lite was just plain bad. Not too long, mind you- defective. I

We currently use iptables, matching packets based on IP address and marking them with an ID. Multiple IP addresses can be marked with the same ID. We then filter based on the ID. We have close to 2000 filters now and I''m looking into hashing tables. Is there any way to create a hashing filter based on the fwmark? Paul C. Diem PCDiem@FoxValley.net

I''m looking for a way to configure a qdisc or filter to drop all packets. The logic behind this is that I''m using the u32 hashing tables to get move my filters from iptables to tc filters. This will translate into much less per-packet processing for me. However, I need a way to drop any packets that don''t match any of the filters. Paul C. Diem PCDiem@FoxValley.net

Original Message >I have 2 SmartUOS1050SLT's that apparently protocol 3004, has there >been >any progress on getting these units supported under nut? I am running >version 2.4.1, and get the following output when starting the driver. >#lsusb >Bus 005 Device 002: ID 09ae:0001 Tripp Lite ># upsdrvctl -DDDD start >Network UPS Tools - UPS driver controller 2.4.1

Hi Everyone, I'm new to Samba. I have setup a samba server (Redhat 9) in the internal LAN and a samba client (Win2k) in the external LAN. There is a firewall between these two LANs. My problem is I cant see my workgroup in the client Microsoft Windows Network window. I have open 139, 445 tcp ports and 137, 138 udp ports. I have open 901 port as well. Before this I have tried connect to the

I have a TrippLite SmartPro UP (SMART3000RM2U) that shipped with the DB9 cable# 73-0866. nut doesn't recognize the UPS using the tripplite driver. I found this page: http://www.tripplite.com/support/download/PA12/help/device.htm The link lists the SmartPro series as using the cables 73-0724 or 73-0844 and the Internet 350/525 is listed as using a cable 73-0866. I have a few 73-0844s

Recently, Windows 2000 SP4 clients have developed a problem when using a network printer connected to a Samba print share. Some applications are OK. But take, well, notepad, for example. Selecting a local printer is normal, but there is a two minute delay (!) in selecting a network printer. Once selected, all is well. All smb operations are frozen until the selection happens. This is

Greetings to all, I recently connected a Tripp Lite SMX500RT1U unit to a Synology NAS (basically a Marvell ARM equipped box running a custom 2.6.24 Linux). I tried using the tripplite_usb driver contained in nut 2.4.1 with not much luck. It does read the model ID and VA rating properly, but fails at everything else - mains voltage (this is a 230VAC EU model), battery config, unit status etc.

I am using NUT 2.0.2 on SuSE Linux 9.2 which is attached to a Tripplite SmartPro Net 2200 UPS. I have Nut using the included tripplite driver, and it is communicating with the UPS correctly. The battery voltage of theTripplite reported by the NUT server is 13.5VDC. If I attach the UPS to a Windows 2000 server running Tripplite's PowerAlert software, the battery voltage is being reported as

I have 2 SmartUOS1050SLT's that apparently protocol 3004, has there been any progress on getting these units supported under nut? I am running version 2.4.1, and get the following output when starting the driver. #lsusb Bus 005 Device 002: ID 09ae:0001 Tripp Lite # upsdrvctl -DDDD start Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: tripplite exec: /lib/nut/tripplite_usb -a

He everyone, I have a Tripplite SMART700DVa using the tripplite_usb from NUT 2.5 (rev 2217) driver running in Solaris 10x86. My driver hangs when trying to connect. Once the driver sends the watchdog command ("W\0"), it can no longer receive any signals and eventually exits. The UPS responds to other watchdog commands ("W5" for example), but there doesn't seem to be

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

Good afternoon, I'm trying without much success to monitor a Tripp Lite OMNIVS1500XL using NUT. I checked the compatibility list and saw that this UPS is supported by tripplite_usb. The system is running Debian Stable, but I've downloaded NUT 2.0.3 and compiled from source since the packaged 2.0.1 doesn't include tripplite_usb. I compiled --with-user=nut. My first attempt at

I've having no success trying to use the tripplite driver to communicate with a Tripp-Lite SMART1500XL via the serial port. I'm using the cable that was included with the UPS. The tripplite driver simply returns "Failed - giving up..." after 20 seconds. I have verified that the tripplite driver is sending ":W" out the serial port. I am able to use Tripp-Lite's

Hello, I am trying to get a SMART500RT1U working on CentOS and just receiving the following message when attempting to start the driver: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U Unknown input voltage range: 0x02 Unknown number of

Hey, I am wondering if anyone gotten nut to work with a Tripp Light Smart Pro 2U Rack/Towers (SMART2200RMXL2U). If so which driver did you use, or what driver do you think I should try? Also when trying use a nut driver, do you have to be a nut user? Thanks, Ricky -------------- next part -------------- An HTML attachment was scrubbed... URL:

As I understand it from looking through the archives of this mailing list and the source for the driver, tripplite_usb should work for this device. I tried to go through the source as best I could to see if I could add support myself, but got a bit lost. Anyhow, here's hoping that someone has some experience with this model. My system is using the latest CVS checkout of the Development branch

I am running Debian Etch, with the nut 2.0.4 packages, and I get a segmentation fault from tripplite_usb. # /lib/nut/tripplite_usb -u root -DDDDD auto Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.4) Warning: This is an experimental driver. Some features may not function correctly. debug level is '5' Checking device (09AE/0001) (002/004) - VendorID: 09ae -