search

JonStratton / mesh-micro

Just a Simple Batman-adv Shell script that can also make a Node a Gateway
GNU General Public License v3.0
0 stars 0 forks source link

Is there something wrong with my Settings? Why is the network disconnected! #1

Closed shaozhai closed 2 years ago

shaozhai commented 2 years ago

![Uploading IMG_20220322_160815.jpg…]() ![Uploading IMG_20220322_155057.jpg…]() Is there something wrong with my Settings? Why is the network disconnected!

JonStratton commented 2 years ago

I cant see whatever screenshots you posted. If you want me to help looking at something, start by pasting the text content of "ip a". If you have more than one of these running, also run "sudo batctl n".

shaozhai commented 2 years ago

16480017697702499563990981753105

shaozhai commented 2 years ago

16480018339485018946283749019856

shaozhai commented 2 years ago

16480019022713060766208157011944

JonStratton commented 2 years ago

Yes, that looks correct. The host with the Ethernet connection("Server") has an IP address of 192.168.200.1 on bat0. "bat n" shows that both computers are connected in a mesh. So they are meshed, there might be something else going on with the IPs or the bridging to the internet.

On the computer without the Ethernet connection("Client"), you should also run "ip a". You should see a "192.168.200.??" IP address for the bat0 interface. This means that the Server is acting as a DHCP server for the Client. If not, run "dhclient bat0" on the Client and see if it gets an IP address thats in the "192.168.200.??" range.

If that is the case, you should be able to ping the Server from the Client ("ping 192.168.200.1"). Finally, if the connection is good, you should be able to ping the internet from the Client ("ping 8.8.8.8").

shaozhai commented 2 years ago

IMG_20220324_175312 IMG_20220324_175412 IMG_20220324_175447 Conf file mesh-micro.conf is not found in /etc/dnsmasq.d. Eth0 does not have an IP address. Bat0 has IP address 169.254.11.173

JonStratton commented 2 years ago

It looks like "iptables" was missing from the base install. This may have caused the "client" to not get a dhcp lease from the server. You can probably correct this on the "server" without reinstalling by running "apt-get install iptables" and then rebooting.

Let me know if this doesn't fix your issue. And thanks for the heads up.

shaozhai commented 2 years ago

root@rock3a:~# apt-get install iptables Reading package lists... Done Building dependency tree... Done Reading state information... Done iptables is already the newest version (1.8.7-1ubuntu2). 0 upgraded, 0 newly installed, 0 to remove and 60 not upgraded.

shaozhai commented 2 years ago

Upgrade and the problem is still there