Re: DDB Crash Report About if_ether.c and arpinit() Gelen Kutusu
Hello again,
My device continues to crash almost every single day.
Unfortunately, due to the system freeze, I'm unable to generate a crash
report. These crashes typically result in the following errors:
kernel : protection fault trap, code=0
Stopped at arptimer+0x45: movq 0x10(%r15),%rdi
ddb{0}>
Is there a solution to this issue? What steps should I take?
Thanks.
On Sat, Jan 27, 2024 at 10:51 AM Samuel Jayden
wrote:
> Hello Misc,
>
> My OpenBSD 7.4 crash with this error messages;
>
> panic: kernel diagnostic assertion "ifp != NULL" failed: file
> "/usr/src/sys/net/inet/if_ether.c", line 758
>
> Stopped at db_enter+0x14: popq %rbp
>TID PID UID PRFLAGS PFLAGS CPUCOMMAND
> 399412 7311877 0x112 0 10dhcpleased
> 360364 39155 115 0x112 0 11slaacd
> 155433 90182 00x14000 0x2002softnet0
> 162438 45442 00x14000 0x2004systq
> * 37835 96688 00x14000 0x42000softclock
> db_enter() at db_enter+0x14
> panic(820a8599) at panic+0xc3
> __assert(821232bc,8209baea,2f6,820712c0) at
> __assert+0x29
> arpinit() at arpinit
> arptimer(825a38e8) at arptimer+0x5f
> softclock_thread(800021c1fd48) at softclock_thread+0x12b
> end trace frame: 0x0, count: 9
> https://www.openbsd.org/ddb.html describes the minimum info required in
> bug reports. Insufficient info makes it difficult to find and fix bugs.
> ddb{0}>
>
> Dmesg output of my device is in the attachment.
>
> Thank you in advance for your interest.
>
Re: M.2 Libre NIC
Follow-up question for Theo and the list: I think I get what Theo is implying here about libre firmware. I am really interested in the baseboard management controller (BMC) layer. Recently, I have become particularly interested in the OpenBMC project: https://www.openbmc.org/ Would this be considered FLOSS firmware? Thank you, Katie From: owner-m...@openbsd.org on behalf of Theo de Raadt Sent: Tuesday, January 30, 2024 5:42:29 PM To: Rohan Ganapavarapu <24rganapavar...@athenian.org> Cc: misc@openbsd.org Subject: Re: M.2 Libre NIC Attention : courriel externe | external email Rohan Ganapavarapu <24rganapavar...@athenian.org> wrote: > Do any of you guys know of a NIC card with OpenBSD support, fits in a M.2 > slot, and has libre firmware? > > I found the AR9462, which has libre firmware and is M.2, but the current > ath9k driver does not support it. libre firmware ha ha ha
Re: M.2 Libre NIC
Rohan Ganapavarapu <24rganapavar...@athenian.org> wrote: > Do any of you guys know of a NIC card with OpenBSD support, fits in a M.2 > slot, and has libre firmware? > > I found the AR9462, which has libre firmware and is M.2, but the current > ath9k driver does not support it. libre firmware ha ha ha
[offtopic] hardware routers failing
hello I have problem while running program i2pd and increasing bandwidth/number of tunnels, router fails and internet connectivity network-wide goes down, router restarts it after a few seconds up to minutes someone told me this: > For an ISP "customer premises equipment" router (home/officr router)? > That often means you made too many connections and exceeded the size of > NAT/firewall state table that they can cope with. Also for ISPs with > CGN, you might have a limited port-range that you're allowed to use and > can't make more connections once that has been exceeded. the 1st problem can be solved by custom router running OpenBSD, yes? how can I make sure it's 1st solution without buying/making router? ISP says there is nothing they can do or they act dumb can someone help me? thank you - best regards
Re: M.2 Libre NIC
I don't, what about the rest of system? I'm interested in libre hardware/firmware and maybe buy On Tue, January 30, 2024 6:13 pm, Rohan Ganapavarapu wrote: > Do any of you guys know of a NIC card with OpenBSD support, fits in a M.2 > slot, and has libre firmware? > > I found the AR9462, which has libre firmware and is M.2, but the current > ath9k driver does not support it. > > -- > rohan >
M.2 Libre NIC
Do any of you guys know of a NIC card with OpenBSD support, fits in a M.2 slot, and has libre firmware? I found the AR9462, which has libre firmware and is M.2, but the current ath9k driver does not support it. -- rohan
Re: my software is changing its future
Greetings Peter, Will the BSD port remain freely licensed? If so, thank you. -- jrmu IRCNow (https://ircnow.org)
Re: Power usage in Dell XPS 17
On Tue, Jan 30, 2024 at 12:02:37PM -0500, Jag Talon wrote: > Ah yes that's exactly my experience it looks like it might be the GPU at > fault. Good to know I wasn't the only one experiencing this. > > Do people know if there's a way to somehow turn off the GPU outside of BIOS? > Perhaps there's no way around that? > > On 1/30/24 11:54, Benjamin Stürz wrote: > > > I had the same issue with my TUXEDO Polaris 17 (AMD) w/ an RTX 2060M. > > It was also not possible to disable the GPU in the BIOS, > > so the battery life was miserable (45 min). > > > > That's why I later bought myself a used Thinkpad T450 and then a T480, > > which both played very nice with OpenBSD. > > -- > Jag Talon > > https://weirder.earth/@jag > https://jagtalon.net/ > https://aangat.lahat.computer/ One thing I did a while ago is made acpipwrres(4) issue an _OFF on the power resoruce attached to the GPU. That worked on one machine, but failed on another machine since that power resource also powered the screen. YMMV, and you'd need to write that diff yourself in acpipwrres_attach(). -ml
Re: Power usage in Dell XPS 17
Ah yes that's exactly my experience it looks like it might be the GPU at fault. Good to know I wasn't the only one experiencing this. Do people know if there's a way to somehow turn off the GPU outside of BIOS? Perhaps there's no way around that? On 1/30/24 11:54, Benjamin Stürz wrote: I had the same issue with my TUXEDO Polaris 17 (AMD) w/ an RTX 2060M. It was also not possible to disable the GPU in the BIOS, so the battery life was miserable (45 min). That's why I later bought myself a used Thinkpad T450 and then a T480, which both played very nice with OpenBSD. -- Jag Talon https://weirder.earth/@jag https://jagtalon.net/ https://aangat.lahat.computer/ OpenPGP_0x2F17E7825E755F08.asc Description: OpenPGP public key
Re: Power usage in Dell XPS 17
On 30.01.24 15:40, Jag Talon wrote: Unfortunately nothing about disabling a GPU in BIOS. I see everything else like Thunderbolt, fingerprint reader, microphone, etc. but no GPU. I'll keep looking and I'll check online as well perhaps I missed it! I had the same issue with my TUXEDO Polaris 17 (AMD) w/ an RTX 2060M. It was also not possible to disable the GPU in the BIOS, so the battery life was miserable (45 min). That's why I later bought myself a used Thinkpad T450 and then a T480, which both played very nice with OpenBSD.
Re: Power usage in Dell XPS 17
Unfortunately nothing about disabling a GPU in BIOS. I see everything else like Thunderbolt, fingerprint reader, microphone, etc. but no GPU. I'll keep looking and I'll check online as well perhaps I missed it! On 1/30/24 09:00, Dave Voutila wrote: Can you disable that in the uefi/bios settings? There may also be other power settings in there to tweak. While OpenBSD doesn't have the fanciest power management, the firmware can still do something to throttle or change power states of systems. -- Jag Talon https://weirder.earth/@jag https://jagtalon.net/ https://aangat.lahat.computer/ OpenPGP_0x2F17E7825E755F08.asc Description: OpenPGP public key
Re: Power usage in Dell XPS 17
Jag Talon writes: > I was wondering if I could get help with reducing power consumption on > my laptop. > > I have a Dell XPS 17 9700 that's newly running 7.4 (dmesg in > attachment) and previously it was running Fedora. Real-world usage > seems to have gone from 4 hrs to about 40 mins so I was wondering if > I'm missing anything: > > * I've tried using `apm -A`, `apm -L`, and `obsdfreqd` but any > improvement seems small. > > * I've tried lowering the resolution from 3840x2400 to 1680x1050, > which improved things a little bit, but not much. When `xenodm` or > `gdm` is not running it still gets pretty hot. > > * It still consumes a lot of power even when I'm not using it, so it > doesn't seem to be a CPU issue. > > Are there other things that I could try looking into? Does anyone have > experience with this laptop? > > I get the feeling that it could perhaps be the Nvidia GPU running in > the background even when it's unsupported? Is that possible? Can you disable that in the uefi/bios settings? There may also be other power settings in there to tweak. While OpenBSD doesn't have the fanciest power management, the firmware can still do something to throttle or change power states of systems.
Re: Clock stops working on OpenBSD qemu/kvm guest
Lévai, Dániel writes: > Turns out the clock stopped every night at the time when backups were > running and thus the VM was paused (saved, or 'managedsaved' if > someone uses libvirt) for a minute. > Not sure why, though; while I was testing pause/resume the clock > didn't stop, it just failed to get synced by ntpd(8). Maybe over time > the drift was too much? >From my experience, ntp daemons will try not to just jump the clock forward or backwards by too great an amount and instead increase or decrease time advancement to try to sync. It's indeed possible you drifted too far for ntpd to handle through this method. You might want to look into installing the Qemu guest agent in OpenBSD vms: https://marc.info/?l=openbsd-ports=158936392710472=2 Usually these agents handle properly setting the rtc after a suspend/resume cycle of the vm. (That's what the vmmci(4) driver does, for instance, in OpenBSD guests running atop OpenBSD's vmd(8).) > > Anyway, the rather curious thing was ntpd(8) not syncing the clock > properly after resume, so I ended up giving the 'trusted' option to > the server I'm using here. Strangely, it still took quite some time > [1], but in the end it managed to sync - so I guess this should work > in the long run. > > > [1] > Jan 30 11:50:33 ntpd[83421]: peer 148.6.0.1 now valid > Jan 30 11:54:37 ntpd[4758]: adjusting local clock by 23.831836s > Jan 30 11:54:37 ntpd[83421]: clock is now synced > Jan 30 11:54:37 ntpd[83421]: constraint reply from 9.9.9.9: offset 23.653130 > Jan 30 11:57:48 ntpd[4758]: adjusting local clock by 22.879877s > Jan 30 11:57:48 ntpd[83421]: clock is now unsynced > Jan 30 12:01:34 ntpd[4758]: adjusting local clock by 21.754396s > Jan 30 12:04:51 ntpd[4758]: adjusting local clock by 20.774539s > Jan 30 12:08:33 ntpd[4758]: adjusting local clock by 19.670413s > Jan 30 12:12:43 ntpd[4758]: adjusting local clock by 18.426017s > Jan 30 12:17:04 ntpd[4758]: adjusting local clock by 17.127167s > Jan 30 12:21:19 ntpd[4758]: adjusting local clock by 15.857846s > Jan 30 12:21:53 ntpd[4758]: adjusting local clock by 15.688043s > Jan 30 12:25:30 ntpd[4758]: adjusting local clock by 14.613690s > Jan 30 12:29:49 ntpd[4758]: adjusting local clock by 13.323883s > Jan 30 12:33:32 ntpd[4758]: adjusting local clock by 12.204646s > Jan 30 12:34:06 ntpd[4758]: adjusting local clock by 12.036162s > Jan 30 12:35:10 ntpd[4758]: adjusting local clock by 11.712658s > Jan 30 12:36:13 ntpd[4758]: adjusting local clock by 11.412870s > Jan 30 12:39:55 ntpd[4758]: adjusting local clock by 10.308062s > Jan 30 12:43:34 ntpd[4758]: adjusting local clock by 9.208613s > Jan 30 12:44:07 ntpd[4758]: adjusting local clock by 9.048595s > Jan 30 12:47:48 ntpd[4758]: adjusting local clock by 7.950845s > Jan 30 12:49:27 ntpd[4758]: adjusting local clock by 7.460912s > Jan 30 12:53:08 ntpd[4758]: adjusting local clock by 6.360250s > Jan 30 12:56:22 ntpd[4758]: adjusting local clock by 5.385971s > Jan 30 12:56:53 ntpd[4758]: adjusting local clock by 5.241883s > Jan 30 13:01:13 ntpd[4758]: adjusting local clock by 3.951414s > Jan 30 13:04:22 ntpd[4758]: adjusting local clock by 3.009970s > Jan 30 13:07:05 ntpd[4758]: adjusting local clock by 2.201024s > Jan 30 13:11:18 ntpd[4758]: adjusting local clock by 0.937320s > Jan 30 13:12:22 ntpd[4758]: adjusting local clock by 0.613777s > Jan 30 13:13:27 ntpd[4758]: adjusting local clock by 0.285335s > Jan 30 13:14:32 ntpd[83421]: clock is now synced
Re: Power usage in Dell XPS 17
Yes I've tried that as well it doesn't seem to have an effect. On 1/30/24 08:25, Louis Brauer wrote: * I've tried using `apm -A`, `apm -L`, and `obsdfreqd` but any improvement seems small. Did you stop and disable apmd when using obsdfreqd? That did the trick for me. Louis -- Jag Talon https://weirder.earth/@jag https://jagtalon.net/ https://aangat.lahat.computer/ OpenPGP_0x2F17E7825E755F08.asc Description: OpenPGP public key
Re: Power usage in Dell XPS 17
> * I've tried using `apm -A`, `apm -L`, and `obsdfreqd` but any > improvement seems small. Did you stop and disable apmd when using obsdfreqd? That did the trick for me. Louis
Power usage in Dell XPS 17
I was wondering if I could get help with reducing power consumption on my laptop. I have a Dell XPS 17 9700 that's newly running 7.4 (dmesg in attachment) and previously it was running Fedora. Real-world usage seems to have gone from 4 hrs to about 40 mins so I was wondering if I'm missing anything: * I've tried using `apm -A`, `apm -L`, and `obsdfreqd` but any improvement seems small. * I've tried lowering the resolution from 3840x2400 to 1680x1050, which improved things a little bit, but not much. When `xenodm` or `gdm` is not running it still gets pretty hot. * It still consumes a lot of power even when I'm not using it, so it doesn't seem to be a CPU issue. Are there other things that I could try looking into? Does anyone have experience with this laptop? I get the feeling that it could perhaps be the Nvidia GPU running in the background even when it's unsupported? Is that possible? Thank you. -- Jag Talon https://weirder.earth/@jag https://jagtalon.net/ https://aangat.lahat.computer/ OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023 r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68433362944 (65263MB) avail mem = 66339627008 (63266MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x52ed5000 (98 entries) bios0: vendor Dell Inc. version "1.27.1" date 09/25/2023 bios0: Dell Inc. XPS 17 9700 efi0 at bios0: UEFI 2.7 efi0: Dell rev 0x1 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT HPET APIC MCFG SSDT SSDT NHLT SSDT LPIT WSMT SSDT DBGP DBG2 SLIC BOOT MSDM SSDT DMAR SSDT ASF! BGRT FPDT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) XHC_(S0) XDCI(S4) HDAS(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz, 4988.38 MHz, 06-a5-02, patch 00f8 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,PKU,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 16MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz, 4888.61 MHz, 06-a5-02, patch 00f8 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,PKU,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 16MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz, 4788.64 MHz, 06-a5-02, patch 00f8 cpu2: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,PKU,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,MISC_PKG_CT,ENERGY_FILT,FB_CLEAR,RRSBA,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 16MB 64b/line 16-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz, 4689.08 MHz, 06-a5-02, patch 00f8 cpu3:
Re: Clock stops working on OpenBSD qemu/kvm guest
Turns out the clock stopped every night at the time when backups were running and thus the VM was paused (saved, or 'managedsaved' if someone uses libvirt) for a minute. Not sure why, though; while I was testing pause/resume the clock didn't stop, it just failed to get synced by ntpd(8). Maybe over time the drift was too much? Anyway, the rather curious thing was ntpd(8) not syncing the clock properly after resume, so I ended up giving the 'trusted' option to the server I'm using here. Strangely, it still took quite some time [1], but in the end it managed to sync - so I guess this should work in the long run. [1] Jan 30 11:50:33 ntpd[83421]: peer 148.6.0.1 now valid Jan 30 11:54:37 ntpd[4758]: adjusting local clock by 23.831836s Jan 30 11:54:37 ntpd[83421]: clock is now synced Jan 30 11:54:37 ntpd[83421]: constraint reply from 9.9.9.9: offset 23.653130 Jan 30 11:57:48 ntpd[4758]: adjusting local clock by 22.879877s Jan 30 11:57:48 ntpd[83421]: clock is now unsynced Jan 30 12:01:34 ntpd[4758]: adjusting local clock by 21.754396s Jan 30 12:04:51 ntpd[4758]: adjusting local clock by 20.774539s Jan 30 12:08:33 ntpd[4758]: adjusting local clock by 19.670413s Jan 30 12:12:43 ntpd[4758]: adjusting local clock by 18.426017s Jan 30 12:17:04 ntpd[4758]: adjusting local clock by 17.127167s Jan 30 12:21:19 ntpd[4758]: adjusting local clock by 15.857846s Jan 30 12:21:53 ntpd[4758]: adjusting local clock by 15.688043s Jan 30 12:25:30 ntpd[4758]: adjusting local clock by 14.613690s Jan 30 12:29:49 ntpd[4758]: adjusting local clock by 13.323883s Jan 30 12:33:32 ntpd[4758]: adjusting local clock by 12.204646s Jan 30 12:34:06 ntpd[4758]: adjusting local clock by 12.036162s Jan 30 12:35:10 ntpd[4758]: adjusting local clock by 11.712658s Jan 30 12:36:13 ntpd[4758]: adjusting local clock by 11.412870s Jan 30 12:39:55 ntpd[4758]: adjusting local clock by 10.308062s Jan 30 12:43:34 ntpd[4758]: adjusting local clock by 9.208613s Jan 30 12:44:07 ntpd[4758]: adjusting local clock by 9.048595s Jan 30 12:47:48 ntpd[4758]: adjusting local clock by 7.950845s Jan 30 12:49:27 ntpd[4758]: adjusting local clock by 7.460912s Jan 30 12:53:08 ntpd[4758]: adjusting local clock by 6.360250s Jan 30 12:56:22 ntpd[4758]: adjusting local clock by 5.385971s Jan 30 12:56:53 ntpd[4758]: adjusting local clock by 5.241883s Jan 30 13:01:13 ntpd[4758]: adjusting local clock by 3.951414s Jan 30 13:04:22 ntpd[4758]: adjusting local clock by 3.009970s Jan 30 13:07:05 ntpd[4758]: adjusting local clock by 2.201024s Jan 30 13:11:18 ntpd[4758]: adjusting local clock by 0.937320s Jan 30 13:12:22 ntpd[4758]: adjusting local clock by 0.613777s Jan 30 13:13:27 ntpd[4758]: adjusting local clock by 0.285335s Jan 30 13:14:32 ntpd[83421]: clock is now synced
Re: Communication between hosts on different network interfaces
Indeed, that is why I always added 0.0.0.0/0 Sorry for not mentioning it. On Tuesday, January 30, 2024 at 08:56:19 p.m. GMT+9, Stuart Henderson wrote: On 2024-01-07, All wrote: > This is very much doable with DHCP one liner: > add the following to your dhcpd.conf ((!) inside the block of your > 192.168.2.0/24 network) > option classless-static-routes 192.168.3.0/24 192.168.2.1; > > This will install static route into all machines in 192.168.2.0/24 network. On clients that follow the spec properly, that will *override* the default routes so they will have a route to 192.168.3.0/24 but no default route. You need to include the default route too, for example (assuming that should go via 192.168.2.254), option classless-static-routes 192.168.3.0/24 192.168.2.1, 0.0.0.0/0 192.168.2.254;
Re: Communication between hosts on different network interfaces
On 2024-01-07, All wrote: > This is very much doable with DHCP one liner: > add the following to your dhcpd.conf ((!) inside the block of your > 192.168.2.0/24 network) > option classless-static-routes 192.168.3.0/24 192.168.2.1; > > This will install static route into all machines in 192.168.2.0/24 network. On clients that follow the spec properly, that will *override* the default routes so they will have a route to 192.168.3.0/24 but no default route. You need to include the default route too, for example (assuming that should go via 192.168.2.254), option classless-static-routes 192.168.3.0/24 192.168.2.1, 0.0.0.0/0 192.168.2.254;
Re: my software is changing its future
please stop trolling On Tue, January 30, 2024 11:20 am, hahahahacker2...@airmail.cc wrote: > On 2024-01-29 23:31, beecdadd...@danwin1210.de wrote: > You are not using the right word. > When a software is open source, you can have your eyes on it and > fix its bug if it is broken, or use pledge and unveil to sandbox it. when open > source is to make sure a software is not malware, it is useless. Correct > yourself on future posts about open source. >> open source model benefits everyone because people can check and know there >> are no spyware/malware which affects people directly (use your software) or >> by using some service that uses your software like companies getting hacked >> left and right even the biggest companies get hacked because they are full of >> idiots who use proprietary code >> >> I am not familiar with the whole profiting thing, but the idea of >> paying only for compiled binaries sounds reasonable (and accepting donations >> if they don't) like if someone is on windows, how are they going to compile >> it? I never seen compiling done on MS Windows, so still profitable? this >> makes sense to me >> >> and if you have money and time think of us who don't like viruses on our >> computer because that's what proprietary is, virus >> >> thank you >> >> On Mon, January 29, 2024 3:07 pm, Peter J. Philipp wrote: >> >>> Hi, >>> >>> >>> >>> I have written an authoritative DNS server since 2005. This february >>> 16th >>> it will have the last Open Source release at version 1.8. The Open Source >>> development was a great prototype (for me), but I feel that asking for >>> donations is not going to make me a lot of money so I intend to port it to >>> Microsoft Windows (and perhaps Mac OS) in the next two years. >>> >>> >>> >>> I also intend to keep this part non-open source, and you may be able >>> to buy that port in a microsoft store. This is just part of a greater plan >>> to eventually enter the firewall market as a cloud based layer seven >>> firewall. Many systems already exist doing this, but I'm hoping my >>> approach will eventually get me a minute market share enough to pay some >>> bills. >>> >>> Now to my question(s): >>> >>> >>> >>> 1. Does the LibreSSL port to windows work? If so, great! That will >>> easen the porting work. >>> >>> 2. How hard would it be to port the imsg framework to Windows? I >>> understand there is descriptor passing involved which windows doesn't know. >>> But >>> I'm >>> confident that an alternative can be found. Does a windows port to imsg >>> already exist? >>> >>> 3. Just out of the blue, is there Windows efforts for pledge and >>> unveil? I don't intend to port them but leave them be just like the Linux >>> port that is already working. >>> >>> Please, don't feel annoyed that I'm porting to Windows. It is just an >>> effort to gain a larger marketshare of people that could use this as a >>> product. After >>> nearly 20 years I have finally a chance to make some money. Something I >>> never had before. Also version 1.8 will always be around, it will never >>> go away. And in a few years I do intend to release version 1.9 (without >>> windows port), >>> >>> >>> I'm a firm believer that the Open Source model benefits the cream of >>> the crop (the people with skills on top), but it doesn't benefit everyone. >>> I'm not >>> a hotshot programmer, I'm mediocre at best. This is why I want to adopt an >>> "open core" business model. This may be selling out to some. So >>> what. >>> >>> >>> Also the days of closed source are almost finished. People with >>> enough ML/AI power can devise decompilers that are able to make a fine >>> human understandable code (in C) of a binary. I have seen screenshots of >>> C >>> decompilers that label variables var0, var1, var2, var3 etc etc. So >>> non-coherent. But with a bit of AI the var1, var2, varN... can be >>> rearranged to something more understandable. This also means that open >>> source will win, but its significance will not be so obvious anymore. So I >>> give my "closed >>> source" part a few years before they are decompiled back into source. >>> Hopefully enough time to make a bit of money. >>> >>> >>> >>> Thank you for your help along the way for the last 19 years! And who >>> knows you can always fork my open source version and continue development >>> for all. It would be nice to see what you're doing with it and even >>> participate but my priority for the next two years is re-education as a >>> social worker and when I can to work on this windows port, so that I have >>> more options to make money in 2026 and beyond (before I reach retirement >>> age in 20 odd years). >>> >>> -peter >>> >>> >>> >>> Please reply with CC to me since I'm not on tech@ and misc@ lists for >>> the time being. >>> >>> >
Re: Communication between hosts on different network interfaces
Dear colleagues, A printer doesn't need internet access, and that is why I can block the internet access. The printer on the white network a label printer that just works. The other printer is a laser printer connected by USB to an Ubuntu computer on the white network, because that was easier than getting it working on OpenBSD; the same goes for the scanner. If only I had the right plug for my matrix printer, then maybe I would not need such complexity. Alas, they don't make matrix printers and parallel ports like they used to. Anyway, I return to my original inquiry. My barrier machine is indeed my primary gateway/firewall. I have configured the it in the way Brian and Nick recommended, except I added magic routes proposed by All, and it works as I want. I remain curious as to why it was necessary. Could someone explain my flaw in reasoning? Aside from setting those routes by DHCP, I am using vanila routes. In particular, the default route on the other computers is the barrier machine. With great humility, Ibsen
