inline

On Sun, Mar 23, 2025 at 10:30 PM Philipp Buehler
<e1c1bac6253dc54a1e89ddc046585...@posteo.net> wrote:
>
> Am 24.03.2025 00:24 schrieb Diana Eichert:
> > Am I missing something or is this the only way to automatically bring
> > up a pair(4) patch?
> >
> > find /etc -name '*.pair*' -print -exec cat {} \;
> > /etc/hostname.pair0
> > rdomain 0
>
> > group pair
> > lladdr 00:00:C0:44:44:00
>
> group and lladdr is optional

yep, just thought I'd post the entire file.  I have a weird quirk
where I set lladdr on network interfaces to Western Digital OUI
values, allows me to look at network device cam tables for my
systems.

> > inet 10.1.1.0/31
> > up
> up is implied when setting inet/inet6

yep, I was part of a thread on @tech where this was discussed.  To
many years in network engineer where you explicitly bring an
interface / port online.

> > /etc/hostname.pair44
> > rdomain 44
> > group pair
> > patch pair0
>
> this is the key line to "patch" those two together

yep, the "issue" is the order interfaces are brought up, pair0
comes up first, but I can't put "patch pair44" in that config
because pair44 isn't up yet.  I realize "patch pair44" isn't
required, it is an artifact from the typo that took 6 days to
discover.

> > lladdr 00:00:C0:44:00:44
> > inet 10.1.1.1/31
> > up
> > !ifconfig pair0 patch pair44
>
> and the above would just do the same again as 'patch pair0'
>
> > !route -q -T 0 add -inet 44.31.83.0/24 10.1.1.1
>
> So not much to reduce - yet that extra !ifconfig could be painful when
> you start changing things inconsistently
> --
> pb

yep, I should remove "!ifconfig pair0 patch pair44" from
/etc/hostname.pair44 .  Because I want the route added when the pair
comes up I have to be aware of consistent destroy / add interfaces.

thanks for your input,

diana

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Reply via email to