b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Mundy" <mark.mundy@draeger.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Error - mac address of the ping destination could not be resolved and is not a bat-host name
Date: Fri, 09 Jun 2023 18:55:24 -0000	[thread overview]
Message-ID: <168633692419.986.3016729917435716783@diktynna.open-mesh.org> (raw)
In-Reply-To: <8229391.T7Z3S40VBb@ripper>

Thanks for your reply, Sven. Comments inline below

Sven Eckelmann wrote:
> On Thursday, 8 June 2023 22:38:23 CEST mark.mundy@draeger.com wrote:

If I read your message correctly, the bridging of interfaces may make my original question moot. If I am wrong about that, I will go back to your original answer. 

> If it should be a transparent bridge between mesh without IP routing then 
> please add bat0+eth1 in the same bridge. And then configure the IP address on 
> top of the bridge.

I think I understand this to mean that I should remove the ipaddress, netmask configuration items from the bat0 interface, and create a bridge with bat0 and eth1. Something more like this for 10.1.1.1, and similar changes for 10.2.1.1 where it is actually the bridge interface that contains holds the IP address info

# new configuration file 
# /etc/network/interfaces for 10.1.1.1
#
source-directory /etc/network/interfaces.d

allow-hotplug eth0
auto eth0
iface eth0 inet dhcp

allow hotplug eth1
auto eth1
iface eth1 inet static
        address 10.1.1.1
        netmask 255.0.0.0
        gateway 10.0.0.1
#        dns-nameservers 1.1.1.1 8.8.8.8 8.8.4.4

allow hotplug bat0
auto bat0
iface bat0 inet manual          <-- changed from static
#        address 10.2.1.4
#        netmask 255.0.0.0
        up ip link set up dev $IFACE
        pre-up ip link set up dev wlan0
        pre-up iw dev wlan0 del
        pre-up iw phy phy0 interface add wlan0 type mesh
        pre-up iw dev wlan0 set channel 149 80MHz
        pre-up ip link set up dev wlan0
        pre-up iw dev wlan0 mesh join mesh149
        pre-up batctl if add wlan0
        pre-up batctl if add eth1
        down ip link set down dev $IFACE
        batman-adv-bridge yes
        batman-adv-mesh-id bat0
        batman-adv-multicast-mode 1
        batman-adv-ttl 50
        batman-adv-originator-ttl 50
        batman-adv-gateway-mode server
        batman-adv-hard-interface wlan0
        batman-adv-hard-interface eth1

allow hotplug br0
auto br0
iface br0 inet static
        address 10.2.1.4
        netmask 255.0.0.0
        bridge_ports eth1 bat0



> Kind regards,
>     Sven

  reply	other threads:[~2023-06-09 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 20:38 Error - mac address of the ping destination could not be resolved and is not a bat-host name mark.mundy
2023-06-09 12:10 ` Sven Eckelmann
2023-06-09 18:55   ` Mark Mundy [this message]
2023-06-10 10:09     ` Sven Eckelmann
2023-06-29 16:13       ` Mark Mundy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=168633692419.986.3016729917435716783@diktynna.open-mesh.org \
    --to=mark.mundy@draeger.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).