Re: riscv
On 2020-03-14 23:19, Mike Larkin wrote: On Sat, Mar 14, 2020 at 11:18:11PM -0700, Mike Larkin wrote: On Fri, Mar 13, 2020 at 02:12:19PM -0700, Jordan Geoghegan wrote: On 2020-03-13 09:50, Christian Weisgerber wrote: On 2020-03-13, "Peter J. Philipp" wrote: Any developer working on a riscv port and willing to share their unofficial work for possible future collaboration? I think I'd have heard by now if somebody was, so I'll go out on a limb and say no, nobody's working on a RISC-V port. I stumbled across this a while back, this guy at least claims to be attempting a port to RISC-V... https://github.com/MengshiLi/openbsd-riscv-notes We have a riscv64 kernel booting up to the rootdev prompt, and are working on PS, "We" here is my student team. This is not being done as part of the main OpenBSD development effort. We hope to be able to get this committed when it is ready but we are nowhere near that yet. getting plic working so that we can use virtio disks. The link above is from one of my students that is working on this. This is not in the main tree, and I'm not sure what it will take to get it there (we are using a newer version of clang than is in base). -ml That's great to hear, I'm excited to see what comes of this work, hats off to you and your students! It's a shame that clang was re-licensed, I hope we don't end up with a repeat of the gcc 4.x saga. I've heard a number of people lamenting about various improvements made in clang post relicencing, especially for non x86 arches such as powerpc. Jordan
Re: iwm wifi driver errors
On Sun, Mar 15, 2020 at 02:15:36PM +, b...@0x1bi.net wrote: > Have you installed the wireless firmware? > http://firmware.openbsd.org/firmware/ > yeah of course without the firmware the interface doesn't work, and now I'm using the wifi.
Re: Lot of errors as a "bad ip cksum" using Tor
On 2020-03-15, Carlos Lopez wrote: > Good morning, > > I've been seeing a lot of "bad ip cksum" error messages in my OpenBSD’s Tor > gateway, like these: from the tcpdump manual: IP and Protocol Checksum Offload Some network cards support IP and/or protocol checksum offload. Packet headers for such interfaces erroneously indicate a bad checksum, since the checksum is not calculated until after tcpdump sees the packet.
Re: Filesystem corruption on OpenBSD routers after power outage?
There is a discussion about sofdeps here http://openbsd-archive.7691.n7.nabble.com/What-are-the-disadvantages-of-soft-updates-td264283.html
Re: iwm wifi driver errors
Have you installed the wireless firmware? http://firmware.openbsd.org/firmware/
Re: Filesystem corruption on OpenBSD routers after power outage?
Good day, I have few questions, why are soft updates not on by default, and does they help consistency in case of failure, are they recom‐ mended to be turned on only in specific case ? Except my mis‐ take, they help keeping drive consistent, avoid the need for fsck for most hard failure cases, and only risk to have unused spare sectores which can be later recovered. Would not they help with the file system in general or some draw back with their use ? Regards, J.F.
Re: Lot of errors as a "bad ip cksum" using Tor
Sorry, my mistake. I have only one match rule configured as: match in all scrub (no-df max-mss 1440 random-id) -- Regards, C. L. Martinez On 15/03/2020, 13:33, "Carlos Lopez" wrote: Good morning, I've been seeing a lot of "bad ip cksum" error messages in my OpenBSD’s Tor gateway, like these: Mar 15 12:27:03.113986 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49964, dst 172.217.19.142:443] 172.22.55.4.49964 > 127.0.0.1.9040: SWE 3285379865:3285379865(0) win 65535 (ttl 63, id 46325, len 64, bad ip cksum 2341! -> 64a7) Mar 15 12:27:07.847299 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49965, dst 85.17.191.244:443] 172.22.55.4.49965 > 127.0.0.1.9040: SWE 755785425:755785425(0) win 65535 (ttl 63, id 9318, len 64, bad ip cksum 5f32! -> f536) Mar 15 12:27:08.355880 rule 1._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49966, dst 88.221.213.34:80] 172.22.55.4.49966 > 127.0.0.1.9040: SWE 2618743678:2618743678(0) win 65535 (ttl 63, id 53617, len 64, bad ip cksum 992c! -> 482b) Mar 15 12:27:09.337650 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49967, dst 85.17.191.242:443] 172.22.55.4.49967 > 127.0.0.1.9040: SWE 2709850134:2709850134(0) win 65535 (ttl 63, id 31872, len 64, bad ip cksum 71a! -> 9d1c) Mar 15 12:27:09.364017 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49968, dst 85.17.191.242:443] 172.22.55.4.49968 > 127.0.0.1.9040: SWE 855567415:855567415(0) win 65535 (ttl 63, id 58857, len 64, bad ip cksum 9db0! -> 33b3) As you can see all packets are allowed and I have configured my match rules as: match in all scrub (no-df max-mss 1440) match out on egress all scrub (no-df random-id reassemble tcp max-mss 1440) Any idea this error is always on? -- Regards, C. L. Martinez
Lot of errors as a "bad ip cksum" using Tor
Good morning, I've been seeing a lot of "bad ip cksum" error messages in my OpenBSD’s Tor gateway, like these: Mar 15 12:27:03.113986 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49964, dst 172.217.19.142:443] 172.22.55.4.49964 > 127.0.0.1.9040: SWE 3285379865:3285379865(0) win 65535 (ttl 63, id 46325, len 64, bad ip cksum 2341! -> 64a7) Mar 15 12:27:07.847299 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49965, dst 85.17.191.244:443] 172.22.55.4.49965 > 127.0.0.1.9040: SWE 755785425:755785425(0) win 65535 (ttl 63, id 9318, len 64, bad ip cksum 5f32! -> f536) Mar 15 12:27:08.355880 rule 1._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49966, dst 88.221.213.34:80] 172.22.55.4.49966 > 127.0.0.1.9040: SWE 2618743678:2618743678(0) win 65535 (ttl 63, id 53617, len 64, bad ip cksum 992c! -> 482b) Mar 15 12:27:09.337650 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49967, dst 85.17.191.242:443] 172.22.55.4.49967 > 127.0.0.1.9040: SWE 2709850134:2709850134(0) win 65535 (ttl 63, id 31872, len 64, bad ip cksum 71a! -> 9d1c) Mar 15 12:27:09.364017 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0: [orig src 172.22.55.4:49968, dst 85.17.191.242:443] 172.22.55.4.49968 > 127.0.0.1.9040: SWE 855567415:855567415(0) win 65535 (ttl 63, id 58857, len 64, bad ip cksum 9db0! -> 33b3) As you can see all packets are allowed and I have configured my match rules as: match in all scrub (no-df max-mss 1440) match out on egress all scrub (no-df random-id reassemble tcp max-mss 1440) Any idea this error is always on? -- Regards, C. L. Martinez
Re: riscv
On Sat, Mar 14, 2020 at 11:18:11PM -0700, Mike Larkin wrote: > On Fri, Mar 13, 2020 at 02:12:19PM -0700, Jordan Geoghegan wrote: > > > > > > On 2020-03-13 09:50, Christian Weisgerber wrote: > > > On 2020-03-13, "Peter J. Philipp" wrote: > > > > > > > Any developer working on a riscv port and willing to share their > > > > unofficial > > > > work for possible future collaboration? > > > I think I'd have heard by now if somebody was, so I'll go out on a > > > limb and say no, nobody's working on a RISC-V port. > > > > > > > I stumbled across this a while back, this guy at least claims to be > > attempting a port to RISC-V... > > > > https://github.com/MengshiLi/openbsd-riscv-notes > > > > We have a riscv64 kernel booting up to the rootdev prompt, and are working on PS, "We" here is my student team. This is not being done as part of the main OpenBSD development effort. We hope to be able to get this committed when it is ready but we are nowhere near that yet. > getting plic working so that we can use virtio disks. > > The link above is from one of my students that is working on this. This is not > in the main tree, and I'm not sure what it will take to get it there (we are > using a newer version of clang than is in base). > > -ml >
Re: riscv
On Fri, Mar 13, 2020 at 02:12:19PM -0700, Jordan Geoghegan wrote: > > > On 2020-03-13 09:50, Christian Weisgerber wrote: > > On 2020-03-13, "Peter J. Philipp" wrote: > > > > > Any developer working on a riscv port and willing to share their > > > unofficial > > > work for possible future collaboration? > > I think I'd have heard by now if somebody was, so I'll go out on a > > limb and say no, nobody's working on a RISC-V port. > > > > I stumbled across this a while back, this guy at least claims to be > attempting a port to RISC-V... > > https://github.com/MengshiLi/openbsd-riscv-notes > We have a riscv64 kernel booting up to the rootdev prompt, and are working on getting plic working so that we can use virtio disks. The link above is from one of my students that is working on this. This is not in the main tree, and I'm not sure what it will take to get it there (we are using a newer version of clang than is in base). -ml
