Re: Package -stable updates
> http://cdn.openbsd.org/pub/OpenBSD/6.5/packages-stable/amd64/ > updated binary packages (with security fixes) for stable, as described here > https://marc.info/?l=openbsd-announce=156577865917831=2 Uu Ooh - I am sorry :-( I managed to break my .muttrc and so I've overseen the announce of /packages-stable Excuse me!
Re: Incoming connection via VLAN
On Mon, Sep 02, 2019 at 05:51:23PM -, Stuart Henderson wrote: > On 2019-09-01, Felix Hanley wrote: > > I had assumed I would be able to use the existing pf.conf (which has > > worked for years) even after the introduction of the vlan2 interface > > as the pppoe0 parent. To get anything to work I had to remove all > > queueing references. > > Note that queues should be done on the *physical* interface, i.e. the > ethernet interface that is the parent of the vlan that is the parent of > the pppoe. I did not know that, thank you. I have no queueing at the moment. It is as if the daemons do not listen on the new em0 -> vlan2 -> pppoe0 chain of interfaces. I cannot even rdr-to localhost to connect to them. I have tried all the following variations: - IP address on vlan2 - Explicitly listening on various IP addresses (on vlan2 and pppoe0) - Disabling IPv6 completely The only incoming connections that work are those that I rdr-to hosts on the internal network. I am suspicious of my vlan2 config, particularly the txprio setting. It does not work without it but I know little about DSCP so I am not sure if I need to add something to pf.conf as well. Would that even stop packets to local daemons??: # cat /etc/hostname.vlan2 vnetid 2 parent em0 txprio 1 up Thanks again for your help. -felix
Re: Incoming connection via VLAN
On Mon, Sep 02, 2019 at 10:55:18AM -0400, Daniel Ouellet wrote: > It's hard trying to help you as. > > Vlan syntax changed from the upgrade or 6.1 to 6.2 and the pf queuing > changed from 6.3 to 6.4. > > So looks like you skip a few version and no where did you provide any > details on your configuration. I have not skipped any versions. My configs were in the original post. > So I would suggest to go and read either the man page or look at the > upgrade from 61. to 6.2 for your vlan part. > > https://www.openbsd.org/faq/upgrade62.html Yes, I am using the new syntax. > and then 6.3 to 6.4 for your pf part. > > https://www.openbsd.org/faq/upgrade64.html > > If you do upgrade a system it's always a good idea to go read the > excellent upgrade page before doing it. I have read the precious man pages and have not resolved the issue, hence posting to misc. > Assuming things never changed is not a good idea. Agreed. > OpenBSD will changed everything if that make sense to do at time, but > they also document it as well. > > For what I can read anyway and guess from your info is that look to me > to upgrade or skip a few version, or run an old configuration on a much > newer system without looking changes that happens. > > Worst case get your system working again and then read the vlan part if > you still have issue and experiment with that and get it back where you > want it. Read it, numerous times. > In any case with what you provided it's not possible to help or tell you > more, everything I wrote here is simply a guess based on your info. > > Hope this help you some. > > Daniel Thanks.
OpenBSD was right
I hope it is OK to share here: https://www.youtube.com/watch?v=jI3YE3Jlgw8 Jan
Re: handling snapshot installation in production environment
Stuart Henderson(s...@spacehopper.org) on 2019.09.02 17:58:55 -:
> On 2019-09-02, Marcus MERIGHI wrote:
> > Hello Joerg,
> >
> > just passing on my user experience...:
> >
> > streckf...@dfn-cert.de (Joerg Streckfuss), 2019.09.02 (Mon) 10:15 (CEST):
> >> Furthermore I'm not sure which snapshot should I run. Almost every day
> >> there will be a fresh one.
> >
> > you seem to be watching closely, therefore you will notice a time when
> > there are no new daily snapshots for a couple of days. this is usually
> > when the next release is tagged/built. additionally you can monitor
> > ports@ to see when the ports tree gets locked for the next release.
>
> Ports lock is no indication of the state of base. The locks are independent.
>
> >> Perhaps is there a moment/date where a
> >> freeze of the code base will be done which reflects the 6.6 release?
While a bit dated, this presentation explains what we do:
https://www.openbsd.org/papers/asiabsdcon2009-release_engineering/
> Use sysupgrade -n and monitor the OS version number ("what
> /home/_sysupgrade/bsd"). If you see 6.6-current it is post-release and
> you should not install it ("rm /bsd.upgrade"), you can then wait until
> actual release day and update to be sure you're running on the proper
> release binaries.
Re: What is you motivational to use OpenBSD
What motivates me to stay on OpenBSD is that I want the free desktop concept to work. This system + Arcan + GNOME-like interface seems, to me, like an compelling way to get there. I hope I can shoehorn this project into my life and then reality in some fashion. -- Patrick Harper paia...@fastmail.com On Wed, 28 Aug 2019, at 15:32, Mohamed salah wrote: > 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? >
Re: handling snapshot installation in production environment
This will only work if you stop upgrading snapshots long before 6.6 is announced. Otherwise you will be on 6.6-current by November 1st and -r will wait for 6.7. On September 2, 2019 1:15:26 PM GMT+02:00, Ian Darwin wrote: >> The sysupgrade tool is a nice way to install the newest snapshot, >never >> had a problem. But what is the correct way to install a stable >release >> on snapshot? Using the standard bsd.rd upgrade way? > >From man sysupgrade: > >-r Upgrade to the next release. The default is to find out if the > system is running a release or a snapshot. In case of release > sysupgrade downloads the next release. > >So when 6.6 is announced as released > > # sysupgrade -r -- Sent from a mobile device. Please excuse poor formating.
Re: Package -stable updates
In this thread I didn't understand what you update. You said you run STABLE? So you update ports? ...or using m:tier?? ...? Can somebody please tell me what are those "-stable updates for packages"? http://cdn.openbsd.org/pub/OpenBSD/6.5/packages-stable/amd64/ updated binary packages (with security fixes) for stable, as described here https://marc.info/?l=openbsd-announce=156577865917831=2
Re: obsd web server
On 2019-09-01, Gustavo Rios wrote: > i would like to confgiure my obsd server as a web server. > > I would like to configure my web server to handle multiple domains > without having to set each domain one by one. > > I mean: > Every request for www.x.com is mapped into the root directory > /var/web/www.x.com > > Got the idea ? If a new server is required, All i needed to do would > create a directory inside /var/web with the full access string : > > mkdir /var/web/www.newdomain.com > > And i should not need to manipulate config files. With nginx you can do e.g. root/sites/$http_host/htdocs; access_log /sites/$http_host/logs/access.log main; Apache httpd has a similar method (see the manual about "Mass Virtual Hosting"). httpd in the base OS does not support this.
Re: handling snapshot installation in production environment
On 2019-09-02, Marcus MERIGHI wrote:
> Hello Joerg,
>
> just passing on my user experience...:
>
> streckf...@dfn-cert.de (Joerg Streckfuss), 2019.09.02 (Mon) 10:15 (CEST):
>> Furthermore I'm not sure which snapshot should I run. Almost every day
>> there will be a fresh one.
>
> you seem to be watching closely, therefore you will notice a time when
> there are no new daily snapshots for a couple of days. this is usually
> when the next release is tagged/built. additionally you can monitor
> ports@ to see when the ports tree gets locked for the next release.
Ports lock is no indication of the state of base. The locks are independent.
>> Perhaps is there a moment/date where a
>> freeze of the code base will be done which reflects the 6.6 release?
Use sysupgrade -n and monitor the OS version number ("what
/home/_sysupgrade/bsd"). If you see 6.6-current it is post-release and
you should not install it ("rm /bsd.upgrade"), you can then wait until
actual release day and update to be sure you're running on the proper
release binaries.
Re: Incoming connection via VLAN
On 2019-09-01, Felix Hanley wrote: > I had assumed I would be able to use the existing pf.conf (which has worked > for years) even after the introduction of the > vlan2 interface as the pppoe0 parent. To get anything to work I had to remove > all queueing references. > > BTW, I am running 6.5: > > # uname -a > OpenBSD malkmus.xx.xx 6.5 GENERIC.MP#3 amd64 > > Thank you for any suggestions to try. > > -felix > > Note that queues should be done on the *physical* interface, i.e. the ethernet interface that is the parent of the vlan that is the parent of the pppoe.
support new
0 C Turkey P Ankara T Yenimahalle Z 06930 O Consultant I A Elvis Brul M elvisbr...@gmail.com U B +90-532-633-17-92 X N More than 5 years, OpenBSD setup installation remote administration. Network engineering, software development.
Re: handling snapshot installation in production environment
On 9/2/19 6:48 AM, Marcus MERIGHI wrote: > Hello Joerg, > > just passing on my user experience...: > > streckf...@dfn-cert.de (Joerg Streckfuss), 2019.09.02 (Mon) 10:15 (CEST): >> Furthermore I'm not sure which snapshot should I run. Almost every day >> there will be a fresh one. > > you seem to be watching closely, therefore you will notice a time when > there are no new daily snapshots for a couple of days. this is usually > when the next release is tagged/built. additionally you can monitor > ports@ to see when the ports tree gets locked for the next release. Careful with this ... While this is what I used to do (which is kinda odd, since I only run snapshots!), in recent releases, especially since the CD production was cut out of the release process, the time between "tagging" and resumed development and new snapshots has dropped a LOT to the point that it's difficult to catch. I think Ian's tip is a bit safer. Nick.
Re: obsd web server
On 9/1/19 5:49 PM, Gustavo Rios wrote:
> Hi folks,
>
> i would like to confgiure my obsd server as a web server.
>
> I would like to configure my web server to handle multiple domains
> without having to set each domain one by one.
>
> I mean:
> Every request for www.x.com is mapped into the root directory
> /var/web/www.x.com
>
> Got the idea ? If a new server is required, All i needed to do would
> create a directory inside /var/web with the full access string :
>
> mkdir /var/web/www.newdomain.com
>
> And i should not need to manipulate config files.
>
> Thanks in advance
I don't think that's doable as you request, nor do I think it is a
noble goal. , Unless you have a really really unusual use case, you
will have per-site specific settings -- for example, HTTPS
certificates.
HOWEVER, with some trivial scripting, you can easily accomplish something
that appears to be what you request. When you have a lot of similar
things to manage, think scripts. :) Here's a primitive and untested
concept:
newweb:
#!/bin/ksh
mkdir -m755 /var/www/$1
chown (whomwever) /var/www/$1
cat >>/etc/httpd <<__ENDSITE
server "$1" {
alias "www.$1"
listen on $ext_addr port 80
log style combined
log access $1.access
log error $1.error
root /$1
}
__ENDSITE
/etc/rc.d/httpd reload
Now, in real life, you would want to flesh out that config a bit
more, and you would probably want to save a copy of the httpd.conf
file, and check if httpd errored, and if so, restore the old copy.
Lots of other error checking would be appropriate as well.
You could also just do something more sophisticated, like create
an httpd.d directory and create a template domain.conf file in
there for each one, and just add an "include" line in your
httpd.conf for each new domain. Now when you decide that all your
domains are NOT just alike, you can easily rev the ones that are
different.
Nick.
antispoof or urpf-failed ?
hi everyone http://lists.dragonflybsd.org/pipermail/users/2017-August/313577.html states that the "urpf-failed" block rule causes the IPv6 traffic (ping) significant packet loss, while IPv4 remains fine is this correct ? https://lipidity.com/openbsd/router/ states The antispoof rules should be replaced by a strict Unicast Reverse Path Forwarding (uRPF) check: block in log quick from urpf-failed i have both antispoof and urpf-failed, should i leave both in my pf.conf or remove antispoof ? shadrock
Re: Unable to boot sparc from raid drive installation:Open ..... Invalid argument
Thanks for the detailed explanation. Really appreciated. All the best Regards, Kihaguru. On Mon, Sep 2, 2019 at 6:17 PM Stefan Sperling wrote: > On Mon, Sep 02, 2019 at 05:32:53PM +0300, Kihaguru Gathura wrote: > > Hi, > > > > Unable to boot with the following message > > > > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/etc/random.seed: Invalid > argument > > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/bsd: Invalid argument > > > Boot device: /pci@83,4000/FJSV,ulsa@2,1/disk@0,0 File and args: > > > Trying bsd... > > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/etc/random.seed: Invalid > argument > > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/bsd: Invalid argument > > BOOT_SPARC64(8)System Manager's Manual (sparc64) > BOOT_SPARC64(8) > > [...] > > To boot from a softraid(4) volume by default, boot-device must be set > to > a disk device hosting a chunk of the softraid volume: > >ok setenv boot-device disk0 > > and boot-file must contain the (sr) device name of the softraid volume > and optionally a partition letter and/or kernel: > >ok setenv boot-file sr0a:/bsd >
Re: Unable to boot sparc from raid drive installation:Open ..... Invalid argument
Thank you,
Works well
Regards,
Kihaguru
On Mon, Sep 2, 2019 at 6:07 PM Otto Moerbeek wrote:
> On Mon, Sep 02, 2019 at 05:32:53PM +0300, Kihaguru Gathura wrote:
>
> > Hi,
> >
> > Unable to boot with the following message
> >
> > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/etc/random.seed: Invalid
> argument
> > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/bsd: Invalid argument
> >
> > Not sure the issue with softraid setup detailed below. Any assistance
> > highly appreciated.
> >
> > Thanks and regards,
>
> Did you setup boot-file?
>
> Try
>
> boot sr0a:/bsd
>
> On the OpenBSD boot loader prompt.
>
> If that works you should setup boot-file as described in
>
> See http://man.openbsd.org/man8/sparc64/boot_sparc64.8
>
> -Otto
>
> >
> > Kihaguru.
> >
> >
> > {0} ok boot cdrom
> > Resetting ...
> >
> > Sep 02 08:57:03 GMT 2019 XSCF:I::[02030100] Start reset sequence
> > Sep 02 08:57:04 GMT 2019 XSCF:I::[02030200] Reset released...
> >
> > Sep 02 08:57:07 GMT 2019 PowerOn SelfTest start
> > POST:Testing Flash/SRAM
> > POST:Testing SC
> > POST:Testing XSCF
> > POST:Banner
> > POST:FATAL check
> > POST:Testing Timer1
> > POST:Testing Tick
> > POST:Testing MMU
> > POST:Testing CPU Type
> > POST:Testing DTAG
> > POST:Memory Probe
> > POST:Testing Memory
> > POST:Testing Softint
> > POST:Testing U2P
> > POST:Testing Slave Device
> > POST:Testing Master Device
> > POST:System Configure
> > POST:OBP Start
> > screen not found.
> > keyboard not found.
> > Keyboard not present. Using ttya for input and output.
> >
> > Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V, No Keyboard
> > OpenBoot 3.18.1-1, 16384 MB memory installed
> > Ethernet address 0:b:5d:f3:a7:5c, Host ID: 80f2a75c.
> > XSCF Version: 4.12.1
> >
> >
> >
> > Executing last command: boot cdrom
> > Boot device: /pci@83,4000/ide@d/cdrom@0,0:f File and args:
> > OpenBSD IEEE 1275 Bootblock 1.4
> > ..>> OpenBSD BOOT 1.12
> > Trying bsd...
> > open /pci@83,4000/ide@d/cdrom@0,0:f/etc/random.seed: No such file or
> > directory
> > Booting /pci@83,4000/ide@d/cdrom@0,0:f/bsd
> > 4145224@0x100+8120@0x13f4048+3255632@0x1c0+938672@0x1f1ad50
> > symbols @ 0xfeae4340 139 start=0x100
> > console is /pci@83,4000/isa@7/su@0,3f8
> > Copyright (c) 1982, 1986, 1989, 1991, 1993
> > The Regents of the University of California. All rights
> reserved.
> > Copyright (c) 1995-2019 OpenBSD. All rights reserved.
> > https://www.OpenBSD.org
> >
> > OpenBSD 6.5 (RAMDISK) #156: Sun Apr 14 05:14:17 MDT 2019
> > dera...@sparc64.openbsd.org:
> /usr/src/sys/arch/sparc64/compile/RAMDISK
> > real mem = 17179869184 (16384MB)
> > avail mem = 16869081088 (16087MB)
> > mainbus0 at root: Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V
> > cpu0 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz
> > cpu0: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K
> > external (64 b/l)
> > "FJSV,SPARC64-V" at mainbus0 not configured
> > psycho0 at mainbus0 addr 0xfffb2000: SUNW,psycho, impl 0, version 4, ign
> c0
> > psycho0: bus range 0-0, PCI bus 0
> > psycho0: dvma map fe00-, STC0 enabled
> > pci0 at psycho0
> > ebus0 at pci0 dev 1 function 0 "Sun PCIO EBus2" rev 0x01
> > "FJSV,scfc" at ebus0 addr 21-210085, 22-220031, 26-260001,
> > 27-28 ivec 0x23 not configured
> > "FJSV,flashprom" at ebus0 addr 0-3f not configured
> > clock1 at ebus0 addr 25-251fff: mk48t59
> > "FJSV,panel" at ebus0 addr 210011-210011 ivec 0x25 not configured
> > ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00
> > com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo
> > com0: console
> > com1 at ebus1 addr 2e8-2ef ivec 0x2b: ns16550a, 16 byte fifo
> > hme0 at pci0 dev 1 function 1 "Sun HME" rev 0x01: ivec 0xe1, address
> > 00:0b:5d:f3:a7:5c
> > nsphyter0 at hme0 phy 1: DP83843 10/100 PHY, rev. 0
> > mpi0 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x07: ivec 0xe0
> > mpi0: 0, firmware 1.0.12.0
> > scsibus0 at mpi0: 16 targets, initiator 7
> > sd0 at scsibus0 targ 0 lun 0: SCSI2
> > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR
> > sd0: 70007MB, 512 bytes/sector, 143374738 sectors
> > sd1 at scsibus0 targ 1 lun 0: SCSI2
> > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL
> > sd1: 70007MB, 512 bytes/sector, 143374738 sectors
> > mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
> > mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
> > pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4:
> DMA,
> > channel 0 configured to native-PCI, channel 1 configured to native-PCI
> > pciide0: using ivec 0xe4 for native-PCI interrupt
> > atapiscsi0 at pciide0 channel 0 drive 0
> > scsibus1 at atapiscsi0: 2 targets
> > cd0 at scsibus1 targ 0 lun 0: ATAPI
> > 5/cdrom removable
> > cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> > pciide0: channel 1 disabled (no drives)
> > ohci0 at pci0 dev 10 function 0 "Acer Labs M5237
Re: Unable to boot sparc from raid drive installation:Open ..... Invalid argument
On Mon, Sep 02, 2019 at 05:32:53PM +0300, Kihaguru Gathura wrote: > Hi, > > Unable to boot with the following message > > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/etc/random.seed: Invalid argument > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/bsd: Invalid argument > Boot device: /pci@83,4000/FJSV,ulsa@2,1/disk@0,0 File and args: > Trying bsd... > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/etc/random.seed: Invalid argument > open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/bsd: Invalid argument BOOT_SPARC64(8)System Manager's Manual (sparc64) BOOT_SPARC64(8) [...] To boot from a softraid(4) volume by default, boot-device must be set to a disk device hosting a chunk of the softraid volume: ok setenv boot-device disk0 and boot-file must contain the (sr) device name of the softraid volume and optionally a partition letter and/or kernel: ok setenv boot-file sr0a:/bsd
Re: Unable to boot sparc from raid drive installation:Open ..... Invalid argument
On Mon, Sep 02, 2019 at 05:32:53PM +0300, Kihaguru Gathura wrote:
> Hi,
>
> Unable to boot with the following message
>
> open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/etc/random.seed: Invalid argument
> open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/bsd: Invalid argument
>
> Not sure the issue with softraid setup detailed below. Any assistance
> highly appreciated.
>
> Thanks and regards,
Did you setup boot-file?
Try
boot sr0a:/bsd
On the OpenBSD boot loader prompt.
If that works you should setup boot-file as described in
See http://man.openbsd.org/man8/sparc64/boot_sparc64.8
-Otto
>
> Kihaguru.
>
>
> {0} ok boot cdrom
> Resetting ...
>
> Sep 02 08:57:03 GMT 2019 XSCF:I::[02030100] Start reset sequence
> Sep 02 08:57:04 GMT 2019 XSCF:I::[02030200] Reset released...
>
> Sep 02 08:57:07 GMT 2019 PowerOn SelfTest start
> POST:Testing Flash/SRAM
> POST:Testing SC
> POST:Testing XSCF
> POST:Banner
> POST:FATAL check
> POST:Testing Timer1
> POST:Testing Tick
> POST:Testing MMU
> POST:Testing CPU Type
> POST:Testing DTAG
> POST:Memory Probe
> POST:Testing Memory
> POST:Testing Softint
> POST:Testing U2P
> POST:Testing Slave Device
> POST:Testing Master Device
> POST:System Configure
> POST:OBP Start
> screen not found.
> keyboard not found.
> Keyboard not present. Using ttya for input and output.
>
> Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V, No Keyboard
> OpenBoot 3.18.1-1, 16384 MB memory installed
> Ethernet address 0:b:5d:f3:a7:5c, Host ID: 80f2a75c.
> XSCF Version: 4.12.1
>
>
>
> Executing last command: boot cdrom
> Boot device: /pci@83,4000/ide@d/cdrom@0,0:f File and args:
> OpenBSD IEEE 1275 Bootblock 1.4
> ..>> OpenBSD BOOT 1.12
> Trying bsd...
> open /pci@83,4000/ide@d/cdrom@0,0:f/etc/random.seed: No such file or
> directory
> Booting /pci@83,4000/ide@d/cdrom@0,0:f/bsd
> 4145224@0x100+8120@0x13f4048+3255632@0x1c0+938672@0x1f1ad50
> symbols @ 0xfeae4340 139 start=0x100
> console is /pci@83,4000/isa@7/su@0,3f8
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California. All rights reserved.
> Copyright (c) 1995-2019 OpenBSD. All rights reserved.
> https://www.OpenBSD.org
>
> OpenBSD 6.5 (RAMDISK) #156: Sun Apr 14 05:14:17 MDT 2019
> dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/RAMDISK
> real mem = 17179869184 (16384MB)
> avail mem = 16869081088 (16087MB)
> mainbus0 at root: Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V
> cpu0 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz
> cpu0: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K
> external (64 b/l)
> "FJSV,SPARC64-V" at mainbus0 not configured
> psycho0 at mainbus0 addr 0xfffb2000: SUNW,psycho, impl 0, version 4, ign c0
> psycho0: bus range 0-0, PCI bus 0
> psycho0: dvma map fe00-, STC0 enabled
> pci0 at psycho0
> ebus0 at pci0 dev 1 function 0 "Sun PCIO EBus2" rev 0x01
> "FJSV,scfc" at ebus0 addr 21-210085, 22-220031, 26-260001,
> 27-28 ivec 0x23 not configured
> "FJSV,flashprom" at ebus0 addr 0-3f not configured
> clock1 at ebus0 addr 25-251fff: mk48t59
> "FJSV,panel" at ebus0 addr 210011-210011 ivec 0x25 not configured
> ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00
> com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo
> com0: console
> com1 at ebus1 addr 2e8-2ef ivec 0x2b: ns16550a, 16 byte fifo
> hme0 at pci0 dev 1 function 1 "Sun HME" rev 0x01: ivec 0xe1, address
> 00:0b:5d:f3:a7:5c
> nsphyter0 at hme0 phy 1: DP83843 10/100 PHY, rev. 0
> mpi0 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x07: ivec 0xe0
> mpi0: 0, firmware 1.0.12.0
> scsibus0 at mpi0: 16 targets, initiator 7
> sd0 at scsibus0 targ 0 lun 0: SCSI2
> 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR
> sd0: 70007MB, 512 bytes/sector, 143374738 sectors
> sd1 at scsibus0 targ 1 lun 0: SCSI2
> 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL
> sd1: 70007MB, 512 bytes/sector, 143374738 sectors
> mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
> mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
> pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: DMA,
> channel 0 configured to native-PCI, channel 1 configured to native-PCI
> pciide0: using ivec 0xe4 for native-PCI interrupt
> atapiscsi0 at pciide0 channel 0 drive 0
> scsibus1 at atapiscsi0: 2 targets
> cd0 at scsibus1 targ 0 lun 0: ATAPI
> 5/cdrom removable
> cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 disabled (no drives)
> ohci0 at pci0 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec 0xe9,
> version 1.0, legacy support
> usb0 at ohci0: USB revision 1.0
> uhub0 at usb0 configuration 1 interface 0 "Acer Labs OHCI root hub" rev
> 1.00/1.00 addr 1
> psycho1 at mainbus0 addr 0xfff9e000: SUNW,psycho, impl 0, version 4, ign c0
> psycho1: bus range 128-128, PCI bus 128
> psycho1: dvma map fe00-, STC0
Re: Incoming connection via VLAN
It's hard trying to help you as. Vlan syntax changed from the upgrade or 6.1 to 6.2 and the pf queuing changed from 6.3 to 6.4. So looks like you skip a few version and no where did you provide any details on your configuration. So I would suggest to go and read either the man page or look at the upgrade from 61. to 6.2 for your vlan part. https://www.openbsd.org/faq/upgrade62.html and then 6.3 to 6.4 for your pf part. https://www.openbsd.org/faq/upgrade64.html If you do upgrade a system it's always a good idea to go read the excellent upgrade page before doing it. Assuming things never changed is not a good idea. OpenBSD will changed everything if that make sense to do at time, but they also document it as well. For what I can read anyway and guess from your info is that look to me to upgrade or skip a few version, or run an old configuration on a much newer system without looking changes that happens. Worst case get your system working again and then read the vlan part if you still have issue and experiment with that and get it back where you want it. In any case with what you provided it's not possible to help or tell you more, everything I wrote here is simply a guess based on your info. Hope this help you some. Daniel On 9/1/19 9:04 AM, Felix Hanley wrote: > I had assumed I would be able to use the existing pf.conf (which has worked > for years) even after the introduction of the > vlan2 interface as the pppoe0 parent. To get anything to work I had to remove > all queueing references. > > BTW, I am running 6.5: > > # uname -a > OpenBSD malkmus.xx.xx 6.5 GENERIC.MP#3 amd64 > > Thank you for any suggestions to try. > > -felix >
Unable to boot sparc from raid drive installation:Open ..... Invalid argument
Hi,
Unable to boot with the following message
open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/etc/random.seed: Invalid argument
open /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a/bsd: Invalid argument
Not sure the issue with softraid setup detailed below. Any assistance
highly appreciated.
Thanks and regards,
Kihaguru.
{0} ok boot cdrom
Resetting ...
Sep 02 08:57:03 GMT 2019 XSCF:I::[02030100] Start reset sequence
Sep 02 08:57:04 GMT 2019 XSCF:I::[02030200] Reset released...
Sep 02 08:57:07 GMT 2019 PowerOn SelfTest start
POST:Testing Flash/SRAM
POST:Testing SC
POST:Testing XSCF
POST:Banner
POST:FATAL check
POST:Testing Timer1
POST:Testing Tick
POST:Testing MMU
POST:Testing CPU Type
POST:Testing DTAG
POST:Memory Probe
POST:Testing Memory
POST:Testing Softint
POST:Testing U2P
POST:Testing Slave Device
POST:Testing Master Device
POST:System Configure
POST:OBP Start
screen not found.
keyboard not found.
Keyboard not present. Using ttya for input and output.
Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V, No Keyboard
OpenBoot 3.18.1-1, 16384 MB memory installed
Ethernet address 0:b:5d:f3:a7:5c, Host ID: 80f2a75c.
XSCF Version: 4.12.1
Executing last command: boot cdrom
Boot device: /pci@83,4000/ide@d/cdrom@0,0:f File and args:
OpenBSD IEEE 1275 Bootblock 1.4
..>> OpenBSD BOOT 1.12
Trying bsd...
open /pci@83,4000/ide@d/cdrom@0,0:f/etc/random.seed: No such file or
directory
Booting /pci@83,4000/ide@d/cdrom@0,0:f/bsd
4145224@0x100+8120@0x13f4048+3255632@0x1c0+938672@0x1f1ad50
symbols @ 0xfeae4340 139 start=0x100
console is /pci@83,4000/isa@7/su@0,3f8
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2019 OpenBSD. All rights reserved.
https://www.OpenBSD.org
OpenBSD 6.5 (RAMDISK) #156: Sun Apr 14 05:14:17 MDT 2019
dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/RAMDISK
real mem = 17179869184 (16384MB)
avail mem = 16869081088 (16087MB)
mainbus0 at root: Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V
cpu0 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz
cpu0: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K
external (64 b/l)
"FJSV,SPARC64-V" at mainbus0 not configured
psycho0 at mainbus0 addr 0xfffb2000: SUNW,psycho, impl 0, version 4, ign c0
psycho0: bus range 0-0, PCI bus 0
psycho0: dvma map fe00-, STC0 enabled
pci0 at psycho0
ebus0 at pci0 dev 1 function 0 "Sun PCIO EBus2" rev 0x01
"FJSV,scfc" at ebus0 addr 21-210085, 22-220031, 26-260001,
27-28 ivec 0x23 not configured
"FJSV,flashprom" at ebus0 addr 0-3f not configured
clock1 at ebus0 addr 25-251fff: mk48t59
"FJSV,panel" at ebus0 addr 210011-210011 ivec 0x25 not configured
ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00
com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo
com0: console
com1 at ebus1 addr 2e8-2ef ivec 0x2b: ns16550a, 16 byte fifo
hme0 at pci0 dev 1 function 1 "Sun HME" rev 0x01: ivec 0xe1, address
00:0b:5d:f3:a7:5c
nsphyter0 at hme0 phy 1: DP83843 10/100 PHY, rev. 0
mpi0 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x07: ivec 0xe0
mpi0: 0, firmware 1.0.12.0
scsibus0 at mpi0: 16 targets, initiator 7
sd0 at scsibus0 targ 0 lun 0: SCSI2
0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR
sd0: 70007MB, 512 bytes/sector, 143374738 sectors
sd1 at scsibus0 targ 1 lun 0: SCSI2
0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL
sd1: 70007MB, 512 bytes/sector, 143374738 sectors
mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide0: using ivec 0xe4 for native-PCI interrupt
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: ATAPI
5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 disabled (no drives)
ohci0 at pci0 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec 0xe9,
version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Acer Labs OHCI root hub" rev
1.00/1.00 addr 1
psycho1 at mainbus0 addr 0xfff9e000: SUNW,psycho, impl 0, version 4, ign c0
psycho1: bus range 128-128, PCI bus 128
psycho1: dvma map fe00-, STC0 enabled, STC1 enabled
pci1 at psycho1
bge0 at pci1 dev 1 function 0 "Fujitsu PRIMEPOWER250/450 LAN" rev 0x02,
BCM5702/5703 A2 (0x1002): ivec 0xc0, address 00:0b:5d:f4:27:5c
brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
timer0 at mainbus0 addr 0xfff8bc00 ivec 0xec, 0xed
softraid0 at root
scsibus2 at softraid0: 256 targets
bootpath: /pci@83,4000/ide@d,0/cdrom@0,0:f
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T
Welcome to the OpenBSD/sparc64 6.5 installation program.
Re: support new
Please go away. If somebody needs half a dozen tries before they manage to send an email, that person is not qualified to help others with computers. Rakort Information Technologies wrote on Mon, Sep 02, 2019 at 04:31:19PM +0300: > 0 > C Turkey > P Ankara > T Cankaya > Z 06510 > O Rakort Information Technologies > I Rakort Information Technologies > A 2139. Street 2/11 > M rakorti...@gmail.com > U http://www.rakort.com > B +90-850-460-10-58 > X > N More than 5 years, OpenBSD setup/installation/remote administration. > Network engineering, software development. Also experienced with > Solaris and Linux. We specialize in providing open source solutions > for businesses using OpenBSD and Linux. CCNP, RHCE certifications, > VPNs, firewalls, wireless, DNS, squidGuard, mail - even training with > OpenBSD. We have more then 5 years experience with the OpenBSD > platform and are able to deliver 24/7 solutions with necessary SLA's.
support new
0 C Turkey P Ankara T Cankaya Z 06510 O Rakort Information Technologies I Rakort Information Technologies A 2139. Street 2/11 M rakorti...@gmail.com U http://www.rakort.com B +90-850-460-10-58 X N More than 5 years, OpenBSD setup/installation/remote administration. Network engineering, software development. Also experienced with Solaris and Linux. We specialize in providing open source solutions for businesses using OpenBSD and Linux. CCNP, RHCE certifications, VPNs, firewalls, wireless, DNS, squidGuard, mail - even training with OpenBSD. We have more then 5 years experience with the OpenBSD platform and are able to deliver 24/7 solutions with necessary SLA's.
Re: handling snapshot installation in production environment
Hello Joerg, just passing on my user experience...: streckf...@dfn-cert.de (Joerg Streckfuss), 2019.09.02 (Mon) 10:15 (CEST): > Furthermore I'm not sure which snapshot should I run. Almost every day > there will be a fresh one. you seem to be watching closely, therefore you will notice a time when there are no new daily snapshots for a couple of days. this is usually when the next release is tagged/built. additionally you can monitor ports@ to see when the ports tree gets locked for the next release. > Perhaps is there a moment/date where a > freeze of the code base will be done which reflects the 6.6 release? Yes, the moment I tried to describe above. Marcus
Re: handling snapshot installation in production environment
> The sysupgrade tool is a nice way to install the newest snapshot, never > had a problem. But what is the correct way to install a stable release > on snapshot? Using the standard bsd.rd upgrade way? >From man sysupgrade: -r Upgrade to the next release. The default is to find out if the system is running a release or a snapshot. In case of release sysupgrade downloads the next release. So when 6.6 is announced as released # sysupgrade -r
4DEE-D811-E382
accept
support new
0 C Turkey P Ankara T Cankaya Z 06520 O Consultant I Ibrahim TOPBASI A M ibrahimtopb...@linuxmail.org U B +90 532 633 17 92 X N OpenBSD Consulting, Training, Installation, Maintenance and Support for mid-size business. Over 5 years of experience with OpenBSD and PF firewall.We have more then 5 years experience with the OpenBSD platform and are able to deliver 24/7 solutions with necessary SLA's.
Support New
0 C Turkey P Ankara T Cankaya Z 06510 O Rakort Information Technologies I ibrahim Topbasi A 2139. Street 2/11 M open...@rakort.com U http://www.rakort.com B +90-850-460-10-58 X N More than 5 years, OpenBSD setup/installation/remote administration. Network engineering, software development. Also experienced with Solaris and Linux. We specialize in providing open source solutions for businesses using OpenBSD and Linux. CCNP, RHCE certifications, VPNs, firewalls, wireless, DNS, squidGuard, mail - even training with OpenBSD. We have more then 5 years experience with the OpenBSD platform and are able to deliver 24/7 solutions with necessary SLA's.
Re: support new
Hello Ingo,� First of all, thanks for quick reply.� The website is also presented as English now. You can visit the website to see what we do and our experience about openbsd.� We would like to give openbsd support as Rakort in Turkey. Therefore, Would you add openbsd.org commercial support list for Turkey ?� The information is follow;� 0C TURKEYP AnkaraT CankayaZ 06510A 2139. Street 2/11O Rakort Information TechnologiesI Ebubekir OkurM open...@rakort.comu http://www.rakort.comB 90-850-460-10-58X 90-850-460-10-58N More than 5 years, OpenBSD setup/installation/remote administration. Network engineering, software development(C/Python/PHP/PostgreSQL/MySQL). Also experienced with Solaris and Linux.We specialize in providing solid open source solutions for businesses using OpenBSD, � and Linux. MCSE, CCNP, RHCE certifications, VPNs, firewalls, wireless, DNS, squidGuard, mail - even training with OpenBSD.� 29.08.2019, 12:43, "Ingo Schwarze" : Hello Ibrahim, Ibrahim Topbasi wrote on Thu, Aug 29, 2019 at 12:04:39PM +0300: � � 0C TURKEYP AnkaraT CankayaZ 06510A 2139. Street 2/11O Rakort Information � TechnologiesI Ibrahim TopbasiM open...@rakort.comu http://www.rakort.comB � 90-850-460-10-58X 90-850-460-10-58N More than 5 years, OpenBSD � setup/installation/remote administration. Network engineering, software � development(C/Python/PHP/PostgreSQL/MySQL). Also experienced with Solaris � and Linux.We specialize in providing solid open source solutions for � businesses using OpenBSD, ? and Linux. MCSE, CCNA, RHCE certifications, � VPNs, firewalls, wireless, DNS, squidGuard, mail - even training with � OpenBSD. It would no doubt be nice to have a support.html entry for Turkey, but i'm not convinced i want to add a person who is not even able to send properly formatted email. Then, i consider using "OpenBSD OpenBSD" as the comment in the From: Header of outgoing email pretentious, maybe even offensive. A serious business would put the real name of a real person in that place and additionally use the Reply-To: header. Besides, while i guess it is OK that the website is in Turkish language only, it doesn't appear to even mention OpenBSD, so i think this request ought to be disregarded. Yours, � � Ingo � -- Ingo Schwarze http://www.openbsd.org/ http://mandoc.bsd.lv/
Re: obsd web server
Hi gustavo, my own expirience with this list is that you will receive very good answers and tips from experienced people. ...but only if you try to ask good questions ;-) With "good questions" I mean for example writing about what you want to do, what you have done by now, what is not working, giving filenames, errormessages, logfiles... - and of course asking a question ;-) Because in your mail you have failed to tell what you have tried so far. You didn't telll us what you expect and what failed or what errormessage you receive. And - maybe I read wrong - there is no specific question in your mail. If you fix the above, I will be sure that someone will jump in and help On Sun, Sep 01, 2019 at 08:49:45PM -0300, Gustavo Rios wrote: > Hi folks, > > i would like to confgiure my obsd server as a web server. > > I would like to configure my web server to handle multiple domains > without having to set each domain one by one. > > I mean: > Every request for www.x.com is mapped into the root directory > /var/web/www.x.com > > Got the idea ? If a new server is required, All i needed to do would > create a directory inside /var/web with the full access string : > > mkdir /var/web/www.newdomain.com > > And i should not need to manipulate config files. > > Thanks in advance > > -- > Pag Bem Fácil Ltda > www.pagbemfacil.com.br > -- Viele Grüße Michael
Re: Package -stable updates
In this thread I didn't understand what you update. You said you run STABLE? So you update ports? ...or using m:tier?? ...? Can somebody please tell me what are those "-stable updates for packages"? On Wed, Aug 28, 2019 at 07:59:59PM -0400, Steven Shockley wrote: > So, many thanks to everyone who put together the new -stable updates for > packages. Is there a command I can put in the crontab that will only > output if there are updates? Similar to what syspatch or openup does. > I tried pkg_add -unx, but that still tells me to delete old files and > prints the quirks line even if there are no updates. >
handling snapshot installation in production environment
Hi Misc, we have to run 6.6 snapshot on one of our firewall clusters to get in touch with the new aggr(4) driver. This driver seems to work great whith 6.6 snapshot on a dell pe 470 with intel X710 based quadport sfp+ nics doing LACP. We had serious problems with the trunk(4) driver on OpenBSD 6.5 stable which I discribed in the thread "Dell PE R740, Intel X710 QuadPort & LACP not working". I am new in running snapshots in production environments. Our goal is to run the 6.6 snapshot till 6.6 will be released. The sysupgrade tool is a nice way to install the newest snapshot, never had a problem. But what is the correct way to install a stable release on snapshot? Using the standard bsd.rd upgrade way? Furthermore I'm not sure which snapshot should I run. Almost every day there will be a fresh one. Perhaps is there a moment/date where a freeze of the code base will be done which reflects the 6.6 release? Thanks.
