Re: Freeze on OpenBSD 7.1
On Mon, Jul 18, 2022 at 12:14:20AM +0200, Tobias Fiebig wrote: > Heho, > If the machine just hardlocks (no panic), and the memory seems fine > (did you run memtest?), and there are no blown elcos on the > motherboard, my first guess would be testing another PSU; The > pattern sounds familiar. > > Also, the voltages do not necessarily look overly healthy... but > that might just be a fluke. [...] > Could you help me please ? Thank you very much ! > > Nicolas, Paris. > [...] > hw.sensors.it0.volt0=4.08 VDC (VCORE_A) > hw.sensors.it0.volt1=4.08 VDC (VCORE_B) > hw.sensors.it0.volt2=4.08 VDC (+3.3V) > hw.sensors.it0.volt3=6.85 VDC (+5V) > hw.sensors.it0.volt4=16.32 VDC (+12V) > hw.sensors.it0.volt5=4.01 VDC (-12V) > hw.sensors.it0.volt6=4.05 VDC (-5V) > hw.sensors.it0.volt7=6.85 VDC (+5VSB) > hw.sensors.it0.volt8=4.08 VDC (VBAT) > What Tobias wrote - voltages look way too much off. Onboard sensors are not always trusty, so I would go with real voltmeter. If you do not feel comfortable with electrical stuff, ask somebody for help. I would: 1. turn computer off, open the case 2. find molex connector https://en.wikipedia.org/wiki/Molex_connector#Disk_drive 3. pull it out of the case so I could reach it without touching insides of the case 4. turn computer on and start memtest 5. put black probe of voltmeter into black hole of molex 6. put red probe into another hole of molex (yellow or red) and see what voltages it measures Do not touch or move any cables beyound molex while the hw is powered on. This means if you move molex cable, it should not push on other cables - because some cables are very touchy touchy, like hdd data connectors. >From what I recall, PSU voltages are good when within +- 5% of what they should be. Yours look bad, because ~30% too big. Bear in mind, I am not electrical engineer. If you do not own voltmeter, this probably means you should ask for help of someone who does. -- Regards, Tomasz Rola -- ** A C programmer asked whether computer had Buddha's nature. ** ** As the answer, master did "rm -rif" on the programmer's home** ** directory. And then the C programmer became enlightened... ** ** ** ** Tomasz Rola mailto:tomasz_r...@bigfoot.com **
Re: Freeze on OpenBSD 7.1
Heho, If the machine just hardlocks (no panic), and the memory seems fine (did you run memtest?), and there are no blown elcos on the motherboard, my first guess would be testing another PSU; The pattern sounds familiar. Also, the voltages do not necessarily look overly healthy... but that might just be a fluke. With best regards, Tobias -Original Message- From: owner-m...@openbsd.org On Behalf Of e.co...@gmx.net Sent: Sunday, 17 July 2022 22:52 To: misc@openbsd.org Subject: Freeze on OpenBSD 7.1 Hello, I encounter a freeze on my OpenBSD 7.1 router. I have to reboot it. When that happens, there's nothing special in the /var/log/messages file : Jul 17 06:00:01 system syslogd[8620]: restart Jul 17 21:00:25 system syslogd[97469]: start Jul 17 21:00:25 system /bsd: OpenBSD 7.1 (GENERIC) #443: Mon Apr 11 17:55:15 MDT 2022 That happened several times. At first I thought that was a temperature related issue. So I installed a large USB fan on the case, and the case is at the room temperature of 25°C. I don't know how to diagnose that issue. Below you'll find : - dmesg output - vmstat output - systat output - sysctl output regarding temperature sensors Could you help me please ? Thank you very much ! Nicolas, Paris. OpenBSD 7.1 (GENERIC) #443: Mon Apr 11 17:55:15 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 2005192704 (1912MB) avail mem = 1927290880 (1838MB) random: boothowto does not indicate good seed mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb530 (73 entries) bios0: vendor American Megatrends Inc. version "4.6.5" date 07/10/2016 bios0: INTEL Corporation ChiefRiver acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) CPU 1037U @ 1.80GHz, 1796.23 MHz, 06-3a-09 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4. 2,x2APIC,POPCNT,DEADLINE,XSAVE,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 4 (RP04) acpiprt6 at acpi0: bus 5 (RP05) acpiprt7 at acpi0: bus 6 (RP06) acpiprt8 at acpi0: bus -1 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo acpibtn0 at acpi0: PWRB "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu0 at acpi0: C1(1000@1 mwait.1) acpipwrres0 at acpi0: FN00, resource for FAN0 acpipwrres1 at acpi0: FN01, resource for FAN1 acpipwrres2 at acpi0: FN02, resource for FAN2 acpipwrres3 at acpi0: FN03, resource for FAN3 acpipwrres4 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 106 degC acpitz1 at acpi0: critical temperature is 106 degC acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD01 acpivout1 at acpivideo0: DD02 acpivout2 at acpivideo0: DD03 acpivout3 at acpivideo0: DD04 acpivout4 at acpivideo0: DD05 acpivout5 at acpivideo0: DD06 acpivout6 at acpivideo0: DD07 acpivout7 at acpivideo0: DD08 cpu0: using VERW MDS workaround (except on vmm entry) pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 2500" rev 0x09 drm0 at inteldrm0 inteldrm0: msi, IVYBRIDGE, gen 7 xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi, xHCI 1.0 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB"
Freeze on OpenBSD 7.1
Hello, I encounter a freeze on my OpenBSD 7.1 router. I have to reboot it. When that happens, there's nothing special in the /var/log/messages file : Jul 17 06:00:01 system syslogd[8620]: restart Jul 17 21:00:25 system syslogd[97469]: start Jul 17 21:00:25 system /bsd: OpenBSD 7.1 (GENERIC) #443: Mon Apr 11 17:55:15 MDT 2022 That happened several times. At first I thought that was a temperature related issue. So I installed a large USB fan on the case, and the case is at the room temperature of 25°C. I don't know how to diagnose that issue. Below you'll find : - dmesg output - vmstat output - systat output - sysctl output regarding temperature sensors Could you help me please ? Thank you very much ! Nicolas, Paris. OpenBSD 7.1 (GENERIC) #443: Mon Apr 11 17:55:15 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 2005192704 (1912MB) avail mem = 1927290880 (1838MB) random: boothowto does not indicate good seed mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb530 (73 entries) bios0: vendor American Megatrends Inc. version "4.6.5" date 07/10/2016 bios0: INTEL Corporation ChiefRiver acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) CPU 1037U @ 1.80GHz, 1796.23 MHz, 06-3a-09 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4. 2,x2APIC,POPCNT,DEADLINE,XSAVE,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 4 (RP04) acpiprt6 at acpi0: bus 5 (RP05) acpiprt7 at acpi0: bus 6 (RP06) acpiprt8 at acpi0: bus -1 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo acpibtn0 at acpi0: PWRB "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu0 at acpi0: C1(1000@1 mwait.1) acpipwrres0 at acpi0: FN00, resource for FAN0 acpipwrres1 at acpi0: FN01, resource for FAN1 acpipwrres2 at acpi0: FN02, resource for FAN2 acpipwrres3 at acpi0: FN03, resource for FAN3 acpipwrres4 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 106 degC acpitz1 at acpi0: critical temperature is 106 degC acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD01 acpivout1 at acpivideo0: DD02 acpivout2 at acpivideo0: DD03 acpivout3 at acpivideo0: DD04 acpivout4 at acpivideo0: DD05 acpivout5 at acpivideo0: DD06 acpivout6 at acpivideo0: DD07 acpivout7 at acpivideo0: DD08 cpu0: using VERW MDS workaround (except on vmm entry) pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 2500" rev 0x09 drm0 at inteldrm0 inteldrm0: msi, IVYBRIDGE, gen 7 xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi, xHCI 1.0 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 7 Series HD Audio" rev 0x04: msi azalia0: no supported codecs ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi pci1 at ppb0 bus 1 em0 at pci1 dev 0 function 0 "Intel 82583V" rev 0x00: msi, address 0c:e8:5c:68:ce:78 ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi pci2 at ppb1 bus 2 em1 at pci2 dev 0
Re: relayd macros
Did you try it with quotes only and expand the variables with $var as in the
manpage?
This would point out if there is a bug in the -n check option and/or in the
parsing code of relayd.
-Stefan
Le 17 juil. 2022 16:08, Paul Pace a écrit :
On 2022-07-17 06:51, Stuart Henderson wrote:
> On 2022-07-17, Paul Pace wrote:
>> On 2022-07-17 00:28, Kapfhammer, Stefan wrote:
>>> You need to define a table.
>>> See relayed.conf manual page
>>> Section macros
>>
>> The macros section does include include creating tables that contain a
>> macro:
>>
>>
>> MACROS
>> Macros can be defined that will later be expanded in context.
>> Macro
>> names must start with a letter, digit, or underscore, and may
>> contain any
>> of those characters. Macro names may not be reserved words (for
>> example,
>> table, relay, or timeout). Macros are not expanded inside
>> quotes.
>>
>> For example:
>>
>> www1="10.0.0.1"
>> www2="10.0.0.2"
>> table {
>> $www1
>> $www2
>> }
>>
>>
>> I have created macros and tables:
>>
>> adminip1 = 203.0.113.5
>> adminip2 = 195.51.100.103
>
> Don't they need to be in quotes?
The configurations pass relayd -n checks and services work as expected
with
the following macro syntax:
adminip1=203.0.113.5
adminip2 = 203.0.113.6
adminip3="203.0.113.7"
adminip4 = "203.0.113.8"
>
>> table { 203.0.113.5 }
>> table {
>> $adminip1
>> $adminip2
>> }
>>
>> When I replace $adminip1 with or in a working
>> protocol
>> filter rule on line 20, I get a bunch of syntax errors beginning on
>> line
>> 20.
>>
>> Thank you,
>>
>> Paul
>>
>>
>>>
>>> -Stefan
>>>
>>>
>>>
>>>
>>> Le 16 juil. 2022 22:09, Paul Pace a écrit :
>>> Hello!
>>>
>>> I'm working on a relayd.conf configuration where I want to limit
>>> access
>>> to the path of an admin panel at /admin/ by using the from parameter
>>> in
>>> a protocol filter rule.
>>>
>>> I expect more than one IP address so want to use a macro with more
>>> than
>>> one IP address (or even more than one macro), similar to how I use
>>> them
>>> in httpd.conf and pf.conf:
>>>
>>> admin_ips = "{ 203.0.113.5, 198.51.100.103 }"
>>>
>>> When I add this to line 4 of relayd.conf and before creating a rule,
>>> I
>>> get:
>>>
>>> relayd -n
>>> /etc/realyd.conf:4: syntax error
>>>
>>> Have I just merely made a syntax error or is what I want to do not
>>> possible in relayd.conf?
>>>
>>> Thank you,
>>>
>>>
>>> Paul
>>
>>
RFC7432 (EVPN)
hi is there an plan or think about it to implement this RFC ? Holger
Re: Request: A script that lists all dependencies to any given package for facilitating offline installations
On 17/07-22 14:26, Allan Streib wrote: > On Sun, Jul 17, 2022, at 1:32 PM, ha...@tutanota.de wrote: > > > It would be useful to have a function that lists all dependencies. > > You can do this if you install the ports tree, see man 7 ports and > "print-run-depends" > > Also the sqlports package may help, though I've never used it. > Indeed, `sqlports` is needed. Example output below: % cd /usr/ports/ && make search key=sxiv Port: nsxiv-30 Path: graphics/nsxiv Info: neo simple X Image Viewer Maint: Thim Cederlund Index: graphics x11 L-deps: devel/libinotify graphics/imlib2 graphics/libexif graphics/libwebp B-deps: R-deps: devel/desktop-file-utils x11/gtk+3,-guic Archs: any Best Regards, Thim Cederlund
Re: Request: A script that lists all dependencies to any given package for facilitating offline installations
On Sun, Jul 17, 2022, at 1:32 PM, ha...@tutanota.de wrote: > It would be useful to have a function that lists all dependencies. You can do this if you install the ports tree, see man 7 ports and "print-run-depends" Also the sqlports package may help, though I've never used it.
Re: Request: A script that lists all dependencies to any given package for facilitating offline installations
On 2022-07-17, ha...@tutanota.de wrote: > Please implement it asap. How rude. That is not how things work here. > (it would be very easy, and of huge help) It's not as easy as you seem to think. -- Please keep replies on the mailing list.
Re: Multiple OpenBSD mirror issues for i386.
Stuart Henderson wrote: > On 2022-07-17, Brian Durant wrote: > > I am trying to download and install the i386 verion of OpenBSD 7.1 to an > > IBM/Lenovo T60. > > > > https://cdn.openbsd.org/pub/OpenBSD/7.1/i386/install71.img (and .iso) > > give me the following message: > > > > Error 503 Backend is unhealthy > > > > Backend is unhealthy > > Error 54113 > > > > Details: cache-cph2320057-CPH 1658065549 3028862290 > > > > Varnish cache server" Actually it was broken.. Now fixed.
Re: Multiple OpenBSD mirror issues for i386.
On 2022-07-17, Brian Durant wrote: > I am trying to download and install the i386 verion of OpenBSD 7.1 to an > IBM/Lenovo T60. > > https://cdn.openbsd.org/pub/OpenBSD/7.1/i386/install71.img (and .iso) > give me the following message: > > Error 503 Backend is unhealthy > > Backend is unhealthy > Error 54113 > > Details: cache-cph2320057-CPH 1658065549 3028862290 > > Varnish cache server" Works for me at the moment. > I have also downloaded both the 7.1 .iso and .img file from alternative > mirrors. The files have passed muster with SHA256 and signify. However, > when booting the USB pen drive that the images have been burned to, the > lead is >> OpenBSD/amd64 BOOT 3.53 - and then a few lines down, after > boot> I get the following: > > hd0a:/7.1/amd64/bsd.rd > > It looks to me as if someone uploaded the wrong files in under the wrong > architecture directory, and that it has propagated through the OpenBSD > mirrors. I have tried this a number of times, so I know that I haven't > just pressed the wrong link. I have gone into the mirrors manually under > the correct architecture directory and downloaded the files... I think you are booting from sonething other than the i386 img. The downloaded files look good to me. $ md5 install71.img MD5 (install71.img) = 064268d2d384e58d50a3bb288c635fbd $ strings install71.img | grep OpenBSD/amd64 $ strings install71.img | grep OpenBSD/i386 >> OpenBSD/i386 %s %s INSTALLATION NOTES for OpenBSD/i386 7.1 OpenBSD/i386 runs on standard PC computers and clones, based on Intel The OpenBSD/i386 binary distribution sets contain the binaries which base71 The OpenBSD/i386 7.1 base binary distribution. You MUST comp71 The OpenBSD/i386 Compiler tools. All of the tools relating OpenBSD/i386 7.1 works across a broad range of standard PCs and OpenBSD/i386 7.1 supports most SMP (Symmetrical MultiProcessor) the OpenBSD/i386 installation will only start terminals on Disks on OpenBSD/i386 are partitioned using either "MBR" Looks like i386. -- Please keep replies on the mailing list.
Multiple OpenBSD mirror issues for i386.
I am trying to download and install the i386 verion of OpenBSD 7.1 to an IBM/Lenovo T60. https://cdn.openbsd.org/pub/OpenBSD/7.1/i386/install71.img (and .iso) give me the following message: Error 503 Backend is unhealthy Backend is unhealthy Error 54113 Details: cache-cph2320057-CPH 1658065549 3028862290 Varnish cache server" I have also downloaded both the 7.1 .iso and .img file from alternative mirrors. The files have passed muster with SHA256 and signify. However, when booting the USB pen drive that the images have been burned to, the lead is >> OpenBSD/amd64 BOOT 3.53 - and then a few lines down, after boot> I get the following: hd0a:/7.1/amd64/bsd.rd It looks to me as if someone uploaded the wrong files in under the wrong architecture directory, and that it has propagated through the OpenBSD mirrors. I have tried this a number of times, so I know that I haven't just pressed the wrong link. I have gone into the mirrors manually under the correct architecture directory and downloaded the files... Brian
Re: relayd macros
On 2022-07-17, Paul Pace wrote:
> On 2022-07-17 00:28, Kapfhammer, Stefan wrote:
>> You need to define a table.
>> See relayed.conf manual page
>> Section macros
>
> The macros section does include include creating tables that contain a
> macro:
>
>
> MACROS
> Macros can be defined that will later be expanded in context.
> Macro
> names must start with a letter, digit, or underscore, and may
> contain any
> of those characters. Macro names may not be reserved words (for
> example,
> table, relay, or timeout). Macros are not expanded inside quotes.
>
> For example:
>
> www1="10.0.0.1"
> www2="10.0.0.2"
> table {
> $www1
> $www2
> }
>
>
> I have created macros and tables:
>
> adminip1 = 203.0.113.5
> adminip2 = 195.51.100.103
Don't they need to be in quotes?
> table { 203.0.113.5 }
> table {
> $adminip1
> $adminip2
> }
>
> When I replace $adminip1 with or in a working
> protocol
> filter rule on line 20, I get a bunch of syntax errors beginning on line
> 20.
>
> Thank you,
>
> Paul
>
>
>>
>> -Stefan
>>
>>
>>
>>
>> Le 16 juil. 2022 22:09, Paul Pace a écrit :
>> Hello!
>>
>> I'm working on a relayd.conf configuration where I want to limit access
>> to the path of an admin panel at /admin/ by using the from parameter in
>> a protocol filter rule.
>>
>> I expect more than one IP address so want to use a macro with more than
>> one IP address (or even more than one macro), similar to how I use them
>> in httpd.conf and pf.conf:
>>
>> admin_ips = "{ 203.0.113.5, 198.51.100.103 }"
>>
>> When I add this to line 4 of relayd.conf and before creating a rule, I
>> get:
>>
>> relayd -n
>> /etc/realyd.conf:4: syntax error
>>
>> Have I just merely made a syntax error or is what I want to do not
>> possible in relayd.conf?
>>
>> Thank you,
>>
>>
>> Paul
>
>
--
Please keep replies on the mailing list.
Re: make the mouse in cwm follow active window
Hello! Sorry for confusing. I noticed that for the first time on Ubuntu where I use cwm as well. I will check if it is different on OpenBSD. On Вс 17 июл 2022 11:48:20, Marcus MERIGHI wrote: > Hello! > > a23s4a2...@yandex.ru (Maksim Rodin), 2022.07.16 (Sat) 11:58 (CEST): > > When I have two windows on the screen (OpenBSD cwm) and > > move the active one using one of the build in cwm commands (window-snap-...) > > the window being moved looses focus when a mouse pointer is not above > > that window anymore and another window behind the first becomes active > > instead. > > Thank you for pointing me at the window-snap-* functions, never used > them before and they are handy! > > BUT I do not see what you see... when I, for instance, use > window-snap-up-right, then the mouse pointer gets moved, too. And, with > the mouse pointer, the focus as well. > > Am I doing something different than you? > > Marcus > > P.S.: I'm on -current as of the day before yesterday. > > > I suppose there is no way to make the active window being moved remain > > active > > because focus follows mouse but may be there is a way to make the > > mouse pointer follow the window being moved? > > > > -- > > Maksim Rodin > > -- С уважением, Родин Максим
Re: relayd macros
You need to define a table.
See relayed.conf manual page
Section macros
-Stefan
Le 16 juil. 2022 22:09, Paul Pace a écrit :
Hello!
I'm working on a relayd.conf configuration where I want to limit access
to the path of an admin panel at /admin/ by using the from parameter in
a protocol filter rule.
I expect more than one IP address so want to use a macro with more than
one IP address (or even more than one macro), similar to how I use them
in httpd.conf and pf.conf:
admin_ips = "{ 203.0.113.5, 198.51.100.103 }"
When I add this to line 4 of relayd.conf and before creating a rule, I get:
relayd -n
/etc/realyd.conf:4: syntax error
Have I just merely made a syntax error or is what I want to do not
possible in relayd.conf?
Thank you,
Paul
