Search results

On a machine acting as a bridge, I have only one dummynet pipe configured with PLR. I add two rules, hoping that I will generate symmetric packet loss on UL & DL for a single host behind the bridge. However, I end up with double the packet loss in UL, while in DL the packet loss is exacty...

yes, I have IPFIREWALL_DEFAULT_TO_ACCEPT. I do not load any other ip* modules. What other IPFIREWALL_* options should I have? unfortunately I cannot test now what happens if I enable net.link.ether.ipfw and set that rule, since the machine is used, but hopefully I can try that next week.

dammit, yes... devel/ncurses, slipped my mind even though it was mentioned before. seems it is installed. can i get rid of it and revert to the system ncurses?

so, with the dialog example with 0 0 I get some weird placement on the display. but for any size I explicitly set (like 10 10) it looks perfectly ok in the putty remote terminal. cdialog still junk in all situations, no colors too. setenv does not work on my system, so I export this variable...

I was just about to post all details, but found the problem: while in 8.0 I used in sysctl.conf: net.link.ether.ipfw=1 net.link.bridge.ipfw=1 ...and dummynet+bridge performed as expected for delay, plr etc, in 8.2 this does not work anymore. In 8.2 I have to use: net.link.ether.ipfw=0...

this helped me, thanks a lot! do you have any idea why in 8.2 you have to put net.link.ether.ipfw=0? for me in 8.0 this worked with net.link.ether.ipfw=1 perfectly, ported everything to 8.2 and it does not work anymore unless i set this to 0. the rest can all stay identical...

the putty is used on windows, on a remote machine. when I was talking about ttyv, I was talking about local FreeBSD console, run on the same machine where the script is located. either way, the result is the same: for dialog everything looks ok (color, borders etc), for cdialog it's trash...

yes, in local consoles. but the interface will be used over putty, so I do want to avoid to play around much with custom stuff that I cannot reproduce on putty after that... using ncurses in c and compiling gets me good results, but also alot of extra work... I did also not mess with the...

i might be wrong, but ping basically is round-trip-time. which means that you measure the time for the packet going + the response packet back. they will both pass your rules and thus each of them will be delayed, right? i might be also missing something, in case you use "in recv INTF" this...

hi, when i config a pipe with delay >0ms, all my traffic gets blocked. with the pipe active but delay 0 the traffic is ok. this was working before: i had working scripts in 8.0 to delay traffic over a bridge, filtering by dst/src-ip on out. ipfw, dummynet compiled into the kernel, hz=1000...

hi, hope this isn't something well-known, I searched for some time for it and no success. On my 8.2 Release, mostly generic, dialog displays totally ok (with the graphic lines). compiled cdialog from ports (since I need the gauge box), make sure I have the latest ncurses (5.7?) - BUT i get...