On Tue, 17 Sep 2019 02:33:27 -0700 (PDT),
massafrodo@gmail.com declaimed the following:
Hi
I have a BeagleBone Black with a huge Problem
I i flashed the image Debian 9.5 2018-10-07 4GB SD IoT
<https://debian.beagleboard.org/images/bone-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz>
I have one PC in Network 192.168.144.xxx Gateway 192.168.144.254
The Beaglebone is in network 192.168.143.xxx Gateway 192.168.143.254
Just a question: In the old days, 192.168.144.* and 192.168.143.* were
considered to be totally independent Class C networks. You'd need a router
(acting as a gateway) somewhere to cross from one to the other (but...
since the 192.168.*.* range is considered local/private networks, routers
normally do /not/ route them to other local/private nets).
The rest of my comments are musings, since I'm not fully acquainted
with the idiosyncrasies of setting up networks. All my devices use DHCP --
and if an IP needs to be "fixed" that is done in the DHCP router, which is
configured to always provide the same IP # to a host via MAC address (or
hostname -- not sure what that uVerse/Arris router uses).
# The primary network interface
# auto eth0
iface eth0 inet static
address 192.168.143.207
netmask 255.255.255.0
gateway 192.168.143.254
And here your netmask emphasizes that 192.168.144.* and 192.168.143.*
are separate networks.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
I can't ping the BeagleBone from the PC. It is possible to ping the Gateway
in 192.168.143.xxx from PC and Beaglebone.
What IS this gateway machine? Is it configured to route between the two
networks? What does ITS routing table look like?
(see section II, subsection #5)
After booting the BeagleBone, the "route" command shows:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 eth0
default 192.168.143.254 0.0.0.0 UG 0 0 0 eth0
link-local 0.0.0.0 255.255.0.0 U 0 0 0 eth0
192.168.6.0 0.0.0.0 255.255.255.252 U 0 0 0 usb1
192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0
192.168.143.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
There are two default routes!?!?!?!?! WHY?
If i restart the network service, the first default route disappears and i
can successfully ping the Beaglebone from the PC in the 192.168.144 network.
What did i wrong?
Out of curiosity, what does ifconfig show for the eth0 (before and
after your restart of the network)
The use of a static IP could possibly be conflicting with a router
trying to assign a DHCP IP? Or there is some config file defining routes
that you need to modify which is being processed during a cold boot, but
not during a network restart.