Howdy.
I've been playing around with vmm(4) on 6.1 and have noticed a few
things that seem odd.
Take the following vm.conf:
ramdisk="/home/los/vmm/bsd.rd-current"
switch "local" {
add vether0
}
vm "test.vm" {
boot $ramdisk
disable
owner los
memory 2G
disk "/home/los/vmm/te
On 16.8.2017. 19:55, Juan Guillermo Narvaez wrote:
> Hello everyone!
>
> I'm relative new using OpenBSD, I have just 4 years using this OS for dhcp
> servers.
> Today I have the mission of implement this OS in a cablemodem headend, in
> my first try I get negative results with this rules:
>
> *pa
Just some more pointers? Please correct me if I am saying some thing
wrong.
Maybe also good to look at cpu interupts. I'me not sure how good if_bge
today are. I found them in the past "slowly" eating interrupts when
passing lot of small sized traffic. How is your avarage packet size?
I could bl
Thanks James, now I'm trying with 3K customers and 1M states.
I will comments my results to the list when a finish.
Guillermo.
On Wed, Aug 16, 2017 at 4:01 PM, James Shupe wrote:
> Have you raised states? 10K is the default I believe, the most likely
> culprit.
>
> On 8/16/2017 12:55 PM, Juan
Have you raised states? 10K is the default I believe, the most likely
culprit.
On 8/16/2017 12:55 PM, Juan Guillermo Narvaez wrote:
> Hello everyone!
>
> I'm relative new using OpenBSD, I have just 4 years using this OS for dhcp
> servers.
> Today I have the mission of implement this OS in a cabl
Hello everyone!
I'm relative new using OpenBSD, I have just 4 years using this OS for dhcp
servers.
Today I have the mission of implement this OS in a cablemodem headend, in
my first try I get negative results with this rules:
*pass all flags S/SA*
*#LAN*
*match out log on bge0 inet from 192.168
Hi,
I'm trying to figure out how to get my USB headset (Plantronics C310)
to work.
I can't hear anything, nor does the microphone work. I fiddled with
different mixerctl settings to no avail, and I'm not even sure my
headset had been detected at all, as the available options to set
don't change,
> On 16 Aug 2017, at 10:41, Claudio Jeker wrote:
> On Wed, Aug 16, 2017 at 10:27:58AM +0200, Maxim Bourmistrov wrote:
>>
>> Once connection is established, state is created in PF. Subsequent requests
>> will be ???pipelined???.
>> It is possible to influence this behavior by manipulating tcp.est
Sorry have not been checking in for a while - will definitely try the
patches suggested.
It may take a few weeks though to fit with our internal processes.
I will report back - thanks
On Sun, Jul 30, 2017 at 10:33 PM, FUKAUMI Naoki wrote:
> Hi,
>
> From: Andrew Daugherity
> Subject: Re: Gettin
On Wed, Aug 16, 2017 at 10:27:58AM +0200, Maxim Bourmistrov wrote:
>
> Once connection is established, state is created in PF. Subsequent requests
> will be ???pipelined???.
> It is possible to influence this behavior by manipulating tcp.established in
> pf.conf,
> but I don???t think this is wh
Once connection is established, state is created in PF. Subsequent requests
will be ’pipelined’.
It is possible to influence this behavior by manipulating tcp.established in
pf.conf,
but I don’t think this is what you want.
> 16 aug. 2017 kl. 10:05 skrev Mischa Peters :
>
> Hi All,
>
> I have
Hi All,
I have somewhat the following config for relayd running on 6.1.
And I am trying to forward certain request paths to different hosts.
table { xx.xx.xx.131 }
table { xx.xx.xx.31 }
http protocol httpsfilter {
match request header remove "Proxy"
match request header append "X-
12 matches
Mail list logo