Re: very slow scrolling in xterm

2020-12-19 Thread Claus Assmann 
On Sun, Dec 20, 2020, Nick Holland wrote:

> In fact, that machine is loaded with nvidia hw.  If you fixed
> the video, I suspect you will slam into other walls shortly after.

I know it's a "slow" computer (1) by todays standards, but the only
annoying thing is the slow scrolling (hit return, and watch as the
entire xterm content moves up one line before it displays the next
line). Everything else is "good enough" for software development
(it might take longer to compile stuff, but that doesn't matter
much to me - running the regression test suite takes the largest
amount of time).

> If you really want a dab of perfume on this pig, try a cheap ATI
> video card in whatever slots you have available in it.  However, once

Ok, I'll take a look at my other "collector items" to see if I
can find something that fits.

> I'm a tad bit curious about your implying the X performance got bad
> after 6.6...did this thing really not suck in 6.6 and before?  Maybe

Scrolling was just fine "back then": no visible delays - from
probably 5.3 up to 6.6 (AFAIR).

> there was regression in old nvidia hw with newer nvidia support?

I looked at the 6.7 release notes, but couldn't find anything obvious.
Maybe it is "hidden" in the "upgrade some X SW" entries?

Footnote:
(1) before 6.7 it was much faster/nicer to work with than the
"fancy" high-end Mac laptop that I have to use for work.
-- 
Address is valid for this mailing list only, please do not reply
to it direcly, but to the list.

Re: very slow scrolling in xterm

2020-12-19 Thread Nick Holland 
On 2020-12-19 14:00, Claus Assmann wrote:
> On one machine the scrolling in an xterm is very slow since the upgrade
> to 6.7 and also in 6.8.
> Now that I want to use this machine a bit more I'm wondering what
> settings can be used to avoid that problem.
> dmesg and Xorg log are (hopefully) attached, what other info could
> help to track down the problem?

For Some Reason, when I saw your query, the very first thing I thought
of was, "Nvidia".

My guess wasn't wrong.
In fact, that machine is loaded with nvidia hw.  If you fixed
the video, I suspect you will slam into other walls shortly after.

Could I interest you in a new computer?  There's not much in that thing
I'd call redeeming.  In fact, I've tossed a lot of better computers years
ago.  Well, it is interesting, in that it's a ~2006 Dell with an AMD proc,
but that's "interesting" as a collector's item, not a "use it for work"
thing.  

If you really want a dab of perfume on this pig, try a cheap ATI
video card in whatever slots you have available in it.  However, once
you do that, you will probably realize you have lousy disk performance
and unreliable USB.  And you don't have much memory in the thing.

I'm a tad bit curious about your implying the X performance got bad
after 6.6...did this thing really not suck in 6.6 and before?  Maybe
there was regression in old nvidia hw with newer nvidia support?

Nick.

dmesg inlined:
OpenBSD 6.8 (GENERIC.MP) #2: Sat Dec  5 07:17:48 MST 2020

r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1055784960 (1006MB)
avail mem = 1008799744 (962MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf (63 entries)
bios0: vendor Dell Inc version "1.0.3" date 10/02/2006
bios0: Dell Inc Dimension E521
acpi0 at bios0: ACPI 1.0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP BOOT SSDT HPET MCFG SLIC APIC
acpi0: wakeup devices HUB0(S5) XVRA(S5) XVRB(S5) XVRC(S5) USB0(S3) USB2(S3) 
AZAD(S5) MMAC(S5) MMCI(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: disabled
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2004.47 MHz, 0f-4b-02
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2004.19 MHz, 0f-4b-02
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu1: disabling user TSC (skew=162915)
cpu1: smt 0, core 0, package 1
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins, remapped
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (HUB0)
acpibtn0 at acpi0: PWRB
acpipci0 at acpi0 PCI0
acpicmos0 at acpi0
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
cpu0: PowerNow! K8 2004 MHz: speeds: 2000 1800 1000 MHz
pci0 at mainbus0 bus 0
"NVIDIA C51 Host" rev 0xa2 at pci0 dev 0 function 0 not configured
"NVIDIA C51 Memory" rev 0xa2 at pci0 dev 0 function 1 not configured
"NVIDIA C51 Memory" rev 0xa2 at pci0 dev 0 function 2 not configured
"NVIDIA C51 Memory" rev 0xa2 at pci0 dev 0 function 3 not configured
"NVIDIA C51 Memory" rev 0xa2 at pci0 dev 0 function 4 not configured
"NVIDIA C51 Memory" rev 0xa2 at pci0 dev 0 function 5 not configured
"NVIDIA C51 Memory" rev 0xa2 at pci0 dev 0 function 6 not configured
"NVIDIA C51 Memory" rev 0xa2 at pci0 dev 0 function 7 not configured
ppb0 at pci0 dev 2 function 0 "NVIDIA C51 PCIE" rev 0xa1
pci1 at ppb0 bus 1
ppb1 at pci0 dev 3 function 0 "NVIDIA C51 PCIE" rev 0xa1
pci2 at ppb1 bus 2
ppb2 at pci0 dev 4 function 0 "NVIDIA C51 PCIE" rev 0xa1
pci3 at ppb2 bus 3
vga1 at pci3 dev 0 function 0 "NVIDIA GeForce 8500 GT" rev 0xa1
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
"NVIDIA MCP51 Host" rev 0xa2 at pci0 dev 9 function 0 not configured
pcib0 at pci0 dev 10 function 0 "NVIDIA MCP51 ISA" rev 0xa3

Re: RISC-V and OpenBSD

2020-12-19 Thread Zeljko Jovanovic 

On 12/15/20 10:10 PM, Stuart Longland wrote:


On 10/12/20 4:33 am, Mihai Popescu wrote:

Just wanted to see if RISC-V architecture is attractive for OpenBSD
development. It's open and it is from Berkeley.


I hear it's only truly open if you're part of their exclusive "club".
Otherwise it's as much "you take what you're given" as any other
architecture.



RISC-V architecture, and a few implementations are released under BSD licence.

In contrast, ARM Holdings or MIPS Technologies don't allow others to use their
architectures without paying royalty fees. For example, the Chinese Academy of
Sciences designed Loongson processor from the scratch, but had to pay to
MIPS Technologies in order to base it on the MIPS IV instruction set.


Zeljko Jovanovic

Re: OpenSMTPD-extras manual

2020-12-19 Thread Ingo Schwarze 
Hi Maksim & Edgar,

Edgar Pettijohn wrote on Sat, Dec 19, 2020 at 03:37:22PM -0600:
> On Sat, Dec 19, 2020 at 08:02:19PM +0300, ??  wrote:

>> Where can I find any manuals and examples regarding OpenSMTPD-extras?

Try:

   $ man -k ^table-
   $ man table-passwd table-socketmap table-sqlite table-redis

>> Which table types are supported and do not have status "experimental"
>> like ldap tables?
>> E.g. what is opensmtpd-extras-python and how can I use it?

Not sure about thise questions.

> Your best bet is to git clone the repository and search for the tables, 
> etc you are interested in.

That would be unusual with OpenBSD; when possible, we try to include
documentation in user-installable packages and not only in source
distributions.

Strangely, in this case, there are files

  table-postgres.5 table-mysql.5

in the source tarballs but not in the respective packing lists.

Strangely, the tarball also contains three empty README files.

> If there is a manual simply `mandoc file | less`.

Not the best advice ever...  :-/

Manually piping mandoc(1) output to less(1) is never needed.

If you have a manual page in the current directory - say, table-sqlite.5 -
then just

   $ man -l table-sqlite.5

is sufficient, and if it's properly installed, as the opensmtpd-extras
package does it, then just

   $ man table-sqlite

does the job without even needing to worry about the current directory.

> Unfortunantly there aren't manuals for all of the `extras`.

Hmm, you may be right about that one, for example a table-python(5)
manual page doesn't appear to exist.

Yours,
  Ingo

Relayd "cannot load certificates" when using 2 'listen' statements in a relay

2020-12-19 Thread Unicorn 
Hello,

I am just figuring out relayd and am trying to make it listen both on
my ipv4 and ipv6 address. I have specified them with these macros:
```
$ext_ipv4 = "blah"
$ext_ipv6 = "expandedblah"
```


Then I have this relay with the two listen statements, to listen on
ipv4 and ipv6:
```
relay "proxy_secure" {
listen on $ext_ipv4 port 443 tls
listen on $ext_ipv6 port 443 tls

protocol "https"

forward to  port 1001
forward to  port 1002
}
```


Finally, this is the relevant part of the "https" protocol:
```
http protocol "https" {
...
tls keypair "firstdomain.tld"
tls keypair "seconddomain.tld"
}
```


With both listen statements, 'relayd -n' throws this error:

"/etc/relayd.conf:58: cannot load certificates for relay
proxy_secure4:443"

Removing either of the 'listen' statements resolves this issue, but
that would mean listening only on ipv4 OR ipv6. How could I solve this
issue? Am I missing something obvious? The manpage makes me believe
that having two 'listen' statements in a single relay is not an issue
per se, so why is relayd unhappy with this specific configuration?

I'd be very thankful for your guidance. :)

Best,
Unicorn

Re: OpenSMTPD-extras manual

2020-12-19 Thread Martijn van Duren 
On Sat, 2020-12-19 at 15:37 -0600, Edgar Pettijohn wrote:
> On Sat, Dec 19, 2020 at 08:02:19PM +0300, ??  wrote:
> > Hello.
> > Where can I find any manuals and examples regarding OpenSMTPD-extras?
> > Which table types are supported and do not have status "experimental"
> > like ldap tables?
> > E.g. what is opensmtpd-extras-python and how can I use it?
> > -- 
> > Best regards
> > Maksim Rodin
> > 
> 
> Your best bet is to git clone the repository and search for the tables, 
> etc you are interested in. If there is a manual simply `mandoc file | less`.
> 
> Unfortunantly there aren't manuals for all of the `extras`.
> 
> Good luck,
> 
> Edgar
> 
I don't play around too much with opensmtpd-extras and I don't do
python, but minor unrelated hint: mandoc -l will spawn less for
you and will include the tags-file.

martijn@

Re: OpenSMTPD-extras manual

2020-12-19 Thread Edgar Pettijohn 
On Sat, Dec 19, 2020 at 08:02:19PM +0300, ??  wrote:
> Hello.
> Where can I find any manuals and examples regarding OpenSMTPD-extras?
> Which table types are supported and do not have status "experimental"
> like ldap tables?
> E.g. what is opensmtpd-extras-python and how can I use it?
> -- 
> Best regards
> Maksim Rodin
>

Sorry didn't answer the python question. I'm not a python expert, but I 
suspect that you would write a script similar to the following perl:

Obviously untested, just a best guess.

#!/usr/bin/env perl

use common::sense;

our %state = ();

sub update {
$state{updated} = 1;

print STDERR "table perl updated\n";
}

sub check {
my ($service, $value, $key) = @_;
print STDERR "$service: $value: $key\n";
}

sub lookup {
my ($service, $value, $key) = @_;

print STDERR "$service: $value: $key\n";

return "test";
}

sub fetch {
my ($service, $value) = @_;

print STDERR "$service: $value\n";
return "test";
}

Then in smtpd.conf have something like:

table test python:/path/to/python/script.py

action "some_action" maildir alias

Re: OpenSMTPD-extras manual

2020-12-19 Thread Edgar Pettijohn 
On Sat, Dec 19, 2020 at 08:02:19PM +0300, ??  wrote:
> Hello.
> Where can I find any manuals and examples regarding OpenSMTPD-extras?
> Which table types are supported and do not have status "experimental"
> like ldap tables?
> E.g. what is opensmtpd-extras-python and how can I use it?
> -- 
> Best regards
> Maksim Rodin
>

Your best bet is to git clone the repository and search for the tables, 
etc you are interested in. If there is a manual simply `mandoc file | less`.

Unfortunantly there aren't manuals for all of the `extras`.

Good luck,

Edgar

very slow scrolling in xterm

2020-12-19 Thread Claus Assmann 
On one machine the scrolling in an xterm is very slow since the upgrade
to 6.7 and also in 6.8.
Now that I want to use this machine a bit more I'm wondering what
settings can be used to avoid that problem.
dmesg and Xorg log are (hopefully) attached, what other info could
help to track down the problem?

These .Xdefaults settings haven't changed for many years:
XTerm*saveLines:2000
XTerm*scrollKey:on
XTerm*VT100.Translations:   #overrideF4:secure()\n\
XTerm*ttyModes: erase \177
XTerm*background:   white
XTerm.WaitForMap:   True
XTerm*CharClass:33:48,37:48,45-46:48,64:48
XTerm*pointerShape: top_left_arrow
XTerm.reverseWrap:  True
XTerm.utmpInhibit:  True
XTerm*scrollBar:False
XTerm*font: fixed
XTerm*borderWidth:  3
XTerm*border  red:  
XTerm*internalBorder:   2
XTerm*jumpScroll:   on
XTerm*logInhibit:   on
XTerm*statusLine:   on
XTerm*visualBell:   on

-- 
Address is valid for this mailing list only, please do not reply
to it direcly, but to the list.
[   488.845] (--) checkDevMem: using aperture driver /dev/xf86
[   488.886] (--) Using wscons driver on /dev/ttyC4
[   488.948] 
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
[   488.949] Build Operating System: OpenBSD 6.8 amd64 
[   488.949] Current Operating System: OpenBSD neec.esmtp.org 6.8 GENERIC.MP#2 
amd64
[   488.950] Build Date: 24 November 2020  06:57:35AM
[   488.950]  
[   488.950] Current version of pixman: 0.38.4
[   488.950]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   488.950] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   488.950] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 19 18:47:12 
2020
[   488.955] (==) Using config file: "/etc/X11/xorg.conf"
[   488.955] (==) Using system config directory 
"/usr/X11R6/share/X11/xorg.conf.d"
[   488.977] (==) No Layout section.  Using the first Screen section.
[   488.977] (==) No screen section available. Using defaults.
[   488.977] (**) |-->Screen "Default Screen Section" (0)
[   488.977] (**) |   |-->Monitor ""
[   488.979] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   488.979] (==) Automatically adding devices
[   488.979] (==) Automatically enabling devices
[   488.979] (==) Not automatically adding GPU devices
[   488.979] (==) Max clients allowed: 256, resource mask: 0x1f
[   488.979] (WW) The directory "/usr/local/share/ghostscript/fonts" does not 
exist.
[   488.979]Entry deleted from font path.
[   488.980] (**) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/75dpi/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/local/lib/X11/fonts/local/,
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[   488.980] (**) ModulePath set to "/usr/X11R6/lib/modules"
[   488.980] (II) The server relies on wscons to provide the list of input 
devices.
If no devices become available, reconfigure wscons or disable 
AutoAddDevices.
[   488.980] (II) Loader magic: 0xc2c9f625940
[   488.980] (II) Module ABI versions:
[   488.980]X.Org ANSI C Emulation: 0.4
[   488.980]X.Org Video Driver: 24.1
[   488.980]X.Org XInput driver : 24.1
[   488.980]X.Org Server Extension : 10.0
[   488.980] (--) PCI:*(3@0:0:0) 10de:0421:1682:230b rev 161, Mem @ 
0xf800/16777216, 0xc000/536870912, 0xf600/33554432, I/O @ 
0xbc00/128
[   488.980] (II) LoadModule: "glx"
[   489.021] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[   489.087] (II) Module glx: vendor="X.Org Foundation"
[   489.087]compiled for 1.20.8, module version = 1.0.0
[   489.087]ABI class: X.Org Server Extension, version 10.0
[   489.097] (==) Matched nv as autoconfigured driver 0
[   489.097] (==) Matched vesa as autoconfigured driver 1
[   489.097] (==) Assigned the driver to the xf86ConfigLayout
[   489.097] (II) LoadModule: "nv"
[   489.098] (II) Loading /usr/X11R6/lib/modules/drivers/nv_drv.so
[   489.121] (II) Module nv: vendor="X.Org Foundation"
[   489.121]compiled for 1.20.8, module version = 2.1.21
[   489.121]Module class: X.Org Video Driver
[   489.121]ABI class: X.Org Video Driver, version 24.1
[   489.121] (II) LoadModule: "vesa"
[   489.123] (II) Loading /usr/X11R6/lib/modules/drivers/vesa_drv.so
[   4

OpenSMTPD-extras manual

2020-12-19 Thread Родин Максим 

Hello.
Where can I find any manuals and examples regarding OpenSMTPD-extras?
Which table types are supported and do not have status "experimental"
like ldap tables?
E.g. what is opensmtpd-extras-python and how can I use it?
--
Best regards
Maksim Rodin

Re: pf adaptive syncookie

2020-12-19 Thread mabi 
‐‐‐ Original Message ‐‐‐
On Friday, December 18, 2020 6:13 PM, Stuart Henderson  
wrote:

> And if it's anything like when I try it, you'll see some TCP connections
> failing when it is active too. Not everything fails. but e.g. if I have
> "set syncookies always" on a router, and run "ftp -o- 
> http://www.facebook.com/";
> from a machine behind it, it fails every time (it appears to connect
> immediately, but of course that's just syncookies - I never get a response
> after making a request over it until I disblae syncookies again).
> In that case where syncookies are active but things are failing I see
> PROXY and SYN_SENT states in pfctl -ss e.g.
>
> all tcp 157.240.221.35:80 <- 82.68.199.130:16476 PROXY:DST
> all tcp 82.68.199.130:16476 -> 157.240.221.35:80 SYN_SENT:CLOSED
>
> So I strongly recommend trying it with 'always' and see if things are
> broken for you. Otherwise if you set 'adaptive' you may get an unpleasant
> surprise sometime maybe much later when they do actually trigger.

Thanks for the tip. I just tried it on my OpenSD 6.7 firewall at home and 
exactly as you say I can't connect to facebook.com anymore (same for 
instagram.com). This is really weird, do you have any idea why? Is it a bug in 
the implementation of syncookies in OpenBSD or facebook.com doing weird things 
with TCP?

Re: pf.conf parser/lint

2020-12-19 Thread Peter Nicolai Mathias Hansteen 


> 19. des. 2020 kl. 14:50 skrev Aham Brahmasmi :
>>> 
>> 
>> Always put your interfaces into groups.  Identify based upon the groups.
> 
> In case there are more such simple rules of thumb, could you please
> share them?

I think that piece of advice is one of the more important ones you’re likely to 
get.

Adding to that, in my experience, the important thing is to make your 
configurations as simple as possible but not simpler :)

I would like to stress using pf.conf readability features as helpers to keeping 
your config maintainable, so

* use service names when feasible instead of port numbers,
* use tables for groups of IP addresses
* use macros where they do help readability
* write rules that specify only what would be deviation from the default (the 
defaults are, in general sane)
* before actually loading a changed config, run pfctl -vnf /etc/pf.conf to se 
what *actually* loads

That last one will among other things show you the result of the ruleset 
optimizer’s work, so when you see obviously generated table names, you likely 
have a set of rules that differ only in their source or destination address. 
That is a surprisingly frequent phenomenon, and for some reason more people 
than you would think are unaware that you can initialize a table or even load 
new content into one from a separate file.

If you haven’t already, you might glean a few useful bits from going through 
the PF tutorial slides at https://home.nuug.no/~peter/pftutorial/ 
 and links therein.

All the best,
Peter


—
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.






signature.asc
Description: Message signed with OpenPGP

Re: pf.conf parser/lint

2020-12-19 Thread Aham Brahmasmi 
Namaste Theo,

I apologize for reincarnating this thread.

> Sent: Friday, September 04, 2020 at 5:33 PM
> From: "Theo de Raadt" 
> To: "Tommy Nevtelen" 
> Cc: misc@openbsd.org
> Subject: Re: pf.conf parser/lint
>
> Tommy Nevtelen  wrote:
> 
> > On 04/09/2020 18.07, Brian Brombacher wrote:
> > > Well, let’s say a Linter doesn’t exist and you can’t invest time to make 
> > > one.  Do you have a lower environment, mirror-exact ideally, to run tests 
> > > on the pre-receive hook?
> > >
> > > It’s an interesting issue you’re trying to solve ;)
> > >
> > I didn't say I can't invest time. I just wondered if somebody else
> > knew of a solution before would try to dabble with it.. I do have a
> > lab env where stuff could be run but it would be very
> > un-efficient.. also openbsds interface names are based on the drivers
> > so I can't try stuff out in virtual machines since the interface names
> > would differ. I guess I could do some macros for those and change them
> > but this would be overkill for what I want to achieve. Also I do have
> > a lot of different setups and setting up test machines all of them
> > would cost a ton of money which is not worth it. And not what I was
> > after.
> 
> Always put your interfaces into groups.  Identify based upon the groups.

In case there are more such simple rules of thumb, could you please
share them?

It always helps little volks like me to learn and improve. I learnt
about packet tagging/policy based filtering from the pf user's guide. I
now use policy based filtering extensively.

> 
> Yes it is terrible that we have driver names exposed!  We should just
> have eth1-20 etc, but if one of your hardware devices fails, all the
> subsequent ones will renumber, so their names change, and you have
> precisely the same problem of exposed driver names.
> 
> We provide over FIVE ways to identify ports without using the hardware
> driver names, but hey... this discussion is about the theory you can
> check overall behaviour of a system by ignoring the important parts.
> 
> 

Dhanyavaad,
ab
-|-|-|-|-|-|-|--

Acer Extensa 5635Z RAM and net boards.

2020-12-19 Thread luis...@tin.it 
 Hi,I have install OpenBSD 6.8 on Acer Laptop with 2GB of RAM. 
I have upgrade the memory added a new 2 GB RAM bank.On boot the net interface 
not running.The dmesg is:
OpenBSD 6.8 (GENERIC.MP) #98: Sun Oct  4 18:13:26 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4105977856 (3915MB)
avail mem = 3966488576 (3782MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xb5ec (33 entries)
bios0: vendor Phoenix version "V1.3311" date 12/21/2009
bios0: Acer Extensa 5635Z
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET MCFG APIC BOOT SSDT SSDT SSDT SSDT
acpi0: wakeup devices USB0(S3) USB1(S3) USBR(S3) EHC1(S3) USB3(S3) EHC2(S3) 
HDEF(S3) GLAN(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Pentium(R) Dual-Core CPU T4300 @ 2.10GHz, 2095.34 MHz, 06-17-0a
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 1MB 64b/line 4-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Pentium(R) Dual-Core CPU T4300 @ 2.10GHz, 2094.99 MHz, 06-17-0a
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 1MB 64b/line 4-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 10 (P0P1)
acpiprt2 at acpi0: bus 2 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus 7 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiec0 at acpi0
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT1 model "AS09C31" serial 9418 type LION oem "SANYO"
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
"PNP0C14" at acpi0 not configured
acpipci0 at acpi0 PCI0
acpicmos0 at acpi0
"SYN1B20" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu1 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpitz0 at acpi0: critical temperature is 108 degC
acpivideo0 at acpi0: VGA_
acpivideo1 at acpi0: GFX0
acpivout0 at acpivideo1: DD02
cpu0: Enhanced SpeedStep 2095 MHz: speeds: 2100, 1600, 1200 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07
inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: apic 2 int 16, GM45, gen 4
"Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2 int 21
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 
addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi
azalia0: codecs: Conexant CX20561
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: msi
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x03: msi
pci2 at ppb1 bus 7
athn0 at pci2 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 2 int 19
athn0: could not reset chip
ppb2 at pci0 dev 28 function 5 "Intel 82801I PCIE" rev 0x03: msi
pci3 at ppb2 bus 9
alc0 at pci3 dev 0 function 0 "Attansic Technology L1C" rev 0xc0: msialc0: phy 
write timeout: phy 0, reg 29
alc0: phy write timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 29
alc0: phy write timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 29
alc0: phy write timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 29
alc0: phy write timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 29
alc0: phy write timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 29
alc0: phy write timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 29
alc0: phy read timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 29
alc0: phy read timeout: phy 0, reg 30
alc0: phy write timeout: phy 0, reg 30
alc0: could not disable RxQ/TxQ (0x)!
alc0: could not disable Rx/Tx MAC(0x)!