Re: need sd card backup on r-pi-3b
On Sunday 24 September 2017 07:39:34 Alan Corey wrote:
> There isn't some limit on number of machines that can connect coming
> from somewhere? Could be political/economic or technical. I see wifi
> routers advertised as only working with n clients.
>
I think its been found, but no clue how to fix. According to route -n,
no gateway is being assigned, and of course its not going to get out
of my local network w/o it.
root@rock64Sheldon:/etc/network/interfaces.d# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 202 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 202 0 0 eth0
192.168.71.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
(
But, the assignment is there in /etc/network/interfaces.d/eth0:
=================
allow-hotplug eth0
auto eth0
iface eth0 inet static
address 192.168.71.2/24
gateway 192.168.71.1
==================
So wth am I doing wrong, or have I found a bug?
Thanks Alan.
> Sent from my Motorola XT1505
> On Sep 24, 2017 4:35 AM, "Mark Morgan Lloyd" <
>
> markMLl.debian-arm@telemetry.co.uk> wrote:
> > On 23/09/17 20:00, Gene Heskett wrote:
> >
> > So my local network is working as expected. BUT:
> >> root@rock64:/etc# ping -c1 yahoo.com
> >> PING yahoo.com (98.138.253.109) 56(84) bytes of data.
> >> From 192.168.71.2 (192.168.71.2) icmp_seq=1 Destination Host
> >> Unreachable
> >>
> >> Note that the dns request did resolve.
> >>
> >> But my dns requests are probably being answered by dnsmasq in the
> >> router. I cannot find anything in the routers copious settings
> >> (it's DD-WRT) that would prevent a connection, but it refuses to
> >> pass. I've tried several ipv4 addresses in that 192,168.nn block.
> >> No other machines, 5 more, on this local net are being denied
> >> network access.
> >>
> >> Ideas? I'm nearly out of hair. But its been slowly thinning for 82+
> >> years too so I can't blame it on this too loudly.
> >
> > I've only run Stretch briefly so far, in the context of trying to
> > find out whether USB boot worked (patchy, but might have been a
> > power issue).
> >
> > I'd suggest checking using traceroute -I and then looking at
> > route -n and/or ip route ls which should give you a bit more of an
> > indication of what's going on. IME this sort of thing is usually
> > because the router isn't NATting the entire 192.168.x.x range.
> >
> > --
> > Mark Morgan Lloyd
> > markMLl .AT. telemetry.co .DOT. uk
> >
> > [Opinions above are the author's, not those of his employers or
> > colleagues]
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: