Re: bug tracking system for OpenBSD

[Mike Burns]

On 2018-03-30 23.01.16 +0300, Sergey Bronnikov wrote:
> I have made a first step forward in direction to OpenBSD bugtracker
> and imported bugs@ archive to a Fossil SCM -
> https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1

Ran it through curl:

- Your cert is invalid.
- Why does every ticket go to /cgi-bin/b.cgi/honeypot ?

> Let's discuss a next step.

Are these triaged?

Re: bug tracking system for OpenBSD

[Peter Hessler]

On 2018 Mar 30 (Fri) at 23:01:16 +0300 (+0300), Sergey Bronnikov wrote:
:On 17:54 Tue 19 Dec , Ted Unangst wrote:
:> Kai Wetlesen wrote:
:> > > > you don't have to announce your bug database the first day you set it 
up. in
:> > > > fact, it's better not to. but in a few months time, when somebody 
inevitably
:> > > > asks misc how do i contribute, where's the todo list, you'll have this 
handy
:> > > > list of unresolved bugs to point them at.
:> 
:> > There are many decisions that would need to be made that will piss somebody
:> > off. Decisions like what software/platform to use, where to host the 
thing, and
:> > how much the tool should integrate into existing bug reporting mechanisms
:> > (right now just fancy emailing).
:> > 
:> > To answer your tactful question Theo, I personally haven’t done anything 
because
:> > I do not have your blessing nor of someone who can say “yes just effing do 
it". But,
:> > if you would be willing to give me free reign it will be done.
:> 
:> Imagine if you'd followed my suggestion and spent the last six months 
curating
:> a bug database. Then today you could have sent us a link to it and everybody
:> would see how useful it is. Now we have to wait another six months.
:
:I have made a first step forward in direction to OpenBSD bugtracker
:and imported bugs@ archive to a Fossil SCM -
:https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1
:Let's discuss a next step.
:

I believe the next step would be to delete the database.
_Please re-read the entire thread_.  Or even just the parts you quoted.

An example that shouldn't be displayed in the database:
 - Arrival-Date:   Tue Jul  7 17:50:01 MDT 1998

-- 
In Lexington, Kentucky, it's illegal to carry an ice cream cone in your
pocket.

Re: counting dropped packets for pf

[Mihai Popescu]

> ... better badly does work ...

If it so, then it should not be done from the start.
A bad implementation can trigger other problems.
Try to think a little bit. ( hint: Chernobyl)

Re: bug tracking system for OpenBSD

[Sergey Bronnikov]

On 17:54 Tue 19 Dec , Ted Unangst wrote:
> Kai Wetlesen wrote:
> > > > you don't have to announce your bug database the first day you set it 
> > > > up. in
> > > > fact, it's better not to. but in a few months time, when somebody 
> > > > inevitably
> > > > asks misc how do i contribute, where's the todo list, you'll have this 
> > > > handy
> > > > list of unresolved bugs to point them at.
> 
> > There are many decisions that would need to be made that will piss somebody
> > off. Decisions like what software/platform to use, where to host the thing, 
> > and
> > how much the tool should integrate into existing bug reporting mechanisms
> > (right now just fancy emailing).
> > 
> > To answer your tactful question Theo, I personally haven’t done anything 
> > because
> > I do not have your blessing nor of someone who can say “yes just effing do 
> > it". But,
> > if you would be willing to give me free reign it will be done.
> 
> Imagine if you'd followed my suggestion and spent the last six months curating
> a bug database. Then today you could have sent us a link to it and everybody
> would see how useful it is. Now we have to wait another six months.

I have made a first step forward in direction to OpenBSD bugtracker
and imported bugs@ archive to a Fossil SCM -
https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1
Let's discuss a next step.

Re: counting dropped packets for pf

[3]

> On Fri, Mar 30, 2018 at 9:58 AM, 3  wrote:
>> perhaps my poor english prevented you from understanding the question

> perhaps

>> my initial approach does work. u are have comments about route-to?

> If people do not understand the words you use to represent the ideas
> you were thinking, does that matter?
i showed my idea on the example of pf's config- this language should
be familiar to you

> If there are more efficient ways of accomplishing the same thing, is
> it important?
no more effective ways. the variant with pfctl is a kolhoz-style(ugly
and ineffective), it requires a lot of work to convert data into
netflow format

> [regardless, I am going back to lurking and trying to figure out a
> good way to install current on a system I use.]

> Thanks,

Re: counting dropped packets for pf

[Raul Miller]

On Fri, Mar 30, 2018 at 10:35 AM, 3  wrote:
> i showed my idea on the example of pf's config- this language should
> be familiar to you
...
> no more effective ways. the variant with pfctl is a kolhoz-style(ugly
> and ineffective), it requires a lot of work to convert data into
> netflow format

You did indeed show some rules that would do something if you replace
some of their text with something else but which do not address the
issue you had earlier labeled "impossible".

But, if you will excuse me, I have a lot of work to do.

-- 
Raul

Re: counting dropped packets for pf

[Raul Miller]

On Fri, Mar 30, 2018 at 9:58 AM, 3  wrote:
> perhaps my poor english prevented you from understanding the question

perhaps

> my initial approach does work. u are have comments about route-to?

If people do not understand the words you use to represent the ideas
you were thinking, does that matter?

If there are more efficient ways of accomplishing the same thing, is
it important?

[regardless, I am going back to lurking and trying to figure out a
good way to install current on a system I use.]

Thanks,

-- 
Raul

Re: counting dropped packets for pf

[3]

> On 03/30/18 13:32, 3 wrote:

>> people like you do not understand what better badly does work than
>> well not works. and it is not our(not ordinary users) fault that the

> Seriously, cipher, you're just spewing word salad again.

> And it sounds vaguely like abuse, aimed at people who were in fact
> offering useful suggestions.
to give useful suggestions first need to understand the question.
perhaps my poor english prevented you from understanding the question

> Some of us were able to decipher what we thought was your problem
> (wanting to record dropped packets) and offered suggestions on how to do
> that along with the explanation why your original approach was never
> going to work.
my initial approach does work. u are have comments about route-to?

> If you really want to record your dropped packets in a netflow format,
> there's nothing stopping you from implementing just that.
in next time remind yourself that you can surgery on your own, instead
of going to a surgeon

> Whether your implementation will be accepted back the OpenBSD source
> tree is of course a different and separate question.
i am a ordinary user(not a surgeon) and have already talked about it,
but my poor english..

> One thing is certain, though: Spewing abuse-ish word salad at mailing
> lists is not going to get you anywhere.
sorry about that -_- i should have left as soon as i understand we
were living in different worlds

Re: counting dropped packets for pf

[Peter N. M. Hansteen]

On 03/30/18 13:32, 3 wrote:

> people like you do not understand what better badly does work than
> well not works. and it is not our(not ordinary users) fault that the

Seriously, cipher, you're just spewing word salad again.

And it sounds vaguely like abuse, aimed at people who were in fact
offering useful suggestions.

Some of us were able to decipher what we thought was your problem
(wanting to record dropped packets) and offered suggestions on how to do
that along with the explanation why your original approach was never
going to work.

If you really want to record your dropped packets in a netflow format,
there's nothing stopping you from implementing just that.

Whether your implementation will be accepted back the OpenBSD source
tree is of course a different and separate question.

One thing is certain, though: Spewing abuse-ish word salad at mailing
lists is not going to get you anywhere.

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: counting dropped packets for pf

[3]

>> You would need a 1/4" wrench and a screwdriver tip that fits an impact 
>> driver.

> I want to see you using your method for a deep sunken screw inside a
> cylindrical channel of a case.
> You can give a chance to the other guy, too.
> People like you do not understand concepts like evolution, smart
> tools, unix simplicity, KISS, etc.

people like you do not understand what better badly does work than
well not works. and it is not our(not ordinary users) fault that the
progress of obsd is only to cut poorly functioning parts without
giving anything instead. teo and your ideal fucking unix system is
"hello, world!" with two remote holes in the default install. but you
are too d^Hstubborn to understand that such a system is not necessary
for ordinary users. i like pf and i hate dirty monkey's style of
linux, but there will come a time when this will not be enough to
choose obsd

Re: counting dropped packets for pf

[edgar]

On Mar 30, 2018 4:08 AM, Mihai Popescu  wrote:
>
> > You would need a 1/4" wrench and a screwdriver tip that fits an impact 
> > driver.
>
> I want to see you using your method for a deep sunken screw inside a
> cylindrical channel of a case.
> You can give a chance to the other guy, too.
> People like you do not understand concepts like evolution, smart
> tools, unix simplicity, KISS, etc.
>

First let me say I believe '3' to be a bit of an arsehole and was surprised he 
received any helpful responses. However the above is a perfect example of Unix. 
Perhaps you haven't used '|' to combine utility programs.  

Re: SNI PCD-5T - MP operation on OpenBSD 6.3-current

[Frank Scheiner]

Hi Daniel,

On 03/30/2018 02:20 AM, Daniel Dickman wrote:

Hi Frank —


I got this nice old "workstation" from the mid 90ies with dual P54C
processors and i430NX chipset and want to operate it in MP mode with
OpenBSD. Unfortunately this doesn't work as expected currently.


Are you able to describe "doesn't work as expected" a bit more? Does it hang 
after the dmesg? do you get to login? Something else?


Sorry, right, I actually missed the point.

The machine works with OpenBSD, but just not in MP mode, only one CPU is 
activated/found:


```
OpenBSD/i386 (pcd-5t.domain.tld) (tty00)

login: root
Password:
Last login: Wed Mar 28 11:10:35 on tty00
OpenBSD 6.3 (GENERIC.MP) #491: Sat Mar 24 14:38:11 MDT 2018

Welcome to OpenBSD: The proactively secure Unix-like operating system.
[...]
pcd-5t# sysctl hw
hw.machine=i386
hw.model=Intel Pentium (P54C) ("GenuineIntel" 586-class)
hw.ncpu=1
hw.byteorder=1234
hw.pagesize=4096
hw.disknames=fd0:
hw.diskcount=1
hw.cpuspeed=139
hw.physmem=167264256
hw.usermem=167251968
hw.ncpufound=1
hw.allowpowerdown=1
```




I've
already tried with 6.1, 6.2 and 6.3-current-1521924436. Find attached
the full dmesg output for 6.3-[...] below, but I suspect that the
following message is the most relevant one:

```
[...]
bios0: MP default configuration 6 not supported
[...]
```

I actually don't know the meaning of it, can someone perhaps shed some
light on it?


It means you got to this bit of code (see sys/arch/i386/i386/mpbios.c):

if (mp_fps->pap == 0) {
if (mp_fps->mpfb1 == 0)
printf("%s: MP fps invalid: "
"no default config and no configuration table\n",
self->dv_xname);
else
printf("%s: MP default configuration %d not "
"supported\n", self->dv_xname, mp_fps->mpfb1);
goto err;
}


Yes, I also found this part later on with a string search, but couldn't 
make much out of it due to missing knowledge you did provide below - 
thanks for that. :-)




mp_fps is the "MP floating point structure" (see 4.1 in the MP spec). Now, we 
know the pap (Physical Address Pointer) is zero which means the MP config table doesn't 
exist on your system. So when there's no config table, the spec wants to use a default 
setup. (see section 5 of the spec).

To know which default config to use we’d need to use the MP information byte #1 
according to the spec. Your dmesg shows the value is 6 and the spec says a 
value of 6 refers to 2 cpus with EISA+PCI bus and integrated APIC).

It may be the case that more work is needed to add support for this setup. 
Haven’t looked much further than that so far...


The message mentioning that "MP default configuration 6 not supported" 
sounded like specifically default config 6 isn't supported in my case.
But it actually looks like this affects all systems that don't have an 
MP config table, i.e. no MP operation if there's no MP config table but 
just a default config.


I'll try to find out how NetBSD handles default configurations. Maybe 
this can be applied to OpenBSD, too.


Cheers and thanks for the explanations
Frank

Re: counting dropped packets for pf

[Mihai Popescu]

> You would need a 1/4" wrench and a screwdriver tip that fits an impact driver.

I want to see you using your method for a deep sunken screw inside a
cylindrical channel of a case.
You can give a chance to the other guy, too.
People like you do not understand concepts like evolution, smart
tools, unix simplicity, KISS, etc.

Re: counting dropped packets for pf

[3]

> man pf.conf is your friend, please consult there before letting
> resentment stew for years next time, huh?

why are you silent? do you have the courage to admit that the famous
russian comedian zadornov was right when said "ну тупые!"? ;)