C inline
On Sun, Feb 24, 2019 at 1:11 PM Reindl Harald <h.reindl at thelounge.net>
wrote:
>
>
> sounds like your startup ordering is broken
>
>
Yep sounds like a fair assessment. If only I could get QNAP to agree with
that, I have only been at it for 3-4 months or so. It takes them about
1-2 years before they fix things like the dns forwarder issue where it
pointed back to itself.
> make sure whatever is responsible for setup the bridge is started before
> every other network service
>
>
I wish I knew what was responsible. its a terd party device... errr.... I
mean third party device.... well maybe I was correct the first time. I am
trying to reverse engineer the configs to figure out how this thing is
broken... again.
> on the other hand it makes no sense that eth0 and eth1 have a ip at all,
> that belongs to the bridge and nothing else
>
Well it does as it is configured and allowed by the deivce. I fix them at
eth0/192.168.1.2 and eth1/192.168.1.3 due to the device using DHCP server
in VM. I also set nameservers on eth0 as it is only allowed on that device
to the devices itself 192.168.1.2 and the google 8.8.8.8 so it can find
itself other machines on network and outside world with GW at 192.168.1.1
(router). That bit has been working since they decided to set forwarder to
secondary DNS setting of eth0 and not machine itself 192.168.1.2. There is
a Virtual network that consists of the two hard line actual ports, Virt
Network for VMs, and Virt Network for Containers. Web server also runs on
the device. All is accessible (when it works) from inside VMs/Contianers
and outside machines (outside devices via eth1/2) connected on switch.
When it does'nt well the whole network is down... name server and all.
>
> that's an example how a proper bridge is configured and my
> "network-up.service" is part of "network-online.target"
while evry other
> service has "After=network-online.target" *and*
> "Requires=network-online.target"
>
I am certain based on my experience that what I have is not "proper"
by any
stretch of the imagination. I am certain this device starts by eating it's
jello desert with the salad fork and belches every 10 seconds.
I have a DHCP server running in a VM as the device DHCP server is for the
birds. Dodo birds I think.. Does not allow even the simple things like
static assign by MAC address.
I'll look for a network-up.service or similar to see if I can fish out
either a fixed startup sequence or a magic 8 ball startup script.....
whatever they have implemented.
Is there a juju-bad-naughty black list for egregious implementors of SAMBA
that end of up giving it a bad name?
>
> ExecStart=-/usr/sbin/ip link add name br-lan type bridge
> ExecStart=-/usr/sbin/ip link set dev br-lan up
> ExecStart=-/usr/sbin/ip a add 192.168.2.2/255.255.255.0 broadcast
> 192.168.2.255 dev br-lan
> ExecStart=-/usr/sbin/ip link set dev lan-spare1 master br-lan up
> ExecStart=-/usr/sbin/ip link set dev lan-spare2 master br-lan up
> ExecStart=-/usr/sbin/ip link set dev lan-tv master br-lan up
> ExecStart=-/usr/sbin/ip link set dev poe-spare master br-lan up
> ExecStart=-/usr/sbin/ip link set dev poe-phone master br-lan up
>