Re: rc.firsttime after package daemons
On 2021-11-01, Kapetanakis Giannis wrote: > Hi, > > Just a notice for this. > I have a system which is a DNS server it self and runs isc-bind, so the > daemon is started from $pkg_scripts. > > rc.firsttime is run before pkg daemons are started so the system cannot (yet) > resolve since it lists itself in /etc/resolv.conf > > If there is no other reason, maybe rc.firsttime could be moved after package > daemons are started. rc.firsttime has to be earlier. I strongly recommend listing a second nameserver in resolv.conf
Re: pkg_add failing with TLS handshake failure
Check your system time maybe? On 11/1/21 18:06, rahul deshmukh wrote: Hi Team, while installing new packages i am getting below error. myhost01$ doas pkg_add rust https://cdn.openbsd.org/pub/OpenBSD/7.0/packages-stable/amd64/: TLS handshake failure: ocsp verify failed: ocsp response not current https://cdn.openbsd.org/pub/OpenBSD/7.0/packages/amd64/: TLS handshake failure: ocsp verify failed: ocsp response not current https://cdn.openbsd.org/pub/OpenBSD/7.0/packages/amd64/: empty Can't find rust myhost01$ cat /etc/installurl https://cdn.openbsd.org/pub/OpenBSD myhost01$ uname -a OpenBSD Home01.home.net 7.0 GENERIC.MP#232 amd64
pkg_add failing with TLS handshake failure
Hi Team, while installing new packages i am getting below error. myhost01$ doas pkg_add rust https://cdn.openbsd.org/pub/OpenBSD/7.0/packages-stable/amd64/: TLS handshake failure: ocsp verify failed: ocsp response not current https://cdn.openbsd.org/pub/OpenBSD/7.0/packages/amd64/: TLS handshake failure: ocsp verify failed: ocsp response not current https://cdn.openbsd.org/pub/OpenBSD/7.0/packages/amd64/: empty Can't find rust myhost01$ cat /etc/installurl https://cdn.openbsd.org/pub/OpenBSD myhost01$ uname -a OpenBSD Home01.home.net 7.0 GENERIC.MP#232 amd64 -- Thank you - Rahul Deshmukh
Re: Dhcp client configuration in 7.0
On Mon, Nov 1, 2021 at 10:33 AM Arnoud Otten wrote:
> Hi Benno,
>
>
> It looks like it is working right now, even after a restart of the router
> the extra dns server is not added to
> resolv.conf with resolvd enabled and started. The first nameserver
> 213.75.116.129 entry was added when i enabled
> resolvd again, and did not have the "ignore dns" options in place. Then i
> did the steps you asked for.
>
Sorry for the late answer. I was away. The same thing I experienced also
today. Now resolvd is behaving as expected. I do not now what changed as
the configuration was the same from my last attempt, when resolvd was keep
adding the ISP DNS.
Thank you all for your time and help!
> * run "route -n monitor"
> * empty the dhcpleased.conf: mv /etc/dhcpleased.conf /etc/X.dhcpleased.conf
> * cat /etc/resolv.conf, copy the output into an email.
>
> nameserver 213.75.116.129 # resolvd: vlan4
> lookup file bind
> nameserver 127.0.0.1
>
> * restart dhcpleased: doas /etc/rc.d/dhcpleased restart
> * copy the output of "route -n monitor" into the email
> fw# route -n monitor
> got message of size 176 on Mon Nov 1 09:15:38 2021
> RTM_DELETE: Delete Route: len 176, priority 8, table 0, if# 1, name em0,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 239.255.255.250 192.168.2.1 00:24:81:82:19:6d 192.168.2.1
> got message of size 176 on Mon Nov 1 09:16:05 2021
> RTM_ADD: Add Route: len 176, priority 8, table 0, if# 1, name em0, pid: 0,
> seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 239.255.255.250 192.168.2.1 00:24:81:82:19:6d 192.168.2.1
> got message of size 232 on Mon Nov 1 09:16:31 2021
> RTM_PROPOSAL: config proposal: len 232, source dhcp, table 0, if# 9, name
> vlan4, pid: 49678, seq 1, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> proposals:
> INET []
> got message of size 192 on Mon Nov 1 09:16:31 2021
> RTM_DELETE: Delete Route: len 192, priority 3, table 0, if# 9, name vlan4,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 10.200.240.1 link#9 00:24:81:82:19:6e 10.200.240.46
> got message of size 192 on Mon Nov 1 09:16:31 2021
> RTM_DELETE: Delete Route: len 192, priority 4, table 0, if# 9, name vlan4,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 10.200.240.0 10.200.240.46 255.255.252.0 00:24:81:82:19:6e 10.200.240.46
> got message of size 176 on Mon Nov 1 09:16:31 2021
> RTM_DELETE: Delete Route: len 176, priority 1, table 0, if# 9, name vlan4,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 10.200.243.255 10.200.240.46 00:24:81:82:19:6e 10.200.240.46
> got message of size 192 on Mon Nov 1 09:16:31 2021
> RTM_DELETE: Delete Route: len 192, priority 1, table 0, if# 9, name vlan4,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 10.200.240.46 00:24:81:82:19:6e 00:24:81:82:19:6e 10.200.240.46
> got message of size 96 on Mon Nov 1 09:16:31 2021
> RTM_DELADDR: address being removed from iface: len 96, if# 9, name vlan4,
> metric 0, flags:
> sockaddrs:
> 255.255.252.0 00:24:81:82:19:6e 10.200.240.46 10.200.243.255
> got message of size 232 on Mon Nov 1 09:16:31 2021
> RTM_DELETE: Delete Route: len 232, priority 8, table 0, if# 9, name vlan4,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 213.75.112.0 10.200.240.1 255.255.248.0 00:24:81:82:19:6e 10.200.240.46
> "dhcpleased"
> got message of size 176 on Mon Nov 1 09:16:31 2021
> RTM_DELETE: Delete Route: len 176, priority 8, table 0, if# 9, name vlan4,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> locks: inits:
> sockaddrs:
> 224.3.2.6 10.200.240.46 00:24:81:82:19:6e 10.200.240.46
>
>
> * cat /etc/resolv.conf, copy the output into the email.
>
> lookup file bind
> nameserver 127.0.0.1
>
>
> then run dhcpleased with the configuration file:
>
> * run "route -n monitor"
> * mv /etc/X.dhcpleased.conf /etc/dhcpleased.conf
> * cat /etc/dhcpleased.conf and copy the output into the email
>
> interface vlan4 {
> send vendor class id "IPTV_RG"
> ignore dns
> }
>
> * cat /etc/resolv.conf, copy the output into the email.
>
>
> lookup file bind
> nameserver 127.0.0.1
>
> * restart dhcpleased: doas /etc/rc.d/dhcpleased restart
> * copy the output of "route -n monitor" into the email
>
> got message of size 176 on Mon Nov 1 09:19:40 2021
> RTM_DELETE: Delete Route: len 176, priority 8, table 0, if# 1, name em0,
> pid: 0, seq 0, errno 0
> flags:
> fmask:
> use:0 mtu:0expire:0
> loc
rc.firsttime after package daemons
Hi, Just a notice for this. I have a system which is a DNS server it self and runs isc-bind, so the daemon is started from $pkg_scripts. rc.firsttime is run before pkg daemons are started so the system cannot (yet) resolve since it lists itself in /etc/resolv.conf If there is no other reason, maybe rc.firsttime could be moved after package daemons are started. best, Giannis
Re: Dhcp client configuration in 7.0
Hi Benno,
It looks like it is working right now, even after a restart of the router the
extra dns server is not added to
resolv.conf with resolvd enabled and started. The first nameserver
213.75.116.129 entry was added when i enabled
resolvd again, and did not have the "ignore dns" options in place. Then i did
the steps you asked for.
* run "route -n monitor"
* empty the dhcpleased.conf: mv /etc/dhcpleased.conf /etc/X.dhcpleased.conf
* cat /etc/resolv.conf, copy the output into an email.
nameserver 213.75.116.129 # resolvd: vlan4
lookup file bind
nameserver 127.0.0.1
* restart dhcpleased: doas /etc/rc.d/dhcpleased restart
* copy the output of "route -n monitor" into the email
fw# route -n monitor
got message of size 176 on Mon Nov 1 09:15:38 2021
RTM_DELETE: Delete Route: len 176, priority 8, table 0, if# 1, name em0, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
239.255.255.250 192.168.2.1 00:24:81:82:19:6d 192.168.2.1
got message of size 176 on Mon Nov 1 09:16:05 2021
RTM_ADD: Add Route: len 176, priority 8, table 0, if# 1, name em0, pid: 0, seq
0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
239.255.255.250 192.168.2.1 00:24:81:82:19:6d 192.168.2.1
got message of size 232 on Mon Nov 1 09:16:31 2021
RTM_PROPOSAL: config proposal: len 232, source dhcp, table 0, if# 9, name
vlan4, pid: 49678, seq 1, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
proposals:
INET []
got message of size 192 on Mon Nov 1 09:16:31 2021
RTM_DELETE: Delete Route: len 192, priority 3, table 0, if# 9, name vlan4, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
10.200.240.1 link#9 00:24:81:82:19:6e 10.200.240.46
got message of size 192 on Mon Nov 1 09:16:31 2021
RTM_DELETE: Delete Route: len 192, priority 4, table 0, if# 9, name vlan4, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
10.200.240.0 10.200.240.46 255.255.252.0 00:24:81:82:19:6e 10.200.240.46
got message of size 176 on Mon Nov 1 09:16:31 2021
RTM_DELETE: Delete Route: len 176, priority 1, table 0, if# 9, name vlan4, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
10.200.243.255 10.200.240.46 00:24:81:82:19:6e 10.200.240.46
got message of size 192 on Mon Nov 1 09:16:31 2021
RTM_DELETE: Delete Route: len 192, priority 1, table 0, if# 9, name vlan4, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
10.200.240.46 00:24:81:82:19:6e 00:24:81:82:19:6e 10.200.240.46
got message of size 96 on Mon Nov 1 09:16:31 2021
RTM_DELADDR: address being removed from iface: len 96, if# 9, name vlan4,
metric 0, flags:
sockaddrs:
255.255.252.0 00:24:81:82:19:6e 10.200.240.46 10.200.243.255
got message of size 232 on Mon Nov 1 09:16:31 2021
RTM_DELETE: Delete Route: len 232, priority 8, table 0, if# 9, name vlan4, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
213.75.112.0 10.200.240.1 255.255.248.0 00:24:81:82:19:6e 10.200.240.46
"dhcpleased"
got message of size 176 on Mon Nov 1 09:16:31 2021
RTM_DELETE: Delete Route: len 176, priority 8, table 0, if# 9, name vlan4, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
224.3.2.6 10.200.240.46 00:24:81:82:19:6e 10.200.240.46
* cat /etc/resolv.conf, copy the output into the email.
lookup file bind
nameserver 127.0.0.1
then run dhcpleased with the configuration file:
* run "route -n monitor"
* mv /etc/X.dhcpleased.conf /etc/dhcpleased.conf
* cat /etc/dhcpleased.conf and copy the output into the email
interface vlan4 {
send vendor class id "IPTV_RG"
ignore dns
}
* cat /etc/resolv.conf, copy the output into the email.
lookup file bind
nameserver 127.0.0.1
* restart dhcpleased: doas /etc/rc.d/dhcpleased restart
* copy the output of "route -n monitor" into the email
got message of size 176 on Mon Nov 1 09:19:40 2021
RTM_DELETE: Delete Route: len 176, priority 8, table 0, if# 1, name em0, pid:
0, seq 0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
224.3.2.6 192.168.2.1 00:24:81:82:19:6d 192.168.2.1
got message of size 176 on Mon Nov 1 09:20:05 2021
RTM_ADD: Add Route: len 176, priority 8, table 0, if# 1, name em0, pid: 0, seq
0, errno 0
flags:
fmask:
use: 0 mtu: 0 expire: 0
locks: inits:
sockaddrs:
239.255.255.250 192.168.2.1 00:24:81:82:19:6d 192.168.2.1
got message of size 232 on Mon Nov 1 09:20:49 2021
RTM_PROPOSAL: config proposal: len 232, source dhcp, table 0, if# 9, name
vlan4, pid: 83653, seq 1, errno 0
flags:
fmask:
use: 0 mtu: 0 expire:
