I'm not sure what I missed here so I would appreciate it if someone would
hit me with a clue bat.
My OpenBSD firewall is acting as a DHCPv6-PD client and successfully
getting IP information:
My outside interface:
vlan9: flags=208843 mtu
1500
lladdr 00:1e:37:d6:00:ad
priority: 0
I apologize in advance. I hope this is the correct list to post this
question.
I have come across a small problem in KDE 3. I just installed and patched
5.8
and added KDE 3. I opened the "system:/" desktop config file and clicked
on "Add a network folder". What I get is an error window that sta
Simply forwarding 10Gb/s is a tall order. Decapsulating 10Gb/s of l2tp I think
is probably some way off. Doing all that plus logging full packets, nope.
What do you actually need to log? Full packets? Flows? Sampled packets?
Can the traffic be split up to multiple machines?
On 15-10-27 02:53 PM, Martin Schröder wrote:
And then there are SSDs. PCIE SSDs do up to 3000 MB/s write throughput.
https://www-ssl.intel.com/content/www/us/en/solid-state-drives/solid-state-drives-dc-p3608-series.html
And I'm sure there are tape libraries that can write that, too. :-)
I disre
> Well, specifying 'lp' instead of 'rm' does make it run filters, but the job
p is not sent to the printer, even when I use the port@host format from
> the man page. As soon as I set 'rm', filters are no longer executed.
It's all documented in /usr/local/share/doc/pkg-readmes/cups-filters-*
Extra
On 27 October 2015 at 12:53, Martin Schröder wrote:
> 2015-10-27 20:24 GMT+01:00 Adam Thompson :
>> You talk about storing the data - *writing* data to disk at 10Gbps
>> (sustained) is currently in the realm of high-energy physics, with
>> multi-million-dollar budgets for the storage arrays. A 72
On Sun, Oct 25, 2015 at 2:46 AM, Some Developer
wrote:
> I'm just wondering what hardware spec I'd need push 20 gigabits of network
> traffic on an OpenBSD server?
As someone else mentioned, this is likely not possible today.
> The thing is I want to log all traffic on the server for that so I'm
2015-10-27 20:24 GMT+01:00 Adam Thompson :
> You talk about storing the data - *writing* data to disk at 10Gbps
> (sustained) is currently in the realm of high-energy physics, with
> multi-million-dollar budgets for the storage arrays. A 7200rpm disk can
And then there are SSDs. PCIE SSDs do up t
Hi people,
I can confirm this regress, just updated the kernel and top and had the
same issue, but this diff seems to solve it, I just don't know if it's
the right place to put it or not:
Index: kern_pledge.c
===
RCS file: /cvs/s
On 15-10-25 03:46 AM, Some Developer wrote:
I'm just wondering what hardware spec I'd need push 20 gigabits of
network traffic on an OpenBSD server?
Short answer: It's not generally possible today, at least for your use
case.
Medium answer: Contact Esdenera Networks to find out. They mana
On 2015-10-27, Stuart Henderson wrote:
> On 2015-10-25, Jona Joachim wrote:
>> Hi,
>> I was tired of CUPS so I decided keep it simple and stupid and use
>> lpd/lpr. Strangely, things don't work out as expected. It seems that
>> lpd never executes input filters.
>>
>> Here is the content of /etc/
On 2015-10-27, Stuart Henderson wrote:
> On 2015-10-25, Jona Joachim wrote:
>> Hi,
>> I was tired of CUPS so I decided keep it simple and stupid and use
>> lpd/lpr. Strangely, things don't work out as expected. It seems that
>> lpd never executes input filters.
>>
>> Here is the content of /etc/
On Sun, Oct 25, 2015 at 7:30 PM, Hiltjo Posthuma
wrote:
> My /etc/relayd.conf looked something like this:
>
> table { 127.0.0.1 }
>
> http protocol "protmyapp" {
> return error
>
> # TODO: forward non-matching traffic to standard httpd.
> match request head
OpenBSD 5.8-current (GENERIC) #1: Tue Oct 27 12:31:10 EDT 2015
m...@otest.24cl.home:/usr/src/sys/arch/amd64/compile/GENERIC
I didn't see anything in current.html that may affect this.
I downloaded the Oct 20 snapshot. Then I updated the source to current
this morning. After the build, top
On 2015-10-27, Federico Giannici wrote:
> On 10/27/15 16:33, Stuart Henderson wrote:
>> On 2015-10-27, Federico Giannici wrote:
>>> On 10/27/15 15:31, Chris Cappuccio wrote:
Federico Giannici [giann...@neomedia.it] wrote:
> I have to install in an OpenBSD 5.8 amd64 a PCI-E ethernet card
On 10/27/15 16:33, Stuart Henderson wrote:
On 2015-10-27, Federico Giannici wrote:
On 10/27/15 15:31, Chris Cappuccio wrote:
Federico Giannici [giann...@neomedia.it] wrote:
I have to install in an OpenBSD 5.8 amd64 a PCI-E ethernet card supporting
1000BASE-LX (i.e. 1Gbps with Single Mode Fibe
Federico Giannici [giann...@neomedia.it] wrote:
>
> We do have an ix card, the Intel X520-LR1.
> I read that it is supposed to work as 1000BASE-LX too but we were not able
> to make it work! It never gives the link.
>
> If we try to set 1000BASE-LX as media type it gives error.
>
> isengard:/hom
Federico Giannici [giann...@neomedia.it] wrote:
> On 10/27/15 16:17, Chris Cappuccio wrote:
> >Federico Giannici [giann...@neomedia.it] wrote:
> >>
> >>We do have an ix card, the Intel X520-LR1.
> >>I read that it is supposed to work as 1000BASE-LX too but we were not able
> >>to make it work! It n
On 2015-10-27, Federico Giannici wrote:
> On 10/27/15 15:31, Chris Cappuccio wrote:
>> Federico Giannici [giann...@neomedia.it] wrote:
>>> I have to install in an OpenBSD 5.8 amd64 a PCI-E ethernet card supporting
>>> 1000BASE-LX (i.e. 1Gbps with Single Mode Fiber).
>>>
>>> Usually we use Intel ca
On 10/27/15 16:17, Chris Cappuccio wrote:
Federico Giannici [giann...@neomedia.it] wrote:
We do have an ix card, the Intel X520-LR1.
I read that it is supposed to work as 1000BASE-LX too but we were not able
to make it work! It never gives the link.
If we try to set 1000BASE-LX as media type i
On 10/27/15 15:31, Chris Cappuccio wrote:
Federico Giannici [giann...@neomedia.it] wrote:
I have to install in an OpenBSD 5.8 amd64 a PCI-E ethernet card supporting
1000BASE-LX (i.e. 1Gbps with Single Mode Fiber).
Usually we use Intel cards (em driver) but I found that the only Intel LX
card ha
Federico Giannici [giann...@neomedia.it] wrote:
> I have to install in an OpenBSD 5.8 amd64 a PCI-E ethernet card supporting
> 1000BASE-LX (i.e. 1Gbps with Single Mode Fiber).
>
> Usually we use Intel cards (em driver) but I found that the only Intel LX
> card has a PCI-X bus!
>
> What reliable L
Am Dienstag, den 27.10.2015, 13:01 +0100 schrieb Federico Giannici:
> I have to install in an OpenBSD 5.8 amd64 a PCI-E ethernet card
> supporting 1000BASE-LX (i.e. 1Gbps with Single Mode Fiber).
>
> Usually we use Intel cards (em driver) but I found that the only Intel
> LX card has a PCI-X bus!
I have to install in an OpenBSD 5.8 amd64 a PCI-E ethernet card
supporting 1000BASE-LX (i.e. 1Gbps with Single Mode Fiber).
Usually we use Intel cards (em driver) but I found that the only Intel
LX card has a PCI-X bus!
What reliable LX NIC with PCI-E do you suggest?
Thanks.
On 2015-10-27, Michael S. Keller wrote:
> On 10/27/15 3:42 AM, Stuart Henderson wrote:
>> On 2015-10-26, Giancarlo Razzolini wrote:
>>> I suggest you move your match rules to the beginning of the ruleset and
>>> use log on them. So you can watch your pflog interface and see the
>>> packets being
Em 27-10-2015 09:37, Michael S. Keller escreveu:
> These are the rules that appear potentially to affect outgoing packets
> on the internal interface:
>
> match inet from any to 192.168.1.62
> block drop out on gem0 all
> pass out on gem0 inet from any to 192.168.1.0/24 flags S/SA
>
> Only traffic
On 10/27/15 3:42 AM, Stuart Henderson wrote:
On 2015-10-26, Giancarlo Razzolini wrote:
I suggest you move your match rules to the beginning of the ruleset and
use log on them. So you can watch your pflog interface and see the
packets being triggered. Also, you can (should) always use tags. Not
On Monday 26 October 2015 10:42:01 Gerald Hanuer wrote:
> Hello misc@,
>
> Unbound(8) in current errors out, not starting.
>
> This is not a bug report.
> If this is known to devs@ please disregard.
>
>
> /usr/bin/unbound -v
>
> Version 1.5.4
> linked libs: libevent 1.4.15-stable (it us
On 2015-10-25, Jona Joachim wrote:
> Hi,
> I was tired of CUPS so I decided keep it simple and stupid and use
> lpd/lpr. Strangely, things don't work out as expected. It seems that
> lpd never executes input filters.
>
> Here is the content of /etc/printcap:
> lp|hl6050|Brother HL6050:\
> :lp
On 2015-10-26, Giancarlo Razzolini wrote:
> I suggest you move your match rules to the beginning of the ruleset and
> use log on them. So you can watch your pflog interface and see the
> packets being triggered. Also, you can (should) always use tags. Not
> only they make your ruleset "debugable",
30 matches
Mail list logo
