Re: DHCP non-issues
On Wed, 21 Jul 2021 at 07:56, Stuart Henderson wrote: > > > Maybe the patch above fixes other problems for other people's machines. > > > The use case the diff helps is where you need working network when > another daemon is started. (the order of netstart vs dhcpleased needs > changing in /etc/rc too, otherwise it will always timeout on a v4-only > network, because dhcpleased doesn't run until later). > Thank you and Theo for the reply. Very helpful!
Re: DHCP non-issues
On Tue, 20 Jul 2021 at 13:00, Theo de Raadt wrote: > > The following diff will help the most common cases. netstart will pause > a little bit until at least one (v4 or v6) default route is installed. > In the most common cases, this is immediate. In the dynamic cases, the > delay is probably enough. We don't need to solve all potential problems.. > > In my test, on one machine, this did not pause long enough to bring up the hostname.wg0 interface. I see this in dmesg: pf enabled starting network ifconfig: no address associated with name running: kern.version=OpenBSD 6.9-current (GENERIC.MP) #138: Wed Jul 21 00:57:06 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Maybe the patch above fixes other problems for other people's machines.
Re: DHCP non-issues
On Mon, 19 Jul 2021 at 04:48, Christian Weisgerber wrote: > > Look guys, it's simple. > > If you want IPv6 (SLAAC) autoconfiguration, you set "inet6 autoconf" > for that interface. slaacd(8) will then automatically handle things. > > If you want IPv4 (DHCP) autoconfiguration, you set "inet autoconf" > for that interface. dhcpleased(8) will then automatically handle > things. If you require special DHCP options that dhcpleased(8) > doesn't include, then you don't enable autoconfigurarion and run > dhclient(8) instead, which can be extensively configured. > > Both slaacd(8) and dhcpleased(8) pass nameserver information to > resolvd(8), which adds those nameservers to /etc/resolv.conf unless > unwind(8) is running. If you don't want that to happen for some > other reason, you turn off resolvd(8). > Sounds like great information to put in current.html: https://www.openbsd.org/faq/current.html I think folks are surprised by the change and want to know how to handle the new daemons in certain situations. Your explanation above is very helpful and probably could be used in current.html I imagine the 7.0 "what's new" section will contain something similar. What do I need to do to have WireGuard start at boot when I want to use a hostname in my hostname.wg0 interface file? Currently, the interface doesn't come up as expected: ifconfig: no address associated with name Are these my options? a. use dhclient b. make a script to start the interface later c. use ip address > And that's it. > > -- > Christian "naddy" Weisgerber na...@mips.inka.de > Thanks! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: FAQ file sets missing cmdbox
On Tue, 25 Aug 2020 at 08:21, Aner Perez wrote: > > Looks like you may have been playing with the font sizes in your browser > preferences (e.g. > General > Fonts and Colors > Advanced... > Monospace > Size). I haven't changed from the default of what Firefox has. I just created a new firefox profile and have the same results as in the picture. At any rate, somehow it doesn't affect a wider audience and therefore it's fine as is.
Re: FAQ file sets missing cmdbox
On Tue, 25 Aug 2020 at 00:05, Greg Thomas wrote: > > I'm getting pretty old and struggle with stuff like this more and more these > days but I don't see what is "very difficult to follow" about the current > layout, and I'm not sure what's weird about it either? See if these photos illustrate the problem more clearly: https://imgur.com/a/zT6hAxi
FAQ file sets missing cmdbox
Hi, I don't think it's intended for the file sets section of the FAQ is be formatted so weird. If the current layout is correct, it's very difficult to follow. https://www.openbsd.org/faq/faq4.html#FilesNeeded I think the section needs to go into the cmdbox class, such as the simple install section above the file sets. Thanks, j.b.
This is the day pf was added
Hi, A little trip down memory lane, to 2001. Jun 24 PF added. Insane amounts of work done by dhartmei@, 2001 Thank you all for those who have worked on and contributed to pf. Keep up the great work! Best, j.b.
OpenBSD in the news...from a long time ago
Hi, Here's an old news clip about OpenBSD many folks haven't seen or have forgotten about. I don't know what year it's from or the hackathon that was taking place. Maybe someone can fill us in on the details? https://youtu.be/ka45HJu1MTM It features Theo, Bob, Ken, and a developer named Mickey. Unfortunately the background music is a bit loud at parts, though you're able to make out the dialog. Thank you all for continuing to work on OpenBSD! best, j.b.
67.html doesn't mention removal of rebound
Hi, rebound(8) was remove in January, but I don't see an entry in plus67.html or 67.html. Should it be mentioned in either one these pages? https://www.openbsd.org/plus67.html https://www.openbsd.org/faq/current.html thanks, j.b.
Re: Can't select files to upload in a browsers
On Fri, Dec 6, 2019, 2:58 AM dmitry.sensei wrote: > Firefox and Chromium browser, in the file selection window for upload, > does not show the contents of directories other than the Downloads > directory > See here https://www.reddit.com/r/openbsd/comments/eh25ma/firefox_how_to_select_file_to_upload/ >
Re: Nobody said it yet...
On Fri, Oct 18, 2019, 6:22 PM STeve Andre' wrote: > Happy birthday to OpenBSD! > Here, here. Have a great weekend to all the developers, contributors, and users of the project.
Re: What is you motivational to use OpenBSD
Thus said Mohamed Salah on Wed, 28 Aug 2019 16:32:29 +0200 I wanna put something in discussion, what's your motivational to use OPENBSD what not other bsd's what not gnu/Linux, if something doesn't work fine on openbsd and you love this os so much what will do? See stories here: https://runbsd.info/people/
OpenSMTPD on FLOSS Weekly
Hi All, Gilles was on FLOSS Weekly talking about OpenSMTPD: https://twit.tv/shows/floss-weekly/episodes/543 Enjoy the show! Now we just need Bob on to talk about spamd(8); Ingo to talk about mandoc; Nicholas to talk about tmux(1); Theo to talk about OpenBSD & pledge; Mark to talk about vmm; Henning to talk about pf(4). And all the other projects. Thanks all!
Re: Good Quality Microphone for Podcasts compatible with OpenBSD
Thus said Samuel Larkin on Sun, 11 Aug 2019 19:59:19 -0600 I personally have the 18i8 interface. What doesn't work is the proprietary software that comes with it. The interface works fine as an interface without the software. The software is needed to remap the outputs and change a couple of internal settings. When they are changed on a Windows box the settings are saved internally and persist between OSes. What are your microphones into the preamp and what software are you using to record on OpenBSD?
Re: makewhatis for man page changes
On Wed 24 Jul 2019 6:45 PM, Paco Esteban wrote: On Wed, 24 Jul 2019, Jungle Boogie wrote: Hi All, Turns out I don't know everything and I need to read man pages from time-to-time. I'm sure you're like me and also want to consult the man pages. How do you do it on applications you've installed from source? Reading makewhatis.8, I think this is the tool I would use. # makewhatis -D -a /usr/local/share/man As far as I know, that will create a mandoc.db on /usr/local/share/man That's an index for use with apropos(1) and whatis(1). but this doesn't work: $ man 1 nmap man: No entry for nmap in section 1 of the manual. What am I doing wrong? You have to tell man to look on other paths. That can be done setting the MANPATH env variable. In your case something like: MANPATH=/usr/local/share/man: $ MANPATH=/usr/local/share/man: $ echo $MANPATH /usr/local/share/man: $ man nmap man: No entry for nmap in the manual. However, this will work: $ man -M /usr/local/share/man: nmap That will at least get it to load the manpage. Creating a /etc/man.conf page and adding the entry into it gets man pages to load. Thanks for the tips and time!
makewhatis for man page changes
Hi All, Turns out I don't know everything and I need to read man pages from time-to-time. I'm sure you're like me and also want to consult the man pages. How do you do it on applications you've installed from source? Reading makewhatis.8, I think this is the tool I would use. # makewhatis -D -a /usr/local/share/man /usr/local/share/man//de/man1/nmap.1: Adding to database /usr/local/share/man//es/man1/nmap.1: Adding to database /usr/local/share/man//fr/man1/nmap.1: Adding to database /usr/local/share/man//hr/man1/nmap.1: Adding to database /usr/local/share/man//hu/man1/nmap.1: Adding to database /usr/local/share/man//it/man1/nmap.1: Adding to database /usr/local/share/man//ja/man1/nmap.1: Adding to database /usr/local/share/man//man1/aerc.1: Adding to database /usr/local/share/man//man1/curl-config.1: Adding to database /usr/local/share/man//man1/curl.1: Adding to database /usr/local/share/man//man1/dnscap.1: Adding to database /usr/local/share/man//man1/enchive.1.gz: Adding to database /usr/local/share/man//man1/endlessh.1: Adding to database ... but this doesn't work: $ man 1 nmap man: No entry for nmap in section 1 of the manual. What am I doing wrong? Thanks for any tips! $ sysctl kern.version kern.version=OpenBSD 6.5-current (GENERIC.MP) #139: Wed Jul 24 05:11:28 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Re: ssh-keygen specify max keysize for ed25519
Thus said Theo De Raadt on Tue, 02 Jul 2019 22:45:29 -0600 I think this is fine. At the point where the -b argument is matched, it is not clear what key-type is being handled. It is in your case, but not if -b and -t arguments are swapped. You can go read the source to see why. Cool! Thanks for the education!
ssh-keygen specify max keysize for ed25519
Hi All, $ ssh-keygen -t ed25519 -b 1000 Bits has bad value 1000 (too large) $ ssh-keygen -t ed25519 -b 2 key bits exceeds maximum 16384 Should the first example report the max bits like in the second example? This happens to be: kern.version=OpenBSD 6.5-current (GENERIC.MP) #86: Fri Jun 28 12:09:23 MDT 2019 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP arm64 but I believe I've seen this on amd64 as well. $ ssh -V OpenSSH_8.0, LibreSSL 3.0.0 thanks, j.b.
Re: One-shot upgrade script
On Thu 25 Apr 2019 1:02 AM, Christian Weisgerber wrote: I don't remember if I ever posted it, but I've been using an "upgrade" script to download bsd.rd, verify it, move it to /bsd, and reboot. With florian@'s additions in -current, I have now extended the script to download the sets and kick off an unattended upgrade. In the best case, you simply run # ./upgrade and the machine will upgrade itself without any further intervention. Thanks for posting. Am I reading this right - all sets would be downloaded? That would be fine on amd64 if you want X, but extra downloaded files/space for arm64.
Update man.openbsd.org with FreeBSD releases?
Hi All, Thankfully man.openbsd.org has many *BSD man pages available so I don't have to search many websites with a less inferior user interface. However, it seems the most recent FreeBSD manpages available are from the 11.1 release. 12.0 is the latest current release of FreeBSD. Should those manpages be availabl on man.openbsd.org as a dropdown selection? Thanks!
Re: pkg_add errors on current
On Sun 17 Feb 2019 12:25 PM, Stuart Henderson wrote: > On 2019-02-16, Jungle Boogie wrote: > > Hi All, > > > > Running openBSD snapshot on amd64 from today, but I think this has been an > > issue since > > perl 5.28 was added. > > Where did .../perl5/site_perl/amd64-openbsd/auto/List/Util/Util.so come from? > It isn't in ports. > > However you installed it, you either need to rebuild it or remove it. Thanks for the hint! After removing, pkg_add works as normal. > >
pkg_add errors on current
Hi All, Running openBSD snapshot on amd64 from today, but I think this has been an issue since perl 5.28 was added. # pkg_add -u perl:/usr/local/libdata/perl5/site_perl/amd64-openbsd/auto/List/Util/Util.so: undefined symbol 'PL_sv_no' perl:/usr/local/libdata/perl5/site_perl/amd64-openbsd/auto/List/Util/Util.so: undefined symbol 'PL_sv_undef' perl:/usr/local/libdata/perl5/site_perl/amd64-openbsd/auto/List/Util/Util.so: undefined symbol 'PL_sv_yes' Fatal error: can't parse Attempt to reload Scalar/Util.pm aborted. Compilation failed in require at /usr/libdata/perl5/amd64-openbsd/IO/Compress/Base/Common.pm line 8. BEGIN failed--compilation aborted at /usr/libdata/perl5/amd64-openbsd/IO/Compress/Base/Common.pm line 8. Compilation failed in require at /usr/libdata/perl5/amd64-openbsd/IO/Uncompress/RawInflate.pm line 9. BEGIN failed--compilation aborted at /usr/libdata/perl5/amd64-openbsd/IO/Uncompress/RawInflate.pm line 9. Compilation failed in require at /usr/libdata/perl5/amd64-openbsd/IO/Uncompress/Gunzip.pm line 12. BEGIN failed--compilation aborted at /usr/libdata/perl5/amd64-openbsd/IO/Uncompress/Gunzip.pm line 12. Compilation failed in require at /usr/libdata/perl5/OpenBSD/PackageRepository.pm line 434. Is this something I've done wrong with perl or an issue at the moment? Thanks!
Re: AWS
On Thu 29 Nov 2018 1:07 PM, Ahmad Bilal wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I was hoping if there is a official how-to-guide. Or at least semi-official. What official how-to-guide did you follow for vultr?
Re: Bluetooth Support
On Tue 30 Oct 2018 9:07 PM, Marco Menne wrote: > Hello there, > > I installed OpenBSD 6.4 on an old iMac from 2010 and nearly everything > works fine. The sound is cruel but this is a minor problem. > The Apple has a Bluetooth keyboard and I do not find a way to get it > working. I read in some forum that Bluetooth is not supported in OpenBSD. > Is this true? > I can use an USB-Keyboard, of course, but the Apple keyboard is fine and it > would be a little bit sad, if I had to change to an usb one. If you want bluetooth support, you'll need to go all the way back to a completely unsupport release from May 2014 for release 5.5. All releases since then have not had bluetooth. > > Greetings, Marco > - - - > Marco Menne > marco.menn...@gmail.com > GnuPG-Public-Key: > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x96A01AB59F6F7ECF
Re: doas behaviour in recent snapshot [was Re: 6.4 doas gives "command not found" if no #!/bin/sh up top]
Known bug. Use full path until it's fixed.
Re: panic booting with bsd.rd from the September 15 2018 snapshot
See this post: https://marc.info/?l=openbsd-tech&m=153713589005530&w=2 Doesn't hurt to search before posting.
Re: Running your own mail server
On Sat, Sep 8, 2018, 11:32 AM Peter N. M. Hansteen wrote: > On 09/08/18 19:55, jungle Boogie wrote: > > Just a general question about openbsd... > > > > I understand smtpd is in base for sending mail. Then we also have spam. > > Both very neat and useful! > > > > Is there a particular reason there is not a mail receiving agent in base? > > You're joking, right? > > man smtpd and references therein. There are also pointers in this thread > to running a full featured mail server on OpenBSD with smtpd from base. > > > Ah, thanks for setting me straight. >
Re: Running your own mail server
Hi all, Just a general question about openbsd... I understand smtpd is in base for sending mail. Then we also have spam. Both very neat and useful! Is there a particular reason there is not a mail receiving agent in base? Are the existing one sufficient enough for devs and there isn't enough desire to write one? Ken, Just curious, are you using pf to filter out the bad websites for you kids? I find that to be more challenging for our older daughter to not stumble into the bad stuff and not the wholesome sites like openbsd.org, which happens to be her homepage. ;) Best, J. B.
Re: Base httpd and addons like OpenSMTPD extras in ports?
Chris, What are httpd add-ons?
Re: Need an advice: Raspberry Pi3 B+ or Pine64 ROCK64
Hi Carlos, Check out this reddit post with similar questions. https://www.reddit.com/r/openbsd/comments/966wpe/running_on_a_sbcsoc_rock64_rpi_beaglebone_etc
tun interface and netmask
Hi All, Problem I want to solve: I would like the tun interface to 'support' more than one host. Right now, when I setup a tun interface, it's only activated on the dest IP, regardless of the netmask used. my /etc/hostname.tun0: inet 192.168.40.10 255.255.255.0 192.168.40.1 A workaround I've done, is adding a route: route add -inet 192.168.40.10/24 192.168.40.10 More info: Wireguard is using tun0 on machine A; I would like machine B and machine C to also access machine A, all on machine A's tun0 interface - without the need for additional tun interfaces. Fortunately the route trick above works. Question: Is the route add the legitimate way to do this? Can tun support more than one host, or is truly point-to-point? Thanks!
Re: arm64 recommendation Pine64 or Rock64
On Sun 08 Jul 2018 1:02 AM, Predrag Punosevac wrote: > Hi Misc, > > I am soliciting opinions about the arm64 board which I would like to buy > for a project. I am debating between Pine64 Pine 64 which has Allwinner > A64/H5 processor > > https://www.pine64.org/?product=pine-a64-lts I have the pine64 and pine64-lts. Both run openBSD arm64 very well for my limited uses. HDMI doesn't work, I don't think the gpio pins work, but search the mailing list to see if you find anything more. Booting the lts version will require a little extra effort: https://marc.info/?l=openbsd-misc&m=152363766318429&w=2 > > or much newer model Pine64 Rock64 with Rockchip RK3328 processor > > https://www.pine64.org/?product=rock64-media-board-computer Search the arm@ mailing list. I think there's some info on this board there. https://marc.info/?l=openbsd-arm&r=1&w=2 > > I eliminated Raspberry Pi 3 early on due to the proprietary firmware and > lack of storage drivers. > OpenBSD will run on the raspberry pi 3, although I've never done so. https://www.reddit.com/r/openbsd/comments/8asxq5/installing_openbsd_63_snapshots_on_raspberry_pi_3/ > > Best, > Predrag >
Re: hyper-threading...
On 22 June 2018 at 13:14, Dan Campbell wrote: > Just saw the news about you disabling hyper-threading by default on Intel > CPUs for security reasons, which I agree with. It would be nice to be able > to do this on systems that don't have a toggle for it in the BIOS, as it > increases single-threaded performance. So just wondering when your latest > distro will be coming out with this change, as I see your current version > came out in April? I would like to create a Linux live DVD/flash drive that > I could boot to toggle hyper-threading off on Intel systems running Windows, > or to create a dual-boot situation for those who want to use Linux part-time. > It could also be useful for updating processor microcode, which can't be > done under Windows. Thanks, > The current release (not distro) already has a fix for it: https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/010_intelfpu.patch.sig Download 6.3 run syspatch, which will fetch all available patches for 6.3: https://www.openbsd.org/errata63.html > Dan -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: firefox crashes when password field is focused
On 19 June 2018 at 16:24, Leahcim wrote: > Title pretty much says it. > > Whenever I click on a password field on a website firefox crashes. > This is on current w/ newest firefox and is reproducible on every > password field on every site I tried (although usernames work fine) > and is reproducible with all combinations of settings including > default. It has persisted for the last few days. > You'll need to read this: https://marc.info/?l=openbsd-tech&m=152848412106216&w=2 Which says: Check here the readme of firefox and dbus on the info and howto: /usr/local/share/doc/pkg-readmes
mailing list archive page update recommendation
Hi All, It might be worth considering removing the reference to suish.net, as the weekly and daily lists haven't been updated since November 2017. https://www.openbsd.org/mail.html#Archives http://www.squish.net/pipermail/owc/ http://www.squish.net/pipermail/odc/ You might also consider linking here: http://openbsd-archive.7691.n7.nabble.com/
lock order reversal in dmesg?
Hi All, With one of the snapshots from Friday 1 June, I'm seeing more info in my dmesg than I typically do. Has some extra debugging been turned on? lock order reversal: 1st 0xff00bb0eecd8 vmmaplk (&map->lock) @ /usr/src/sys/uvm/uvm_fault.c:1441 2nd 0x80081138 drmdevlk (&dev->struct_mutex) @ /usr/src/sys/dev/pci/drm/i915/i915_gem.c:1801 lock order "&dev->struct_mutex"(rwlock) -> "&map->lock"(rwlock) first seen at: #0 witness_checkorder+0x494 #1 _rw_enter+0x56 #2 vm_map_lock_ln+0xac #3 uvm_map+0x191 #4 km_alloc+0x15a #5 bus_space_map+0x13b #6 i915_alloc_ifp+0x99 #7 intel_gtt_chipset_setup+0x152 #8 intel_enable_gtt+0x18 #9 i915_gem_init_hw+0x36 #10 i915_gem_init+0x23e #11 i915_driver_load+0xfb1 #12 inteldrm_attach+0x35b #13 config_attach+0x1fe #14 pci_probe_device+0x4e1 #15 pci_enumerate_bus+0xa7 #16 config_attach+0x1fe #17 mainbus_attach+0x237 #18 config_attach+0x1fe lock order "&map->lock"(rwlock) -> "&dev->struct_mutex"(rwlock) first seen at: #0 witness_checkorder+0x494 #1 _rw_enter_write+0x53 #2 i915_gem_object_wait_rendering__nonblocking+0x1ea #3 i915_gem_fault+0x137 #4 drm_fault+0x18a #5 uvm_fault+0x733 #6 trap+0x509 #7 Xalltraps_untramp+0xec lock order reversal: 1st 0x81ce85f8 &sched_lock (&sched_lock) @ /usr/src/sys/kern/kern_synch.c:444 2nd 0x8007e270 &dev_priv->irq_lock (&dev_priv->irq_lock) @ /usr/src/sys/dev/pci/drm/i915/intel_ringbuffer.c:1672 lock order "&dev_priv->irq_lock"(mutex) -> "&sched_lock"(sched_lock) first seen at: #0 witness_checkorder+0x494 #1 ___mp_lock+0x70 #2 schedclock+0x30 #3 hardclock+0xd5 #4 lapic_clockintr+0x2f #5 Xresume_lapic_ltimer+0x22 #6 x86_bus_space_mem_read_4+0x7 #7 i915_irq_handler+0x107 #8 intr_handler+0x68 #9 Xintr_ioapic_level11_untramp+0x141 #10 acpicpu_idle+0x232 #11 cpu_idle_cycle+0x10 lock order "&sched_lock"(sched_lock) -> "&dev_priv->irq_lock"(mutex) first seen at: #0 witness_checkorder+0x494 #1 _mtx_enter+0x31 #2 i9xx_ring_put_irq+0x35 #3 __i915_wait_request+0x344 #4 i915_gem_object_wait_rendering__nonblocking+0x1c6 #5 i915_gem_fault+0x137 #6 drm_fault+0x18a #7 uvm_fault+0x733 #8 trap+0x509 #9 Xalltraps_untramp+0xec Thanks!
Re: octeon snapshots
Thus said Pedro Caetano on Mon, 14 May 2018 22:40:40 +0100 Hi misc@, I've been using a edge router lite for the past one and a half year as my home router. (providing a few network services, besides that it has an ipsec tunnel setup similar to dn42.net implementation) I'm running a few daemons, mostly from base: nsd, unbound, ntpd, bgpd, isakmpd, dhcpd, relayd, httpd, slowcgi, rtadvd And a few from ports: vnstatd, igmpproxy, arpwatch In the last 30 days, a strange behaviour has been introduced on this device. When the system is upgraded, either using bsd.rd or doing a binary upgrade, *sometimes* the system livelocks. One is able to login using the serial console, but shortly after a massive slowdown occurs, rendering the system unusable. Powercycling makes the box usable again. Sometimes not on the first try. Unfortunately, I haven't been able to spot any interesting message on dmesg and/or logfiles. Please let me know what additional information is needed in order to debug this. Does it seem to take a certain number of days before the system slow down occurs, or can it happen after a few hours of uptime?
Re: CVE-2018-8897
On 5:58PM, Thu, May 10, 2018 Theo de Raadt wrote: > > >Dare I ask what lead to OpenBSD not being affected. > > > >Sorry if it is a dumb question but since this hit FreeBSD as well I am > >wondering > >what OpenBSD did differently. > > > >Was this caught in an audit? > > > >I am just curious about causality that kept OpenBSD in the clear of this one > >that made such headlines yesterday. > > > We didn't chase the fad of using every Intel cpu feature. > Once again, the puffer protects us again - secure by default.
artwork.html not listing 6.3 release
Hi All, I noticed the 6.3 release is not listed here: https://www.openbsd.org/artwork.html I'm assuming it would be listed and would link here: https://www.openbsd.org/63.html Sorry for the noise if 6.3 is intentionally absent from the artwork page.
dmesg - Asus X555LA
Hi All, Figured I'd see what happens when I load openBSD on a laptop that I haven't used very much. dmesg shows several 'not configured' devices, including the Atheros AR9485 wifi card. Looks like in March 2014 Stefan said the wifi wasn't ready yet. Given that four years have passed, I'll probably just use my urtwn0 https://marc.info/?l=openbsd-tech&m=139963461524621&w=2 OpenBSD 6.3-current (GENERIC.MP) #11: Tue Apr 24 23:05:32 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4176748544 (3983MB) avail mem = 4042244096 (3854MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xa47be000 (26 entries) bios0: vendor American Megatrends Inc. version "X555LAB.602" date 07/27/2016 bios0: ASUSTeK COMPUTER INC. X555LAB acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT ECDT MCFG HPET SSDT UEFI SSDT LPIT ASF! SSDT SSDT SSDT SSDT PCCT SSDT SSDT DMAR BGRT TPM2 MSDM acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP06(S4) RP07(S4) RP08(S4) PXSX(S4) RP05(S4) GLAN(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) Core(TM) i3-5020U CPU @ 2.20GHz, 2197.10 MHz 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,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.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i3-5020U CPU @ 2.20GHz, 2196.83 MHz 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i3-5020U CPU @ 2.20GHz, 2196.83 MHz 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i3-5020U CPU @ 2.20GHz, 2196.83 MHz cpu3: 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,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,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 1 (RP01) acpiprt5 at acpi0: bus -1 (RP02) acpiprt6 at acpi0: bus 2 (RP03) acpiprt7 at acpi0: bus 3 (RP04) acpiprt8 at acpi0: bus -1 (RP06) acpiprt9 at acpi0: bus -1 (RP07) acpiprt10 at acpi0: bus -1 (RP08) acpiprt11 at acpi0: bus -1 (RP05) acpicpu0 at acpi0: C3(200@506 mwait.1@0x60), C2(200@230 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@506 mwait.1@0x60), C2(200@230 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@506 mwait.1@0x60), C2(200@230 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@506 mwait.1@0x60), C2(200@230 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PG00, resource for PEG0 acpipwrres1 at acpi0: PG01, resource for PEG1 acpipwrres2 at acpi0: PG02, resource for PEG2 acpipwrres3 at acpi0: WRST acpipwrres4 at acpi0: WRST acpipwrres5 at acpi0: WRST acpipwrres6 at acpi0: WRST ac
dmesg - nanoPI A64
Hi All, dmesg of a nanoPi A64: http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=159 Absolutely no issues with the openBSD installer. My serial break out cables seem to be backwards so at first I wasn't seeing anything on the console. After I swapped receive/transmit, everything was fine. I did connect the board to a HDMI monitor and briefly saw the boot process, but soon after, the monitor went blank. $ dmesg OpenBSD 6.3-current (GENERIC.MP) #86: Wed Apr 25 02:38:55 MDT 2018 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 947683328 (903MB) avail mem = 888680448 (847MB) mainbus0 at root: Pine64+ cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4 efi0 at mainbus0: UEFI 2.7 efi0: Das U-Boot rev 0x0 psci0 at mainbus0: PSCI 0.2 agtimer0 at mainbus0: tick rate 24000 KHz simplebus0 at mainbus0: "soc" sxiccmu0 at simplebus0 sxipio0 at simplebus0: 103 pins ampintc0 at simplebus0 nirq 224, ncpu 4 ipi: 0, 1: "interrupt-controller" sxiccmu1 at simplebus0 sxipio1 at simplebus0: 13 pins sximmc0 at simplebus0 sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma ehci0 at simplebus0 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 addr 1 com0 at simplebus0: ns16550, no working fifo com0: console sxitwi0 at simplebus0 iic0 at sxitwi0 sxirtc0 at simplebus0 dwxe0 at simplebus0: address ff:ff:ff:ff:ff:ff rgephy0 at dwxe0 phy 0: RTL8169S/8110S/8211 PHY, rev. 5 rgephy1 at dwxe0 phy 7: RTL8169S/8110S/8211 PHY, rev. 5 gpio0 at sxipio0: 32 pins gpio1 at sxipio0: 32 pins gpio2 at sxipio0: 32 pins gpio3 at sxipio0: 32 pins gpio4 at sxipio0: 32 pins gpio5 at sxipio0: 32 pins gpio6 at sxipio0: 32 pins gpio7 at sxipio0: 32 pins gpio8 at sxipio1: 32 pins simplefb0 at mainbus0: 1920x1080 wsdisplay0 at simplefb0 mux 1 wsdisplay0: screen 0-5 added (std, vt100 emulation) cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4 cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4 cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4 scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct removable sd0: 30436MB, 512 bytes/sector, 62333952 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets bootfile: sd0a:/bsd boot device: sd0 root on sd0a (8f2cc65f9ef32a85.a) swap on sd0b dump on sd0b Thanks!
Thank you for the updated arm64 packages
Hi All, Just wanted to pass along my thanks for updated arm64 packages. I have very few installed, but it's nice to see this arch isn't neglected. Thanks to all the ports maintainers, who practically have full time jobs maintaining all the ports. Thanks for everyone who's donated to the project - either via currency or in the form of hardware. Keep kicking butt! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: 4-ports router under $150
Thus said Lilit-aibolit on Thu, 12 Apr 2018 14:39:04 +0300 I haven't tried via serial because I used vga+usb keyboard. However I'll definitely try that lan-serial port. Did you get a chance to try the BIOS via serial connection? https://pt.aliexpress.com/item/Celeron-J1900-Mini-pc-free-shipping-micro-sd-two-usb-and-four-lan-laptop-overwatch-Computer/32794678352.html?spm
Re: dmesg for edgerouter lite
Thus said Sean Murphy on Fri, 13 Apr 2018 22:03:48 -0400 Hello all, Also upgraded the ERL to 6.3, dmesg to follow. You might enjoy this post: https://www.undeadly.org/cgi?action=article;sid=20180418073437
carp ssh setup
Hi All, I have a very simple carp setup - basically I want ssh access if the master goes offline. In theory, this are functioning correctly. In practice, it seems the backup is taking over way too often - the backup takes over way too often, even when I'm ssh'd to the master device. master: inet 192.168.0.99 255.255.255.0 192.168.0.255 vhid 1 carpdev dwxe0 state master advskew 1 pass pass backup: inet 192.168.0.99 255.255.255.0 192.168.0.255 vhid 1 carpdev cnmac0 state backup advskew 10 pass pass Both are running openBSD snapshots of the latest for their platform (master is arm64; backup is octeon). I see there is a sysctl I can tweak regarding logging, but I don't know if that's what I need to do in order to find out what's happening. Crude drawing: https://imgur.com/a/zcoU5 Is anyone else running carp in this simplistic of a manner that could tell me of an issue? -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: pine64-lts - can't detect disk
On 13 April 2018 at 11:05, jungle Boogie wrote: > > Thanks for the reply. I think I'm closer, but there still seems to be > some gaps... It's working now! I had taken a shortcut earlier. At the installer prompt, I incorrectly selected upgrade to take a shortcut. Now thinking about it, openBSD wasn't installed so it didn't know the partition layout. Thanks for the the assistance, Jonathan. Thanks for Peter and all the developers of openBSD. dmesg of openBSD installed and running (not sure if it's different than what's above): pine64# dmesg OpenBSD 6.3-current (GENERIC.MP) #69: Thu Apr 12 14:11:59 MDT 2018 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 2021416960 (1927MB) avail mem = 1927913472 (1838MB) mainbus0 at root: SoPine with baseboard cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4 efi0 at mainbus0: UEFI 2.7 efi0: Das U-Boot rev 0x0 psci0 at mainbus0: PSCI 0.2 agtimer0 at mainbus0: tick rate 24000 KHz simplebus0 at mainbus0: "soc" syscon0 at simplebus0: "syscon" sxiccmu0 at simplebus0 sxipio0 at simplebus0: 103 pins ampintc0 at simplebus0 nirq 224, ncpu 4 ipi: 0, 1: "interrupt-controller" sxiccmu1 at simplebus0 sxipio1 at simplebus0: 13 pins sxirsb0 at simplebus0 axppmic0 at sxirsb0 addr 0x3a3: AXP803 sximmc0 at simplebus0 sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma ehci0 at simplebus0 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 addr 1 ehci1 at simplebus0 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 addr 1 com0 at simplebus0: ns16550, no working fifo com0: console dwxe0 at simplebus0: address 02:ba:43:50:f0:a3 rgephy0 at dwxe0 phy 1: RTL8169S/8110S/8211 PHY, rev. 5 sxirtc0 at simplebus0 gpio0 at sxipio0: 32 pins gpio1 at sxipio0: 32 pins gpio2 at sxipio0: 32 pins gpio3 at sxipio0: 32 pins gpio4 at sxipio0: 32 pins gpio5 at sxipio0: 32 pins gpio6 at sxipio0: 32 pins gpio7 at sxipio0: 32 pins gpio8 at sxipio1: 32 pins cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4 cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4 cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4 scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct removable sd0: 30436MB, 512 bytes/sector, 62333952 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets bootfile: sd0a:/bsd boot device: sd0 root on sd0a (cada93f8e15fb69e.a) swap on sd0b dump on sd0b
Re: pine64-lts - can't detect disk
On 13 April 2018 at 09:39, Jonathan Gray wrote: > On Fri, Apr 13, 2018 at 09:19:23AM -0700, jungle Boogie wrote: >> On 13 April 2018 at 08:30, jungle Boogie wrote: >> > Hi All, >> > >> > So between Peter Hessler's post here: >> > https://bsd.network/@phessler/99389809617980837 >> > >> > And the install instructions for arm64: >> > https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64 >> > >> > I have the pine64-lts: >> > https://www.pine64.org/?page_id=46823 >> >> >> Forgot the dmesg: >> >> OpenBSD 6.3-current (RAMDISK) #235: Thu Apr 12 14:38:28 MDT 2018 >> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK >> real mem = 2015993856 (1922MB) >> avail mem = 1915539456 (1826MB) >> mainbus0 at root: Pine64+ > > The sopine U-Boot image does not currently include the sopine device > tree as there isn't a sopine device tree in U-Boot. > > Until that changes, on the msdos/efi partition create an 'allwinner' > directory, install the dtb port and copy > /usr/local/share/dtb/arm64/allwinner/sun50i-a64-sopine-baseboard.dtb > to > allwinner/sun50i-a64-pine64-plus.dtb > > or to a different path and change fdtfile in the U-Boot environment. > > Though it isn't clear if that is the appropriate device tree. > Thanks for the reply. I think I'm closer, but there still seems to be some gaps... my sd card: $ ls /mnt/allwinner/ sun50i-a64-pine64-plus.dtb => run findfdt ## Error: "findfdt" not defined => load mmc 0:1 ${fdt_addr_r} allwinner/sun50i-a64-pine64-plus.dtb 12734 bytes read in 35 ms (354.5 KiB/s) => load mmc 0:1 ${kernel_addr_r} efi/boot/bootaa64.efi 98588 bytes read in 43 ms (2.2 MiB/s) => bootefi ${kernel_addr_r} ${fdt_addr_r} However, now it sees the sd card but can't use it: Available disks are: sd0. Which disk is the root disk? ('?' for details) [sd0] sd0 is not a valid root disk. Available disks are: sd0. Which disk is the root disk? ('?' for details) [sd0]
Re: pine64-lts - can't detect disk
On 13 April 2018 at 08:30, jungle Boogie wrote: > Hi All, > > So between Peter Hessler's post here: > https://bsd.network/@phessler/99389809617980837 > > And the install instructions for arm64: > https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64 > > I have the pine64-lts: > https://www.pine64.org/?page_id=46823 Forgot the dmesg: OpenBSD 6.3-current (RAMDISK) #235: Thu Apr 12 14:38:28 MDT 2018 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK real mem = 2015993856 (1922MB) avail mem = 1915539456 (1826MB) mainbus0 at root: Pine64+ cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4 efi0 at mainbus0: UEFI 2.7 efi0: Das U-Boot rev 0x0 psci0 at mainbus0: PSCI 0.2 agtimer0 at mainbus0: tick rate 24000 KHz simplebus0 at mainbus0: "soc" sxiccmu0 at simplebus0 sxipio0 at simplebus0: 103 pins ampintc0 at simplebus0 nirq 224, ncpu 4: "interrupt-controller" sxiccmu1 at simplebus0 sxipio1 at simplebus0: 13 pins sximmc0 at simplebus0 sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma ehci0 at simplebus0 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 addr 1 com0 at simplebus0: ns16550, no working fifo com0: console sxitwi0 at simplebus0 iic0 at sxitwi0 sxirtc0 at simplebus0 dwxe0 at simplebus0: address 02:ba:43:50:f0:a3 rgephy0 at dwxe0 phy 0: RTL8169S/8110S/8211 PHY, rev. 5 rgephy1 at dwxe0 phy 1: RTL8169S/8110S/8211 PHY, rev. 5 gpio0 at sxipio0: 32 pins gpio1 at sxipio0: 32 pins gpio2 at sxipio0: 32 pins gpio3 at sxipio0: 32 pins gpio4 at sxipio0: 32 pins gpio5 at sxipio0: 32 pins gpio6 at sxipio0: 32 pins gpio7 at sxipio0: 32 pins gpio8 at sxipio1: 32 pins bootfile: sd0a:/bsd boot device: lookup sd0a:/bsd failed root on rd0a swap on rd0b dump on rd0b
pine64-lts - can't detect disk
Hi All, So between Peter Hessler's post here: https://bsd.network/@phessler/99389809617980837 And the install instructions for arm64: https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64 I have the pine64-lts: https://www.pine64.org/?page_id=46823 Booting to the installer, but the sd card disk cannot be located: Available disks are: none. Which disk is the root disk? ('?' for details) /dev/rd0a no such disk Available disks are: none. Which disk is the root disk? ('?' for details) /dev/rd0 no such disk Available disks are: none. Which disk is the root disk? ('?' for details) ? Available disks are: none. Which disk is the root disk? ('?' for details) Can anyone give some hints on how to have the installer detect the SD card and for the installation to be completed? disklabel rd0 # /dev/rrd0c: type: rdroot disk: rdroot label: duid: 6665228f9017b391 flags: bytes/sector: 512 sectors/track: 480 tracks/cylinder: 2 sectors/cylinder: 960 cylinders: 16 total sectors: 15360 boundstart: 0 boundend: 0 drivedata: 0 3 partitions: #size offset fstype [fsize bsize cpg] a:153600 4.2BSD512 4096 1920 c:153600 unused Thanks! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: 4-ports router under $150
On 10 April 2018 at 16:09, Stuart Henderson wrote: > On 2018-04-08, Patrick Dohman wrote: >> As much as I’d rather not point the blame I found the APU platform buggy >> when running OpenBSD. >> Yes there are reports of stability with other O.S however subtle >> hardware/firmware bugs appeared on several OpenBSD releases. > > APU and APU2 are both rock solid for many people on OpenBSD. If seeing > problems there I would first look for hardware issues e.g. is the power > supply faulty, or are there any mPCIe cards that might be causing > problems? > > It's awesome to know how with the apu2's are running. The other boards from aliexpress are probably okay, but in the end, seem more expensive. What's been linked here from aliexpress doesn't include RAM or HDD. Here's a link to a github repo on setting up openBSD: https://github.com/elad/openbsd-apu2/blob/master/README.md -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: 4-ports router under $150
Thus said Jordan Geoghegan on Sat, 7 Apr 2018 17:57:16 -0700 The Edgerouter 6 is going to be coming out shortly, that is what I am holding out for to run my home network on. Just curious, why this and not amd64 bit with something like the pcengine apu2 board? I know it only has three NICs, so it's likely a non-started for the OP, but it's 64bit amd. I don't know the MSRP of the ER6. Do you?
Re: doas.conf example - add persist?
Thus said Theo De Raadt on Tue, 27 Mar 2018 22:19:42 -0600 That may hint to people it should be the default. And it should not be. That's a very valid point that I can't fault. The documentation is simple and concise, and after further review, I see it already lists many config options. Pardon the noise.
pine64 - works well!
I've had some debian running on the pine64 for too long. It's now EASILY been replaced with openBSD. Keep up the great work. OpenBSD 6.3 (GENERIC.MP) #41: Sat Mar 24 20:06:13 MDT 2018 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 2021548032 (1927MB) avail mem = 1928085504 (1838MB) mainbus0 at root: Pine64+ cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4 efi0 at mainbus0: UEFI 2.7 efi0: Das U-Boot rev 0x0 psci0 at mainbus0: PSCI 0.2 agtimer0 at mainbus0: tick rate 24000 KHz simplebus0 at mainbus0: "soc" sxiccmu0 at simplebus0 sxipio0 at simplebus0: 103 pins ampintc0 at simplebus0 nirq 224, ncpu 4 ipi: 0, 1: "interrupt-controller" sxiccmu1 at simplebus0 sxipio1 at simplebus0: 13 pins sximmc0 at simplebus0 sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma ehci0 at simplebus0 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev 2.00/1.00 addr 1 com0 at simplebus0: ns16550, no working fifo com0: console sxitwi0 at simplebus0 iic0 at sxitwi0 sxirtc0 at simplebus0 dwxe0 at simplebus0: address 02:ba:10:9b:c2:3a rgephy0 at dwxe0 phy 0: RTL8169S/8110S/8211 PHY, rev. 5 rgephy1 at dwxe0 phy 1: RTL8169S/8110S/8211 PHY, rev. 5 gpio0 at sxipio0: 32 pins gpio1 at sxipio0: 32 pins gpio2 at sxipio0: 32 pins gpio3 at sxipio0: 32 pins gpio4 at sxipio0: 32 pins gpio5 at sxipio0: 32 pins gpio6 at sxipio0: 32 pins gpio7 at sxipio0: 32 pins gpio8 at sxipio1: 32 pins cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4 cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4 cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4 scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct removable sd0: 30436MB, 512 bytes/sector, 62333952 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets bootfile: sd0a:/bsd boot device: sd0 root on sd0a (9c66e619342ef8ab.a) swap on sd0b dump on sd0b nd6_dad_timer: called with non-tentative address 2600:8801:980:8270:5880:ec36:8513:bb8d(dwxe0)
doas.conf example - add persist?
Hi All, Now that doas.conf supports the persist keyword, I suggest adding it to the /etc/examples/doas.conf file. The persist keyword was added in openBSD 6.1: https://www.openbsd.org/61.html https://man.openbsd.org/doas.conf.5#persist http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/etc/examples/doas.conf?rev=1.1&content-type=text/plain&only_with_tag=MAIN Thanks for the time.
Re:
Thus said Elo Morio on Sat, 24 Mar 2018 09:28:12 +0100 Are there any existing Documentation, manuals or supplementary expository books that details out the internals of OpenBSD. Otherwise what books or materials would be close enough to better aid the newbie wishing to hack on the systems internals. See this reddit post: https://www.reddit.com/r/openbsd/comments/7vfm54/is_there_any_book_or_something_that_helps_me_for/
Re: Relinking unique kernel failed after syspatch
Thus said Leo Unglaub on Tue, 20 Mar 2018 04:57:55 +0100 Hello, today I wanted to apply the latest patches on our servers. They all worked fine, only on one server where i was missing some previous patches as well it got an error from syspatch. Does this explain it? https://marc.info/?l=openbsd-cvs&m=152148043420143&w=2 http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib/syspatch/bsd.syspatch.mk
Re: 6.2 song?
On Mar 14, 2018 6:41 PM, "Stuart Henderson" wrote: > > On 2018-03-15, jungle boogie wrote: > > Thus said Jungle Boogie on Sun, 31 Dec 2017 14:07:31 -0800 > >> Hi All, > >> > >> There's only a few more hours remaining in 2017, at least in my time > >> zone, are we going to get the 6.2 song before then? > >> > >> https://www.openbsd.org/62.html > >> > >> Thanks and happy new year! > >> > > > > Hi again. > > > > Here we are on pi day and unfortunately, I can't celebrate it - there's > > still no 6.2 song. > > > > As openBSD is very good with documentation, can the reference to the > > song be removed? > > https://www.openbsd.org/62.html > > > > > > > > > > > > it doesn't say which December. Yes, good point! > > (and I don't really see why 14/3/2018 would be "pi day"...) > > Also true. But if we both use iso8601, it's a little more obvious. ;) Except we would need to drop the first five digits.
Re: 6.2 song?
Thus said Jungle Boogie on Sun, 31 Dec 2017 14:07:31 -0800 Hi All, There's only a few more hours remaining in 2017, at least in my time zone, are we going to get the 6.2 song before then? https://www.openbsd.org/62.html Thanks and happy new year! Hi again. Here we are on pi day and unfortunately, I can't celebrate it - there's still no 6.2 song. As openBSD is very good with documentation, can the reference to the song be removed? https://www.openbsd.org/62.html
Re: The vim display issue on OpenBSD
On 11 March 2018 at 18:18, Nan Xiao wrote: > Hi all, > > Update: > > I try to install vim-8.0.0987p0-no_x11, still the same problem, thanks! I am using vim-8.0.1589-no_x11-python3 without any issues on openBSD snapshot from this morning. > Best Regards > Nan Xiao >
Re: go get abort trap?
Thus said Stuart Henderson on Thu, 8 Mar 2018 00:40:03 + (UTC) There's a stack safety diff which is in snapshots (for detailed information see https://marc.info/?l=openbsd-tech&m=152035796722258&w=2: in a nutshell "You may no longer point your stack register at non-stack memory. You'll be killed.") SBCL needs a change to work with this; see joshe's update on ports@. Go also needs a change. Apart from those two: ports bulk builds haven't quite finished yet, but it's looking likely that there won't be other significant impact. A few bootstraps need rebuilding, that's all we've run into so far. Thanks Stuart and Hiltjo for the pointers to the mailing list. I'll continue to use snapshots and update my packages when new ones are made.
go get abort trap?
Hi All, With the latest openbsd snapshot: OpenBSD 6.3-beta (GENERIC.MP) #40: Wed Mar 7 12:51:00 MST 201 It seems I cannot build or update go projects: $ go get -u github.com/justwatchcom/gopass Abort trap (core dumped) dmesg shows: trap pid 74737 tid 99500 type 6: sp c420024750 not inside 7f7fffbef000-7f7ee000 A week or two ago, I was able to update this project without any issues. I can't run 'go' without the abort trap. Anyone else running openbsd snapshots experiencing this? Thanks! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: sudoedit for doas?
Thus said Michael on Thu, 01 Mar 2018 08:39:51 +0100 ‎What is a sudoedit alternative? I mean: what should it do? You can edit the file with a text editor, like vim. Worth reading: https://undeadly.org/cgi?action=article&sid=20160913101323
Re: signify-openbsd to crypt'ly verify install62.iso in linux
On Fri 09 Feb 2018 5:50 PM, Kenneth Gober wrote: > > This paper provides some good background about why signify rather than > https or gpg: > > http://www.openbsd.org/papers/bsdcan-signify.html And the video: https://www.youtube.com/watch?v=9R5s3l-0wh0 It's quite creative to include the next set of public keys. > > -ken >
Re: considering a move to OpenBSD
On Thu 08 Feb 2018 6:21 PM, Steve Litt wrote: > On Thu, 8 Feb 2018 13:41:20 -0800 > Charlie Eddy wrote: > > > hello misc, > > > > I am considering a move to OpenBSD, since I subscribed to this > > mailing list some time ago (~few months). I want to take advantage of > > security. > > > > However, a programmer who I know personally and respect considers > > OpenBSD to be old-school, in a negative sense. He recommends Arch > > Linux as superior, because more new. Does the difference boil down to > > one's definition of free software, and then compliance with that > > definition? > > > > I have read up on this a lot, and this is a serious question. I have > > heard that it is unimportant what *nix you're on after a few years of > > using one or the other, in terms of functionality. I am interested in > > embedded devices. I think that bends the needle towards Arch, but the > > security of OpenBSD is also attractive. What considerations should I > > take into account? > > If installability on embedded devices is a requirement, I think that > would rule out a whole bunch of BSDs and Linux distros. > > About your friend: There's a logical fallacy called "Appeal to Novelty" > (https://en.wikipedia.org/wiki/Appeal_to_novelty) If your experience is > anything like mine, household appliances installed in the 1980's tended > to last almost 20 years, whereas appliances in the 2010's tend to last > about six. Sometimes newer is better, sometimes it's not. Arch Linux > uses the relatively new systemd init system/OS controller/Desktop aid. > It's such a mess that nobody's ever been able to draw its block diagram, > complete with boxes and arrows. > > My main OS right now is Void Linux, but when I used OpenBSD I was > impressed with how everything worked exactly the same, every single > time. This is subjective, but I view OpenBSD as the most solid OS I've > ever run. > I agree, I continue to be impressed by openBSD. I run snapshots and update nearly daily. I try to find bugs and issues, but they're few and far between. To the OP, does your friend update to the latest linux code daily? That's possible, but doubtful. Of course you may not need to update snapshots daily, but that just shows how solid the OS is. The openBSD group has hackathons to improve it, fix things, and more importantly - take code out. Simply provide this page to your friend: https://www.openbsd.org/innovations.html > SteveT > > Steve Litt > January 2018 featured book: Troubleshooting: Why Bother? > http://www.troubleshooters.com/twb >
Re: bsd.mp not installed on EdgeRouter Lite
On 18 January 2018 at 07:00, Scott Bennett wrote: > On 1/18/2018 9:23 AM, Stefan Sperling wrote: >> On Thu, Jan 18, 2018 at 09:06:44AM -0500, Sean Murphy wrote: >>> I performed the steps as indicated n the links above and now have GENERIC.MP >>> running on my ERL. I did see that KARL failed on the initial install and >>> reboot, >> >> It looks like this issue was just fixed in -current by visa@ > > I saw the commit messages. Very exciting! I'll give it a try once a new > snapshot > gets rolled. Luckily I haven't deployed the ERL yet, so re-installing won't be > a problem. > >From the build on the 18th: Location of sets? (disk http nfs or 'done') [done] done Making all device nodes...done. Multiprocessor machine; using bsd.mp instead of bsd. Very nice! Thanks Visa! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: bsd.mp not installed on EdgeRouter Lite
On 12 January 2018 at 08:24, Scott Bennett wrote: > After reading INSTALL.octeon, I was able to write miniroot62.fs to a usb, > plug that into the ERL, and perform a normal installation. The problem is > that the installer was not able to detect both cores, so it only installed > bsd.sp (bsd.mp was not an option in the set selection). See this post: https://an.undulating.space/post/171020-erl-openbsd-smp/ See this reddit thread: https://www.reddit.com/r/openbsd/comments/7agdgh/openbsd_62_on_edgerouter_lite_with_bsdmp/ Hope that helps
Re: no X login
Thus said Ed Ashlen-girard on Fri, 5 Jan 2018 07:17:23 -0600 After upgrading to the Jan 4 amd64 snapshot, I do not see a login box. I can ssh to the machine, and run X applications in an X server, but no graphical login at the console. dmesg below. I had no problems, and I think I was on that exact snapshot. There's newer ones from today: https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ Try that.
6.2 song?
Hi All, There's only a few more hours remaining in 2017, at least in my time zone, are we going to get the 6.2 song before then? https://www.openbsd.org/62.html Thanks and happy new year!
Re: Bug in rc.d/ifstated ?
Thus said Christer Solskogen on Sat, 11 Nov 2017 20:09:13 +0100 If ifstated.conf have a error this will happen: # ifstated -d /etc/ifstated.conf:35: syntax error /etc/ifstated.conf:38: syntax error error: state 'fw_slave' not declared error: state 'fw_slave' not declared unable to load config But with the same config: # /etc/rc.d/ifstated start ifstated(ok) # echo $? 0 I would expect that it would say something like this, like other daemons do. ifstated(failed) Here's a false start with ifstated: $ ls -l /etc/if* ls: /etc/if*: No such file or directory $ doas /etc/rc.d/ifstated -f start ifstated(ok) $ pgrep ifstated - Here's a legitimate failure with ntp: $ ls -l /etc/nt* ls: /etc/nt*: No such file or directory $ doas /etc/rc.d/ntpd -f start ntpd(failed)
Re: X turn off monitors automatically, not with mplayer running
On Oct 7, 2017 4:48 AM, "Marc Espie" wrote: > > On Sat, Oct 07, 2017 at 06:52:53AM -0300, x9p wrote: > > Hi > > > > If am running a video with mplayer, pause it, and lock X with xlock - my > > monitors are not turned off for inactivity. > > > > If mplayer is not running, after a couple of minutes my monitors are > > automatically turned off. > > > > I am trying to disable the energy saving without mplayer, so I run the > > command: > > > > $ xset -dpms > > > > But it did not worked for me. Any hints on the proper way? > > > > cheers. > > > > Have you tried switching to mpv ? > While it seems MPlayer wasn't at fault, I'm with Mark - upgrade to mpv.
Re: resolve.conf overwritten woes
Thus said Theo Buehler on Sat, 12 Aug 2017 22:56:05 -0400 On Sat, Aug 12, 2017 at 07:49:22PM -0700, jungle Boogie wrote: I think I saw it and there was a typo with resolveor section. thanks, but unfortunately i have no idea what you mean. could you please be more specific? Well maybe this is legitimate: provides the domain-name, domain-searchor or domain-name-servers options.
Re: resolve.conf overwritten woes
I think I saw it and there was a typo with resolveor section. Sent from my iPhone 7.1
Re: resolve.conf overwritten woes
Thus said Raf Czlonka on Sat, 12 Aug 2017 09:53:35 +0100 What am I doing wrong? I just want a search domain and a couple NS is resolv.conf Thanks! Hi, I don't think there's anything you're doing wrong - I've tested it myself just now and the option doesn't seem to be doing what it is supposed to, at least as described in the FAQ. I forgot to add that I'm running openbsd -current snapshot from OpenBSD 6.1-current (GENERIC.MP) #1: Fri Aug 11 21:26:07 MDT 2017 In order to achieve the same, I simply use 'supersede', i.e.: send host-name "host"; supersede domain-name-servers 127.0.0.1; That didn't work for me. I have this working by removing the ignore option from /etc/dhclient.conf and now my /etc/resolv.conf looks like this: $ cat /etc/resolv.conf # Generated by wpi0 dhclient nameserver 68.105.28.11 nameserver 68.105.29.11 nameserver 68.105.28.12 lookup file bind search in.example.net nameserver 192.168.0.17 This will work kind of work for the time being. Regards, Raf
resolve.conf overwritten woes
Hi All, From this page: https://www.openbsd.org/faq/faq6.html#Setup Once the interface is configured, the /etc/resolv.conf file will be overwritten. You can customize the resolver configuration by using settings in dhclient.conf(5) and using resolv.conf.tail(5). To prevent the DHCP server from overriding the DNS server you configured in /etc/resolv.conf.tail, add ignore domain-name-servers; to your /etc/dhclient.conf. $ cat /etc/dhclient.conf send host-name "puffer.in.example.net"; ignore domain-name-servers; $ cat /etc/resolv.conf.tail search in.example.net nameserver 192.168.0.17 lookup file bind $ cat /etc/resolv.conf $ $ cat /etc/hosts 127.0.0.1 localhost puffer.in.example.net ::1 localhost What am I doing wrong? I just want a search domain and a couple NS is resolv.conf Thanks!
Re: starting cwm and terminal font
Thus said Jungle Boogie on Sun, 30 Jul 2017 16:06:06 -0700 Hello, I have some cwm questions for you folks. cwm is launching, but it's not setting my background to gray. I thought I made the change correctly. $ cat .xsession /usr/X11R6/bin/cwm xsetroot -solid grey & oclock -geometry 75x75-0-0 & I've learned much from all these posts - thank you all! Now using .Xdefaults: XTerm*faceName: Momo:style=Regular:size=9 XTerm.vt100.saveLines: 1000 XTerm.vt100.scrollBar: true XTerm.vt100.scrollbar.width: 8 XTerm*selectToClipboard:true Also some color stuff below. Is everything above accurate to use with openbsd? My xinitrc: $ cat .xinitrc xsetroot -solid gray40 (does the 40 actually do anything? I've seen a few examples with numbers after it) #xclock -d -geometry 180x30-0-0 exec cwm I have the digit xclock commented out, because when it was enabled, it seem to have locked the system. Any hints? My cwmrc: $ cat .cwmrc command firefox /usr/local/bin/firefox fontname "Courier:pixelsize=12:style=Regular" So it's coming along and I'm liking it! I have links installed as the browser (and firefox as you see above). Is links a favorite low resources browser with you folks? Thanks for all the responses so far!
starting cwm and terminal font
Hello, I have some cwm questions for you folks. cwm is launching, but it's not setting my background to gray. I thought I made the change correctly. $ cat .xsession /usr/X11R6/bin/cwm xsetroot -solid grey & oclock -geometry 75x75-0-0 & The clock is also not showing up. I've also put it in here: $ cat .xinitrc oclock -geometry 75x75-0-0 & xsetroot -solid grey & /usr/X11R6/bin/cwm Does it need to go in the .cwmrc? $ cat .cwmrc command firefox /usr/local/bin/firefox #fontname "sans-serif:pixelsize=14:bold" fontname "Courier:pixelsize=14:style=Regular" Is there a way to change the console font to something a little larger? fontname seems to change for menus only. Thanks!
Re: IPv6 autoconf
On 07/27/2017 05:41 PM, Thomas Smith wrote: Hi, Can anyone advise on this please? What do you see when you do: doas sh /etc/netstart Thank you, ~ Tom
Re: octeon port, ubiquity edgerouter
On Jul 25, 2017 6:59 PM, "Sean Murphy" wrote: > > >> People are willing to take an unknown (right now) performance penalty > >> to run openBSD on it and with pf. > > When I was using my ERL as primary gateway, I found that my network > performed better than it did with the dd-wrt based router I was using > previously. Everything was more stable, easier to keep track of what > was going on, and my work VPN was faster to connect and performed > tremendously. Anyone talking about a "performance penalty" is missing > the point. I absolutely DO NOT want blobs in or around openbsd whatsoever, ever. Im saying I'm presently surprised to see so many folks running openbsd on this arch and enjoying it. I certainly enjoy running it and the frequent updates from the team, I can't say either one of those would happen if we were still using ubiquity's option. To make this clear, I love openbsd and will forever be grateful for the project, the individuals and the 20+ years for the labor of love put into the project. Keep openbsd blob free!
Re: octeon port, ubiquity edgerouter
On 25 July 2017 at 15:20, Doggie wrote: > W dniu 2017-07-25 o 19:39, Peter J. Philipp pisze: >> >> Actually I bought the silent fans. So I don't have to write any code, >> too bad the foxconn fans are a misdesign. I'll maintenance this router >> next week for the new fans. I'm putting it into production at home >> tomorrow though. > > > Thanks for all the details, Peter, and good luck during next steps of your > project. > > I wonder how fast the NIC's will be - using this CPU and still no hardware > acceleration. > Yeah, I'm wondering that too. It's pretty cool this platform is becoming more popular to run openBSD on. People are willing to take an unknown (right now) performance penalty to run openBSD on it and with pf. Sounds like ubiquity should just sell it with openBSD loaded on it support the project. ;)
Re: octeon packages
On 19 July 2017 at 07:47, Christian Weisgerber wrote: > On 2017-07-19, Predrag Punosevac wrote: > >> I got myself a new toy, Ubiquiti Networks - EdgeRouter Lite. I am a bit >> confused about packages for Octeon. I don't see any neither for 6.1 >> release nor for 6.1 snapshots. > > Use the mips64 packages. It's actually explained in INSTALL.octeon. > Wow! That's awesome, thanks for the pointer! > -- > Christian "naddy" Weisgerber na...@mips.inka.de > -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: octeon packages
On 07/19/2017 07:07 AM, Predrag Punosevac wrote: Hi Misc, I got myself a new toy, Ubiquiti Networks - EdgeRouter Lite. I am a bit confused about packages for Octeon. I don't see any neither for 6.1 release nor for 6.1 snapshots. Am I suppose to use only base system on this anemic hardware? I typically add sshguard for example to built in ssh brute force mechanism built in PF and I like to use ldapvi to edit ldap data base. Has anybody tried building any port on this thing? I haven't seen packages available for oceton before. The oceton snapshots are made available at nearly the rate of one a day, so I'm very thankful for that: https://ftp.openbsd.org/pub/OpenBSD/snapshots/octeon/ You can build certain applications on the ERL yourself. sshguard is pretty easy. Best, Predrag P.S. I do see mips64 and mips64el packages but my assumption is that mips64 are SGI packages while mips64el are loongson packages.
Re: OT: protonmail mail body
On 18 July 2017 at 09:29, Eric Johnson wrote: > > On Wed, 12 Jul 2017, Mihai Popescu wrote: > >> Hello, >> >> I preffer to keep it calm, but some people on the list are using >> protonmail and their mails are impossible to read directly on the >> list. I think they are destroying the list, maybe they should turn >> that feature off. Here is what I see reading on marc.info: >> >> TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp >> bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv >> YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+ >> IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg >> bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv >> d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh >> bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t >> YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg >> YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl >> IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg >> Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD >> bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl >> ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN >> VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh >> dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw== > > My primary e-mail address is on protonmail. For testing purposes, I have > sent e-mail from my protonmail account to a number of other accounts and > have never had any problem reading the messages. For example, on this > account I use pine (alpine) to handle my e-mail and have never had a > problem. > Oh, I get it! You can decode base64 in your head and read messages that way. Dang, that's impressive. I know a couple people who know ASCII by memory, but never anyone who can read base64. > Eric > -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: WireGuard will make OpenIKED obsolete?
On 07/13/2017 04:50 PM, if...@airmail.cc wrote: Hi, I have recently read about WireGuard Protocol and it seems really interesting. Here's a description (from wireguard.io): So, my question is: - Will it supersede IPsec, in your opinion? - Why should someone use OpenIKED instead of WireGuard (if it will be ported to OpenBSD)? - There's any plan for a future implementation of the protocol, using the best security practices of OpenBSD team? I'm mainly concerned about privsep here (pledge) and correctness. It doesn't matter if the protocol has a formal verification if it's implementation is bad. I would be interested to know Reyk's thoughts. Here's what he wrote about Tinc in April: http://marc.info/?l=openbsd-misc&m=149328601710376&w=2 Same questions and thoughts apply to wireguard. Regards.
Re: OT: protonmail mail body
On 12 July 2017 at 00:37, Mihai Popescu wrote: > Hello, > > I preffer to keep it calm, but some people on the list are using > protonmail and their mails are impossible to read directly on the > list. I think they are destroying the list, maybe they should turn > that feature off. Here is what I see reading on marc.info: > I agree. I was trying to read this list on the links browser last weekend and I had to skip over many messages because of the base64 encoding issues. Good to know about mail-archive. I'll have to see how that looks on links, though. Thanks!
Re: KARL not sending email?
Hi Theo, On 07/10/2017 09:24 PM, Theo Buehler wrote: On Mon, Jul 10, 2017 at 07:44:19PM -0700, jungle boogie wrote: Hi All, I just updated from the 6th of July snapshot to the 10th of July. When I logged in and check the mail, I didn't see a message advising a new kernel link. Between the 6th and 10th I rebooted my machine many times and didn't see the mail. Are the mails no longer expected? How do I verify the kernel re-linking is actually in place? The mails were replaced with syslog in etc/rc -r1.507 once we were confident enough that it works as expected. You'll find 'Kernel relinking done' notices in your /var/log/messages. In case an error occurs, it will additionally be logged to the console. https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc/rc#rev1.507 Awesome! Sorry to have missed this commit. As expected, the linking is happening without issue: /etc/rc: kernel relinking done
KARL not sending email?
Hi All, I just updated from the 6th of July snapshot to the 10th of July. When I logged in and check the mail, I didn't see a message advising a new kernel link. Between the 6th and 10th I rebooted my machine many times and didn't see the mail. Are the mails no longer expected? How do I verify the kernel re-linking is actually in place? Other than than, I don't have any issues with my system. dmesg: OpenBSD 6.1-current (GENERIC.MP) #94: Mon Jul 10 18:20:35 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3194490880 (3046MB) avail mem = 3091947520 (2948MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf6e60 (62 entries) bios0: vendor Dell Inc. version "A07" date 12/18/2006 bios0: Dell Inc. Latitude D620 acpi0 at bios0: rev 0 acpi0: TCPA checksum error acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC ASF! MCFG SLIC TCPA SSDT acpi0: wakeup devices LID_(S3) PBTN(S4) PCI0(S5) USB0(S0) USB1(S0) USB2(S0) USB3(S0) EHCI(S0) AZAL(S3) PCIE(S4) RP01(S3) RP02(S4) NIC_(S5) RP04(S3) RP05(S3) RP06(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1997.64 MHz 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,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1997.33 MHz 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,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 3 (PCIE) acpiprt3 at acpi0: bus 11 (RP01) acpiprt4 at acpi0: bus 12 (RP02) acpiprt5 at acpi0: bus 9 (PXP0) acpiprt6 at acpi0: bus -1 (RP04) acpiprt7 at acpi0: bus -1 (RP05) acpiprt8 at acpi0: bus -1 (RP06) acpicpu0 at acpi0: !C3(100@57 io@0x1016), !C2(500@1 io@0x1014), C1(1000@1 halt), PSS acpicpu1 at acpi0: !C3(100@57 io@0x1016), !C2(500@1 io@0x1014), C1(1000@1 halt), PSS acpitz0 at acpi0: critical temperature is 126 degC "*pnp0c14" at acpi0 not configured acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "DELL J825J8" serial 1093 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 not present acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN "PNP0F13" at acpi0 not configured "PNP0303" at acpi0 not configured "PNP0501" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivideo1 at acpi0: VID_ acpivideo2 at acpi0: VID2 cpu0: Enhanced SpeedStep 1997 MHz: speeds: 2000, 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03 inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03 drm0 at inteldrm0 intagp0 at inteldrm0 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 3 (PCIE) acpiprt3 at acpi0: bus 11 (RP01) acpiprt4 at acpi0: bus 12 (RP02) acpiprt5 at acpi0: bus 9 (PXP0) acpiprt6 at acpi0: bus -1 (RP04) acpiprt7 at acpi0: bus -1 (RP05) acpiprt8 at acpi0: bus -1 (RP06) acpicpu0 at acpi0: !C3(100@57 io@0x1016), !C2(500@1 io@0x1014), C1(1000@1 halt), PSS acpicpu1 at acpi0: !C3(100@57 io@0x1016), !C2(500@1 io@0x1014), C1(1000@1 halt), PSS acpitz0 at acpi0: critical temperature is 126 degC "*pnp0c14" at acpi0 not configured acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "DELL J825J8" serial 1093 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 not present acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN "PNP0F13" at acpi0 not configured "PNP0303" at acpi0 not configured "PNP0501" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivideo1 at acpi0: VID_ acpivideo2 at acpi0: VID2 cpu0: Enhanced SpeedStep 1997 MHz: speeds: 2000, 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03 inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03 drm0 at inteldrm0 intagp0 at inteldrm0 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0: apic 2 int 16 in
Re: ocsp response not current
On 12 June 2017 at 03:28, Stuart Henderson wrote: > On 2017-06-12, jungle boogie wrote: >> Hi All, >> >> I'm attempting to fetch the latest bsd.rd snapshot, but it's failing >> because of the ocsp response. >> >> $ ftp https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd.rd >> Trying 129.128.5.191... >> Requesting https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd.rd >> ftp: SSL write error: ocsp verify failed: ocsp response not current >> >> Currently on >> OpenBSD 6.1-current (GENERIC.MP) #116: Sat Jun 10 22:34:37 MDT 2017 >> >> Any clues as to what's happening with the ocsp response? >> >> Thanks, >> j.b. >> >> > > It's a server-side problem, same on www.openbsd.org. Not visible in > normal graphical browsers because they fallback to the CA's OCSP server > whereas ftp(1) just relies on the stapled cert. > Ah, that explains why I didn't see it within firefox. > Simplest workaround is to use a mirror, but it does mean that the > installer won't be showing the list of mirrors at the moment (or > feeding into initial RNG entropy) even if your clock is correct, > so you'll also need to type the mirror's hostname by hand in the > installer. > FreeBSD's fetch wasn't affected for some reason or another so I was able to fetch bsd.rd and scp it to my OpenBSD machine. The auto upgrade either downgraded to http or didn't care about the OCSP. > -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
ocsp response not current
Hi All, I'm attempting to fetch the latest bsd.rd snapshot, but it's failing because of the ocsp response. $ ftp https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd.rd Trying 129.128.5.191... Requesting https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd.rd ftp: SSL write error: ocsp verify failed: ocsp response not current Currently on OpenBSD 6.1-current (GENERIC.MP) #116: Sat Jun 10 22:34:37 MDT 2017 Any clues as to what's happening with the ocsp response? Thanks, j.b.
full screen in console
Hi All, I would like to have a full screen console on my rather old dell d620 laptop. The best I've been able to do is for it to occupy 1/4 of the top left of the monitor. I can disable inteldrm during boot and have it use the full screen, but as you know, that's far less quality. With this dmesg, is there any hope that I'll be able to use the full screen with inteldrm? OpenBSD 6.1-current (GENERIC.MP) #109: Wed Jun 7 19:41:42 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3194490880 (3046MB) avail mem = 3091947520 (2948MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf6e60 (62 entries) bios0: vendor Dell Inc. version "A07" date 12/18/2006 bios0: Dell Inc. Latitude D620 acpi0 at bios0: rev 0 acpi0: TCPA checksum error acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC ASF! MCFG SLIC TCPA SSDT acpi0: wakeup devices LID_(S3) PBTN(S4) PCI0(S5) USB0(S0) USB1(S0) USB2(S0) USB3(S0) EHCI(S0) AZAL(S3) PCIE(S4) RP01(S3) RP02(S4) NIC_(S5) RP04(S3) RP05(S3) RP06(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1997.60 MHz 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,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1997.33 MHz 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,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 3 (PCIE) acpiprt3 at acpi0: bus 11 (RP01) acpiprt4 at acpi0: bus 12 (RP02) acpiprt5 at acpi0: bus 9 (PXP0) acpiprt6 at acpi0: bus -1 (RP04) acpiprt7 at acpi0: bus -1 (RP05) acpiprt8 at acpi0: bus -1 (RP06) acpicpu0 at acpi0: !C3(100@57 io@0x1016), !C2(500@1 io@0x1014), C1(1000@1 halt), PSS acpicpu1 at acpi0: !C3(100@57 io@0x1016), !C2(500@1 io@0x1014), C1(1000@1 halt), PSS acpitz0 at acpi0: critical temperature is 126 degC "*pnp0c14" at acpi0 not configured acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "DELL J825J8" serial 1093 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 not present acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN "PNP0F13" at acpi0 not configured "PNP0303" at acpi0 not configured "PNP0501" at acpi0 not configured acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivideo1 at acpi0: VID_ acpivideo2 at acpi0: VID2 cpu0: Enhanced SpeedStep 1997 MHz: speeds: 2000, 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03 inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03 drm0 at inteldrm0 intagp0 at inteldrm0 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0: apic 2 int 16 inteldrm0: 848x480, 32bpp wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: msi azalia0: codecs: Sigmatel STAC9200, Conexant/0x2bfa, using Sigmatel STAC9200 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: msi pci1 at ppb0 bus 11 ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x01: msi pci2 at ppb1 bus 12 wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: msi, MoW1, address 00:19:d2:c8:ce:01 ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x01: msi pci3 at ppb2 bus 9 bge0 at pci3 dev 0 function 0 "Broadcom BCM5752" rev 0x02, BCM5752 A2 (0x6002): msi, address 00:18:8b:be:b2:3d brgphy0 at bge0 phy 1: BCM5752 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2 int 20 uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 2 int 21 uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2 int 22 uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2 int 23 ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 2 int 20 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 add
Re: Sad story
On 5 June 2017 at 16:27, Raul Miller wrote: > On Mon, Jun 5, 2017 at 7:22 PM, jungle Boogie wrote: >> On 5 June 2017 at 16:16, Mihai Popescu wrote: >>> >>> Bytheway, I am using marc.info to read list, has anyone an idea about >>> why some emails are presented like a long ASCII stream without sense? >>> Much like: >>> >>> http://marc.info/?l=openbsd-misc&m=149656895018721&w=2 >> >> It's base64 encoded.: >> >> Maybe the mail client of the poster did something weird. > > I didn't see anything unusual in the mail headers on that message. Did you? > What about this? Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=UTF-8 X-Content-Discarded: text/html If you look at "show original" in gmail, it'll also show the body as base64. > Thanks, > > -- > Raul -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: Sad story
On 5 June 2017 at 16:16, Mihai Popescu wrote: > > Bytheway, I am using marc.info to read list, has anyone an idea about > why some emails are presented like a long ASCII stream without sense? > Much like: > > http://marc.info/?l=openbsd-misc&m=149656895018721&w=2 It's base64 encoded.: Maybe the mail client of the poster did something weird. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: Version skew?
On 05/05/2017 08:01 PM, Donald Allen wrote: The /etc/installurl file is not present on either of my 'current' systems. Reading the man pages, it looks to me like installurl is related to the new syspatch facility, which I believe is for tracking the STABLE branch. As I said, I'm running CURRENT, so if I've got all this right, the fact that /etc/installurl isn't present on my systems is not surprising. Also, if you look at the pkg_add man page, PKG_PATH is documented without any mention that it is deprecated. See this commit: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib/sets/lists/base/mi?rev=1.823&content-type=text/x-cvsweb-markup
Re: Are mips64 or sparc64 packages for 6.1 released yet?
On 12 April 2017 at 12:01, Jan Vlach wrote: > Is this intentional? (Long build times, lack of time ...) Is there a > rough guesstimate when things migt be available? Have octeon packages ever been built? I'm very thankful for the rather regular octeon images. Those must take a couple days to build, and we're fortunate to get them once or more a week! What a treat! Thank you for this! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: pkg_add: ftp: connect: Invalid argument
On 02/04/2017 10:46 PM, jungle boogie wrote: Ping was failing with something very similar: ping: sendmsg: Invalid argument ping: wrote yahoo.com 64 chars, ret=-1 Follow up to my own mystery... I have two network interfaces on this laptop: bge0 and wpi0, both of which are on the same physical network. What happened is the wpi0 interface died somehow and when I rebooted/deleted pf rules, I thought I fixed it, when it reality the network interface just came alive again. The same network interface died earlier today and when I attempted to ping, I got the same response as above. I restarted network with sh /etc/netstart and pinging was fine. Now the off-topic (from original post) question is why did the NIC die? I see lots and lots of this in dmesg: arpresolve: 192.168.0.1: route contains no arp information arpresolve: 192.168.0.1: route contains no arp information one of these: arp: attempt to add entry for 192.168.0.21 on bge0 by 00:0c:42:c2:5f:9e on wpi0 Here's the interface: wpi0: flags=8843 mtu 1500 lladdr 00:19:d2:c8:ce:01 index 1 priority 4 llprio 3 groups: wlan media: IEEE802.11 autoselect (DS1 mode 11g) status: active ieee80211: nwid the-rocks chan 6 bssid 64:70:02:32:c2:48 -42dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet 192.168.0.20 netmask 0xff00 broadcast 192.168.0.255 Thanks for the pointers.
Re: pkg_add: ftp: connect: Invalid argument
On 6 February 2017 at 04:41, Marc Espie wrote: > On Sat, Feb 04, 2017 at 08:31:45PM -0800, jungle boogie wrote: >> On 02/04/2017 05:45 PM, Philip Guenther wrote: >> >On Sat, 4 Feb 2017, jungle boogie wrote: >> >>What's happening here? >> >> >> >>$ doas pkg_add -u >> >>Error from http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ >> >>ftp: connect: Invalid argument >> > >> >Running that under ktrace -i might help see the problem, ala >> > doas ktrace -i pkg_add -u >> > >> >then kdump | less and look for a failed connect call. Should be able to >> >search for "connect -1 errno" and then go backwards to see the connect() >> >call and the sockaddr passed to it. >> > >> > >> >> Here's where it actually lits the URL: > > perl doesn't do network connects in that context. > just run > ftp -o - http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ > it should dump the html list of packages. > > if it doesn't, your network is broken. Ah, that's a good trick! I'll keep that in mind if there's a next time. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: pkg_add: ftp: connect: Invalid argument
On 02/04/2017 07:17 PM, Philip Guenther wrote: Is this it? "Trying 129.128.5.191... ... 80377 ftp CALL connect(3,0xaf766dd0bf0,16) 80377 ftp STRU struct sockaddr { AF_INET, 129.128.5.191:80 } 80377 ftp RET connect -1 errno 22 Invalid argument It dumped the sockaddr and didn't complain about it being invalid, so it made it into soconnect(). That puts the problem somewhere in the network stack or network config. To quote connect(2): [EINVAL] A TCP connection with a local broadcast, the all-ones or a multicast address as the peer was attempted. Double/triple check your network configuration, routing table, etc. Good luck! AH! I think it was a pf rule. I deleted some pf rules, rebooted and now it works! Ping was failing with something very similar: ping: sendmsg: Invalid argument ping: wrote yahoo.com 64 chars, ret=-1 Thanks for the pointers. Philip Guenther
Re: pkg_add: ftp: connect: Invalid argument
On 02/04/2017 05:45 PM, Philip Guenther wrote: On Sat, 4 Feb 2017, jungle boogie wrote: What's happening here? $ doas pkg_add -u Error from http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ ftp: connect: Invalid argument Running that under ktrace -i might help see the problem, ala doas ktrace -i pkg_add -u then kdump | less and look for a failed connect call. Should be able to search for "connect -1 errno" and then go backwards to see the connect() call and the sockaddr passed to it. Here's where it actually lits the URL: "Trying 129.128.5.191... ftp: connect: Invalid argument " 54107 perl RET read 55/0x37 54107 perl CALL kbind(0x7f7ed638,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL kbind(0x7f7ed5f8,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL mmap(0,0x2000,0x3,0x1002,-1,0) 54107 perl RET mmap 34517689896960/0x1f64c6a51000 54107 perl CALL kbind(0x7f7ed4d8,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL write(2,0x1f64c6a51000,0x47) 54107 perl GIO fd 2 wrote 71 bytes "Error from http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/"; 54107 perl RET write 71/0x47 54107 perl CALL write(2,0x1f64c6a51000,0x1) 54107 perl GIO fd 2 wrote 1 bytes " " 54107 perl RET write 1 54107 perl CALL write(2,0x1f64c6a51000,0x1f) 54107 perl GIO fd 2 wrote 31 bytes "ftp: connect: Invalid argument " 54107 perl RET write 31/0x1f 54107 perl CALL read(5,0x1f64397c4000,0x2000) 54107 perl RET read 0 54107 perl CALL close(5) 54107 perl RET close 0 54107 perl CALL kbind(0x7f7ed658,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL kbind(0x7f7ed5b8,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL lstat(0x1f64e36dd4c0,0x1f64b5d2afc0) 54107 perl NAMI "/var/tmp/pkgout.XiGoAUMZwI" 54107 perl STRU struct stat { dev=3, ino=4, mode=-rw--- , nlink=1, uid=0<"root">, gid=0<"wheel">, rdev=1650, atime=1486267550<"Feb 4 20:05:50 2017">.781401466, mtime=1486267550<"Feb 4 20:05:50 2017">.781401466, ctime=1486267550<"Feb 4 20:05:50 2017">.781401466, size=55, blocks=4, blksize=16384, flags=0x0, gen=0x30f9f04e } 54107 perl RET lstat 0 54107 perl CALL kbind(0x7f7ed5b8,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL unlink(0x1f64e36dd4c0) 54107 perl NAMI "/var/tmp/pkgout.XiGoAUMZwI" 54107 perl RET unlink 0 54107 perl CALL write(2,0x1f64c6a51000,0x45) 54107 perl GIO fd 2 wrote 69 bytes "http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ is empty" 54107 perl RET write 69/0x45 54107 perl CALL write(2,0x1f64c6a51000,0x1) 54107 perl GIO fd 2 wrote 1 bytes " " 54107 perl RET write 1 54107 perl CALL write(2,0x1f64c6a51000,0x1f) 54107 perl GIO fd 2 wrote 31 bytes "ftp: connect: Invalid argument " 54107 perl RET write 31/0x1f 54107 perl CALL read(5,0x1f64397c4000,0x2000) 54107 perl RET read 0 54107 perl CALL close(5) 54107 perl RET close 0 54107 perl CALL kbind(0x7f7ed658,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL kbind(0x7f7ed5b8,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL lstat(0x1f64e36dd4c0,0x1f64b5d2afc0) 54107 perl NAMI "/var/tmp/pkgout.XiGoAUMZwI" 54107 perl STRU struct stat { dev=3, ino=4, mode=-rw--- , nlink=1, uid=0<"root">, gid=0<"wheel">, rdev=1650, atime=1486267550<"Feb 4 20:05:50 2017">.781401466, mtime=1486267550<"Feb 4 20:05:50 2017">.781401466, ctime=1486267550<"Feb 4 20:05:50 2017">.781401466, size=55, blocks=4, blksize=16384, flags=0x0, gen=0x30f9f04e } 54107 perl RET lstat 0 54107 perl CALL kbind(0x7f7ed5b8,24,0xb7ca63143ec3382a) 54107 perl RET kbind 0 54107 perl CALL unlink(0x1f64e36dd4c0) 54107 perl NAMI "/var/tmp/pkgout.XiGoAUMZwI" 54107 perl RET unlink 0 54107 perl CALL write(2,0x1f64c6a51000,0x45) 54107 perl GIO fd 2 wrote 69 bytes "http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ is empty" 54107 perl RET write 69/0x45 54107 perl CALL write(2,0x1f64c6a51000,0x1) 54107 perl GIO fd 2 wrote 1 bytes " " 54107 perl RET write 1 54107 perl CALL stat(0x1f64397c5680,0x7f7ed5c0) 54107 perl NAMI "/usr/local/libdata/perl5/site_perl/amd64-openbsd/OpenBSD/Tracker.pmc" 54107 perl RET stat -1 errno 2 No such file or directory 54107 perl CA
Re: pkg_add: ftp: connect: Invalid argument
On 02/04/2017 05:45 PM, Philip Guenther wrote: On Sat, 4 Feb 2017, jungle boogie wrote: What's happening here? $ doas pkg_add -u Error from http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ ftp: connect: Invalid argument Running that under ktrace -i might help see the problem, ala doas ktrace -i pkg_add -u then kdump | less and look for a failed connect call. Should be able to search for "connect -1 errno" and then go backwards to see the connect() call and the sockaddr passed to it. Is this it? "Trying 129.128.5.191... " 80377 ftp RET write 24/0x18 80377 ftp CALL kbind(0x7f7f1128,24,0x2cca07dce05ae2e3) 80377 ftp RET kbind 0 80377 ftp CALL socket(AF_INET,0x1,0x6) 80377 ftp RET socket 3 80377 ftp CALL kbind(0x7f7f1128,24,0x2cca07dce05ae2e3) 80377 ftp RET kbind 0 80377 ftp CALL connect(3,0xaf766dd0bf0,16) 80377 ftp STRU struct sockaddr { AF_INET, 129.128.5.191:80 } 80377 ftp RET connect -1 errno 22 Invalid argument 80377 ftp CALL kbind(0x7f7f1128,24,0x2cca07dce05ae2e3) 80377 ftp RET kbind 0 80377 ftp CALL close(3) 80377 ftp RET close 0 80377 ftp CALL kbind(0x7f7f1128,24,0x2cca07dce05ae2e3) 80377 ftp RET kbind 0 80377 ftp CALL kbind(0x7f7f1128,24,0x2cca07dce05ae2e3) 80377 ftp RET kbind 0 80377 ftp CALL write(2,0xaf79ce13000,0x1f) 80377 ftp GIO fd 2 wrote 31 bytes "ftp: connect: Invalid argument " Philip Guenther
pkg_add: ftp: connect: Invalid argument
Hi All, What's happening here? $ doas pkg_add -u Error from http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ ftp: connect: Invalid argument http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ is empty Couldn't find updates for GeoIP-1.6.5p4 ... zstd-1.1.2 $ doas pkg_add newsbeuter Error from http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ ftp: connect: Invalid argument http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ is empty Can't find newsbeuter $ echo $PKG_PATH http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ I can clearly see the directory is not empty: http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ Running: OpenBSD 6.0-current (GENERIC.MP) #161: Fri Feb 3 17:47:21 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Anyone else see this issue? Thanks!
Re: edge router lite with double NAT
On 01/23/2017 05:43 PM, trondd wrote: Maybe make rules that are very specific to the BBB and ERL IPs in question. And/or make sure 'egress' is the interface you thing it is. Okay, at this point I'm blaming the ISP issued router. I can't add a static route and therefore, I think it's to blame for nothing in 172.16.13.0/24 to get out to the internet. Well the ERL may still collect dust, but it will give me more of a reason to replace the ISP router for something decent. Thanks for all the help!