Netgate Store

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dennypage

Pages: [1] 2 3 4 5 ... 58
1
General Questions / Re: Gateway - Send to Error 65
« on: May 18, 2018, 12:01:08 am »
[NB: When you redact addresses like that, it makes sense to distinguish between the various addresses such as bind address the target address.]

Jimp's post is pretty instructive...

One question comes to mind... Are you using an explicit monitor address? Or using the default gateway address? If an explicit address, you might want to choose one a little farther inside your ISP, or one on the other side of your ISP.

2
Traffic Shaping / Re: playing with fq_codel in 2.4
« on: May 12, 2018, 10:09:28 pm »
Only reason I have it as floating is because I have 6 vlans. I will set it one by one in each vlan and hope this goes away.

Yea, I hear you. Floating is much more convient. I have 5 local nets, although using interface specific rules I only bother with 4 of them. The last network is very low traffic and I donít want to drop packets there anyway.

3
Traffic Shaping / Re: playing with fq_codel in 2.4
« on: May 12, 2018, 12:02:32 pm »
it was reported on here earlier by someone else: https://forum.pfsense.org/index.php?topic=126637.msg765566#msg765566
could it be issue with the way I have set up the firewall rules as floating (same as person in the post I linked to above)
If I do traceroute I see all the hops show up as the destination ip.

It's unclear that this is a problem with limiters themselves. It only happens if you use a floating rule to assign the queue. If you use the default allow rule on the interface to assign the queue, the traceroute problem does not occur.

4
Traffic Shaping / Re: playing with fq_codel in 2.4
« on: May 06, 2018, 02:59:21 pm »
Really appreciate the work Matt!

5
Traffic Shaping / Re: playing with fq_codel in 2.4
« on: May 05, 2018, 08:58:04 pm »

6
Packages / Re: NUT package
« on: May 02, 2018, 10:24:45 pm »
Just did a full reinstall on 2 new drives for ZFS to the latest 2.4.3. Restored my config and see my UPS not connecting.
 ...
Did some reading and find that chmod 777  /dev/ugen0.4 ended up getting it working again.  Wondering what changed to cause what seems to be a permissions issue for that USB ugen path?

Itís generally an issue when you first install the base nut package on FreeBSD. The nut package puts a config script in place to set ownership of the usb device to the user nut runs as. Unfortunately, the script does not execute until you reboot or unplug and replug the usb device.

7
Routing and Multi WAN / Re: Dpinger messages
« on: April 30, 2018, 11:56:50 am »
This is dpinger logging parameters at startup. Nothing to be concerned about.

8
Packages / Re: Configure NUT to only monitor and do nothing?
« on: April 22, 2018, 01:12:44 pm »
You cannot configure NUT such that it will not attempt to perform a shutdown. You could configure a shutdown command that doesn't do anything by adding the following line in the "Additional configuration lines for upsmon.conf" section:

  SHUTDOWNCMD /bin/echo

Note however that NUT will still do everything but shutting down the system, including shutting down any slaves. I'm also unclear on how NUT will behave following the attempted shutdown. You may have to restart the service.

In general however, I would not recommend the approach of trying to split the UPS between apcupsd and NUT. If you want NUT's monitoring, use NUT for the shutdown.

9
Packages / Re: NUT package
« on: April 06, 2018, 01:11:42 pm »
I tried another port and cable.  It still seems to think itís in the same port 0.3.
 Still see the retrieving string failed.  Still not able to monitor UPS in pfSense GUI.

Until you have the USB issue figured, I would disable the NUT service in pfSense.

On the USB bus, the second bus may the front connectors. It's worth a shot. Normally, I recommend against USB hubs, but it's also worth a try to put a (high quality) hub between the host and the UPS to see if that helps.

Btw, did you ever try the tripplite driver?

10
Packages / Re: NUT package
« on: April 05, 2018, 03:44:43 pm »
There's 6 ports on the back, 2 on the front.  Its a Dell Optiplex 390.  It doesn't appear to have USB 3.0 - at least none of the ports are blue.  I could also throw in a USB 3.0 PCIe card if none of the onboard ports work.

It looks like all the ports are USB 2.0. The UPS itself is a low speed USB device, so you are using the internal compatibility bridge anyway.

Btw, if you have any other USB devices connected, you might want to disconnect them while you diagnose your UPS issue.

11
Packages / Re: NUT package
« on: April 05, 2018, 12:05:47 pm »
It almost seems to be maybe a permissions problem?  But even if I try to run it as root it shows this:
[2.4.3-RELEASE][root@pfSense.local]/usr/local/etc/nut: upsd -DDDD

NUT is a multi-process architecture. See /usr/local/etc/rc.d/nut.sh.

12
Packages / Re: NUT package
« on: April 05, 2018, 11:57:49 am »
ugen0.3: <Tripp Lite TRIPP LITE UPS> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0008
  idVendor = 0x09ae
  idProduct = 0x3016
  bcdDevice = 0x0002
  iManufacturer = 0x0003  <retrieving string failed>
  iProduct = 0x0001  <retrieving string failed>
  iSerialNumber = 0x0005  <retrieving string failed>
  bNumConfigurations = 0x0001

The "retrieving string failed" is something I haven't seen before and would seem problematic. First thing I would suggest is trying a USB port on the other bridge chip. I would also test a different cable.

13
Packages / Re: NUT package
« on: April 04, 2018, 04:44:59 pm »
I have a TrippLite Smart 1300VA unit connected via USB.  dmesg does show it connected.  This model is also one listed in NUT to use the USB driver (not the legacy TrippLite driver).

Please run "usbconfig dump_device_desc" and post the output. Also, can you post the contents of /usr/local/etc/nut/ups.conf please? And lastly, the exact model number of the UPS.

Btw, where did you see the note about using the usbhid-ups vs. the tripplite_usb driver? I didn't find a Tripp Lite 1300VA model in the NUT HCL...

14
Traffic Shaping / Re: playing with fq_codel in 2.4
« on: April 03, 2018, 11:04:30 am »
If I were you, I would try to disable all shapers, limiters, leaving just plain firewall and let it run again, to see is it worse or better.

Yes, I ran rrul tests with and without limiters enabled, confirming the basic operation of fq_codel with 4 streams.

15
Traffic Shaping / Re: playing with fq_codel in 2.4
« on: April 03, 2018, 11:00:39 am »
I forget what hardware you were running with.  Have you monitored CPU usage while running the tests? 

It's a 4860. Peak CPU @ ~25%, average under 20%.

Pages: [1] 2 3 4 5 ... 58