LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Other *NIX Forums > *BSD
User Name
Password
*BSD This forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.

Notices


Reply
  Search this Thread
Old 10-09-2017, 11:01 AM   #1
hitest
LQ Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, Debian, OpenBSD
Posts: 5,184

Rep: Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177
OpenBSD 6.2 Released


OpenBSD 6.2 Released.

Code:
$ uname -a
OpenBSD bsd 6.2 GENERIC.MP#134 amd64
http://www.openbsd.org/62.html
 
Old 10-10-2017, 06:48 AM   #2
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Void
Posts: 94

Rep: Reputation: 33
Hmm,

this was the first time my OpenBSD server failed to connect its ethernet correctly after the reboot. Probably a sysmerge thing...
 
Old 10-10-2017, 07:35 AM   #3
Randicus Draco Albus
Senior Member
 
Registered: May 2011
Location: Hiding somewhere on planet Earth.
Distribution: No distribution. OpenBSD operating system
Posts: 1,672
Blog Entries: 8

Rep: Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603
It may be related to the configuration changes. Keep in mind that I actually do not know and this is strictly conjecture on my part.
Quote:
Configuration and syntax changes

hostname.if. The keyword rtsol is no longer supported in hostname.if(5). Replace it with inet6 autoconf.
install.site. The execution of the {install,upgrade}.site scripts in bsd.rd is postponed to the end of the installer script. If you use this feature, make sure your script still works as expected. The script will now run after these steps:
make underlying device nodes for softraid devices
install the boot-block on disk
switch to MP kernel on multi-processor systems
update kernel.SHA256 and relink kernel
prepare execution of sysmerge(8), fw_update(8) and syspatch(8) on reboot.
prepare mail with response file to root/admin user
ifconfig. The vlan(4) and svlan(4) specific configuration options in ifconfig(8) and hostname.if(5) have been deprecated in favour of the generic parent and vnetid handling.
The vlan, vlandev, and -vlandev options are now deprecated in favour of vnetid, -vnetid, parent, and -parent when using ifconfig(8) or in hostname.if(5) configuration files. Use of the vlan option must be replaced with vnetid. Because VLAN tag 0 is invalid according to the relevant VLAN specifications, the vnetid option does not accept 0 as a valid network identifier. To use VLAN tag 0 on the wire the vnetid can be unconfigured with -vnetid. Use of vlandev and -vlandev must be replaced with parent and -parent respectively.

Unlike vlan and vlandev, vnetid and parent do not implicitly bring the vlan interface up. Similarly, the vlan option is no longer implied by the interface's minor when it is not explicitly set.

ifconfig(8) no longer outputs a vlan specific status line, or separate vnetid and parent lines. The vnetid and parent lines have been merged into a single encap line containing the VLAN tag and parent information.

An example of the changes to a vlan(4) configuration file and the ifconfig(8) output is below. Before the changes:

Code:
  # cat /etc/hostname.vlan7
  vlandev em0 # vlan 7 and up are implied
  lladdr random
  # ifconfig vlan7
  vlan7: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
          lladdr 70:a7:3a:75:da:2d
          index 7 priority 0 llprio 3
          vlan: 7 parent interface: em0
          vnetid: 7
          parent: em0
          status: active
After the changes:
Code:
  # cat /etc/hostname.vlan7
  vnetid 7 parent em0
  up
  lladdr random
  # ifconfig vlan7
  vlan7: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
          lladdr 60:e8:d7:0d:10:6d
          index 7 priority 0 llprio 3
          encap: vnetid 7 parent: em0
          groups: vlan
          status: active
 
1 members found this post helpful.
Old 10-10-2017, 07:36 AM   #4
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Void
Posts: 94

Rep: Reputation: 33
I was able to just start dhclient manually which made all issues go away, but I really wonder what happened. I need to examine this over the next weekend or so.
 
Old 10-10-2017, 09:48 AM   #5
hitest
LQ Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, Debian, OpenBSD
Posts: 5,184

Original Poster
Rep: Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177Reputation: 1177
Upgrade cycle complete. Very smooth.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
OpenBSD 6.0 released September 1/16 hitest *BSD 2 09-05-2016 10:06 AM
OpenBSD 5.9 released (early!) JWJones *BSD 6 04-01-2016 08:19 PM
OpenBSD 5.7 released hitest *BSD 9 05-25-2015 05:46 AM
OpenBSD 5.6 released hitest *BSD 12 11-27-2014 08:09 PM
LXer: OpenBSD: 3.9 Released LXer Syndicated Linux News 0 05-01-2006 09:33 PM

LinuxQuestions.org > Forums > Other *NIX Forums > *BSD

All times are GMT -5. The time now is 05:16 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration