Re: static routes on VLAN on CURRENT

2017-07-02 Thread O. Hartmann
On Sun, 2 Jul 2017 13:17:54 -0700 Freddie Cash wrote: > On Jul 2, 2017 4:40 AM, "Hartmann, O." wrote: > > Fiddling around with a self-brewn router/firewall based on 12-CURRENT > and ipfw, I run into problems when setting up a trunk port with >

Re: static routes on VLAN on CURRENT

2017-07-02 Thread O. Hartmann
On Sun, 2 Jul 2017 21:12:17 +0200 Milan Obuch wrote: > On Sun, 2 Jul 2017 20:13:49 +0200 > "Hartmann, O." wrote: > > > On Sun, 2 Jul 2017 14:39:34 +0200 > > Milan Obuch wrote: > > [ snip ] > > > > > To not use a

Re: static routes on VLAN on CURRENT

2017-07-02 Thread Hartmann, O.
On Sun, 2 Jul 2017 14:39:34 +0200 Milan Obuch wrote: > On Sun, 2 Jul 2017 13:40:01 +0200 > "Hartmann, O." wrote: > > [ snip ] > > > On igb1.2 (vlan tag 2) I want to run an asterisk PBX (that is the > > main goal). The interface is attached with

Re: static routes on VLAN on CURRENT

2017-07-02 Thread Freddie Cash
On Jul 2, 2017 4:40 AM, "Hartmann, O." wrote: Fiddling around with a self-brewn router/firewall based on 12-CURRENT and ipfw, I run into problems when setting up a trunk port with different VLANs and static routes. The "router" has three NICs, igb0, igb1, igb2 (it is de

Re: static routes on VLAN on CURRENT

2017-07-02 Thread Milan Obuch
On Sun, 2 Jul 2017 20:13:49 +0200 "Hartmann, O." wrote: > On Sun, 2 Jul 2017 14:39:34 +0200 > Milan Obuch wrote: [ snip ] > > > To not use a routing daemon due to the small size of my network, I > > > desided to use static routes, in rc.conf I

Re: static routes on VLAN on CURRENT

2017-07-02 Thread Milan Obuch
On Sun, 2 Jul 2017 13:40:01 +0200 "Hartmann, O." wrote: [ snip ] > On igb1.2 (vlan tag 2) I want to run an asterisk PBX (that is the main > goal). The interface is attached with the IP 192.168.2.1. The NIX is > attached to a VLAN capable switch and VLAN 2 is for VoIP

static routes on VLAN on CURRENT

2017-07-02 Thread Hartmann, O.
Fiddling around with a self-brewn router/firewall based on 12-CURRENT and ipfw, I run into problems when setting up a trunk port with different VLANs and static routes. The "router" has three NICs, igb0, igb1, igb2 (it is de facto an APU 2C4 from PCengines). igb0 is attached to an external VDSL2+

dtc files in gnu/usr.bin

2017-07-02 Thread Bjoern A. Zeeb
Hi, at the end of a universe run I have the following files in my src tree which don’t belong there: ? gnu/usr.bin/dtc/.depend ? gnu/usr.bin/dtc/dtc ? gnu/usr.bin/dtc/dtc-lexer.lex.c ? gnu/usr.bin/dtc/dtc-parser.tab.c ? gnu/usr.bin/dtc/dtc-parser.tab.h ?

BROKEN: svn commit: r320528 - in head/sys: amd64/include arm/arm arm/include arm64/arm64 arm64/include dev/aac dev/aacraid dev/bnxt dev/cxgb dev/cxgb/ulp/iw_cxgb dev/hyperv/storvsc dev/mfi dev/tsec d

2017-07-02 Thread Mark Millard
[On second thought: the build should not be depending on /usr/include/machine/* . And using installworld to indirectly update /usr/include/machine/* did not fix the problem by itself. I still had to also delete /usr/obj/amd64_clang/amd64.amd64/usr/src/sys/* in order for buildkernel to work.] On

META MODE BROKEN: svn commit: r320528 - in head/sys: amd64/include arm/arm arm/include arm64/arm64 arm64/include dev/aac dev/aacraid dev/bnxt dev/cxgb dev/cxgb/ulp/iw_cxgb dev/hyperv/storvsc dev/mfi

2017-07-02 Thread Mark Millard
[Turns out META_MODE did not update /usr/include/machine/* .] On 2017-Jul-2, at 12:43 AM, Mark Millard wrote: > I attempted to jump from head -r320482 to -r320570 for amd64 > but the kernel build fails with massive numbers of things like: > > > I'll note that, for example, aac_disk.o was

BROKEN: svn commit: r320528 - in head/sys: amd64/include arm/arm arm/include arm64/arm64 arm64/include dev/aac dev/aacraid dev/bnxt dev/cxgb dev/cxgb/ulp/iw_cxgb dev/hyperv/storvsc dev/mfi dev/tsec d

2017-07-02 Thread Mark Millard
I attempted to jump from head -r320482 to -r320570 for amd64 but the kernel build fails with massive numbers of things like: I'll note that, for example, aac_disk.o was rebuilt: --- all_subdir_aac --- Building