On Mon, Mar 21, 2016 at 07:50:43AM -0700, Shohrukh Shoyoqubov wrote: > On Mon, Mar 21, 2016 at 6:25 AM, Sebastian Benoit <be...@openbsd.org> wrote: > > > Shohrukh Shoyoqubov(mau...@shohrukh.com) on 2016.03.17 15:10:22 -0700: > > > I cannot observe the booting process right now since I don't have > > physical > > > access to the machine. I will try to access it tonight. > > > > You can look at "dmesg -s" in that case. > > > > Automatic boot in progress: starting file system checks. > /dev/sd0a (be4971db3e5f3b2f.a): file system is clean; not checking > setting tty flags > pf enabled > net.inet.ip.forwarding: 0 -> 1 > net.inet.ip.ifq.maxlen: 256 -> 1024 > starting network > add host 192.168.1.26: gateway 10.10.10.13 ^^^^^^^^^^^^^^^^^^^^^ Is it this that's breaking things?
You were mentioning that you have a non-trunk setup, are you playing routing tricks there, too? But I don't understand why the interface is shown as running. It might be time for some printf debugging... > starting early daemons: syslogd pflogd ntpd. > starting RPC daemons:. > savecore: /dev/sd0b: Device not configured > checking quotas: done. > clearing /tmp > kern.securelevel: 0 -> 1 > creating runtime link editor directory cache. > preserving editor files. > starting network daemons: sshd ospfd sndiod. > starting local daemons: cron. > Thu Feb 18 20:58:49 TJT 2016 -- I'm not entirely sure you are real.
