out cat /etc/resolv.conf
for f in $(find /etc/network -type f)
do
[[ -f "$f" ]] && [[ "$(file "$f")" =~ text ]] && out cat "$f";
done
echo
echo "All data saved to $REPORT_FILE."
# End of File
-=-=-=-=-
regards,
David
----
&& [[ "$(file "$f")" =~ text ]] && out cat "$f";
done
echo
echo "All data saved to $REPORT_FILE."
# End of File
-=-=-=-=-
regards,
David
-Original Message-
>From: Christopher Barry
>Sent: Jul 12, 2018 11:36 PM
>To: debi
On Friday 13 July 2018 14:43:43 Mark Morgan Lloyd wrote:
> On 13/07/18 15:15, Gene Heskett wrote:
> > On Friday 13 July 2018 10:49:10 Mark Morgan Lloyd wrote:
> >> Yes, and route (and ifconfig etc.) is obsolete. But still sometimes
> >> useful.
> >
> > And will probably continue to be usefull as
On 13/07/18 15:15, Gene Heskett wrote:
On Friday 13 July 2018 10:49:10 Mark Morgan Lloyd wrote:
Yes, and route (and ifconfig etc.) is obsolete. But still sometimes
useful.
And will probably continue to be usefull as long as the man pages for ip
and friends continue to suck dead toads thru
On Friday 13 July 2018 10:49:10 Mark Morgan Lloyd wrote:
> >> And the last automatic updates were done on the 7th June- correct?
> >> Much stuff that I do these days is based on RPIs which don't use an
> >> initrd, but I had to go through this on a PC a few weeks ago after
> >> I'd moved some
And the last automatic updates were done on the 7th June- correct?
Much stuff that I do these days is based on RPIs which don't use an
initrd, but I had to go through this on a PC a few weeks ago after I'd
moved some discs around: the old configuration was still stuck in the
fstab file loaded
Well, nobody did give you the answer in the end because you have a unique
perspective on the problem.
Sent from my Motorola XT1527
On Fri, Jul 13, 2018, 10:27 AM Gene Heskett wrote:
> On Friday 13 July 2018 10:09:30 Mark Morgan Lloyd wrote:
>
> > On 13/07/18 13:45, Gene Heskett wrote:
> > > On
On Friday 13 July 2018 10:09:30 Mark Morgan Lloyd wrote:
> On 13/07/18 13:45, Gene Heskett wrote:
> > On Friday 13 July 2018 05:08:57 Mark Morgan Lloyd wrote:
> >> On 13/07/18 02:00, Gene Heskett wrote:
> >>> Thats a direct copy/paste, so whats wrong with that. Other than
> >>> the fact that its
On 13/07/18 13:45, Gene Heskett wrote:
On Friday 13 July 2018 05:08:57 Mark Morgan Lloyd wrote:
On 13/07/18 02:00, Gene Heskett wrote:
Thats a direct copy/paste, so whats wrong with that. Other than the
fact that its been rebooted twice since the address was changed from
192.168.71.2 to the
On Friday 13 July 2018 05:08:57 Mark Morgan Lloyd wrote:
> On 13/07/18 02:00, Gene Heskett wrote:
> > Thats a direct copy/paste, so whats wrong with that. Other than the
> > fact that its been rebooted twice since the address was changed from
> > 192.168.71.2 to the 11 you see above, but
If it's taking gw as an address something's in the wrong field.
Sent from my Motorola XT1527
On Fri, Jul 13, 2018, 9:29 AM Gene Heskett wrote:
> On Friday 13 July 2018 05:11:29 John Paul Adrian Glaubitz wrote:
>
> > On 07/13/2018 11:02 AM, Christian Knoke wrote:
> > > Gene Heskett schrieb am
On Friday 13 July 2018 07:01:58 Alan Corey wrote:
> Try ping 8.8.8.8
> It's a Google-run nameserver but it's handy to have an outside IP to
> ping if you're having trouble looking up names. I use it as a second
> nameserver.
root@rock64:/etc/network# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84)
On Friday 13 July 2018 05:11:29 John Paul Adrian Glaubitz wrote:
> On 07/13/2018 11:02 AM, Christian Knoke wrote:
> > Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
> >> On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> >>> follow the below 5 steps for help solving this.
> >>>
> >>>
On 07/13/2018 01:21 PM, Mark Morgan Lloyd wrote:
> On 13/07/18 09:15, John Paul Adrian Glaubitz wrote:
>
>> Or, alternatively: Set up systemd-networkd and systemd-resolved and don't
>> waste endless amounts of time and energy to get this mess fixed which is
>> bash-script-based network
On 13/07/18 09:15, John Paul Adrian Glaubitz wrote:
Or, alternatively: Set up systemd-networkd and systemd-resolved and don't
waste endless amounts of time and energy to get this mess fixed which is
bash-script-based network initialization.
..which is something that those of us who are
Try ping 8.8.8.8
It's a Google-run nameserver but it's handy to have an outside IP to ping
if you're having trouble looking up names. I use it as a second nameserver.
Sent from my Motorola XT1527
On Fri, Jul 13, 2018, 5:32 AM Gene Heskett wrote:
> On Friday 13 July 2018 05:02:26 Christian
On Friday 13 July 2018 05:02:26 Christian Knoke wrote:
> Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
> > On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> > > follow the below 5 steps for help solving this.
> > >
> > > [...]
> > > for f in $(find /etc/network -type f); do
> > >
On 07/13/2018 11:02 AM, Christian Knoke wrote:
> Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
>> On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
>
>>> follow the below 5 steps for help solving this.
>
>>> [...]
>>> for f in $(find /etc/network -type f); do
>>> [[ -f ${f} &&
On 13/07/18 02:00, Gene Heskett wrote:
Thats a direct copy/paste, so whats wrong with that. Other than the fact
that its been rebooted twice since the address was changed from
192.168.71.2 to the 11 you see above, but ifconfig still says its on
71.2 right now. So where the heck is it getting
Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
> On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> > follow the below 5 steps for help solving this.
> > [...]
> > for f in $(find /etc/network -type f); do
> > [[ -f ${f} && "$(file "${f}")" =~ text ]] && {
> > out cat "${f}"
> >
On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> On Thu, 12 Jul 2018 21:52:13 -0400
>
> Gene Heskett wrote:
> >On Thursday 12 July 2018 18:04:54 Christian Knoke wrote:
> >> Du schriebst am 12. Jul um 16:57 Uhr:
> >> > On Thursday 12 July 2018 14:16:43 Christian Knoke wrote:
> >> > >
On Thu, 12 Jul 2018 21:52:13 -0400
Gene Heskett wrote:
>On Thursday 12 July 2018 18:04:54 Christian Knoke wrote:
>
>> Du schriebst am 12. Jul um 16:57 Uhr:
>> > On Thursday 12 July 2018 14:16:43 Christian Knoke wrote:
>> > > Gene Heskett schrieb am 12. Jul um 10:07 Uhr:
>> > >
>> > > hth
On Thursday 12 July 2018 18:04:54 Christian Knoke wrote:
> Du schriebst am 12. Jul um 16:57 Uhr:
> > On Thursday 12 July 2018 14:16:43 Christian Knoke wrote:
> > > Gene Heskett schrieb am 12. Jul um 10:07 Uhr:
> > >
> > > hth
> >
> > Not yet. If I can't fix this tomorrow, I'll write another sd
Du schriebst am 12. Jul um 16:57 Uhr:
> On Thursday 12 July 2018 14:16:43 Christian Knoke wrote:
> > Gene Heskett schrieb am 12. Jul um 10:07 Uhr:
> > hth
>
> Not yet. If I can't fix this tomorrow, I'll write another sd card with
> the original files. It worked until an update 2 or 3 weeks
On Thursday 12 July 2018 13:27:20 Mark Morgan Lloyd wrote:
> On 12/07/18 05:00, Gene Heskett wrote:
> > Greetings;
> >
> > I have been playing the 10k monkeys scene trying to figure out how
> > to add a gateway entry to the route -n report on a rock64 with a
> > stretch/xfce install on it.
> >
>
On Thursday 12 July 2018 14:16:43 Christian Knoke wrote:
> Hello,
>
> Gene Heskett schrieb am 12. Jul um 10:07 Uhr:
> > > > auto eth0
> > > > allow-hotplug eth0
> > > > iface eth0 inet static
> > > > address 192.168.71.2
> > > > netmask 255.255.255.0
> > > > gateway 192.168.71.1
> > > >
Hello,
Gene Heskett schrieb am 12. Jul um 10:07 Uhr:
> > > auto eth0
> > > allow-hotplug eth0
> > > iface eth0 inet static
> > > address 192.168.71.2
> > > netmask 255.255.255.0
> > > gateway 192.168.71.1
> > > dns-nameserver 192.168.71.1
> I've even changed the eth0 devices address, but once
On 12/07/18 05:00, Gene Heskett wrote:
Greetings;
I have been playing the 10k monkeys scene trying to figure out how to add
a gateway entry to the route -n report on a rock64 with a stretch/xfce
install on it.
Where does this assignment belong in a static defined eth0 configuration?
I know
On Thursday 12 July 2018 08:50:26 Alan Corey wrote:
> Yeah, I wasn't saying anything because I couldn't remember. I think
> Debian puts it there. Try the interfaces man page.
>
> There's also a route command. Maybe iproute too. Something like
> route add 192.168.43.1 gw
> (or gateway or default
On Thursday 12 July 2018 07:22:03 Christian Knoke wrote:
> Gene Haskett schrieb am 12. Jul um 00:13 Uhr:
> > I have been playing the 10k monkeys scene trying to figure out how
> > to add a gateway entry to the route -n report on a rock64 with a
> > stretch/xfce install on it.
> >
> > The obvious
Yeah, I wasn't saying anything because I couldn't remember. I think Debian
puts it there. Try the interfaces man page.
There's also a route command. Maybe iproute too. Something like
route add 192.168.43.1 gw
(or gateway or default instead of gw).
On a command line. There's a routing table, and
Gene Haskett schrieb am 12. Jul um 00:13 Uhr:
> I have been playing the 10k monkeys scene trying to figure out how to add
> a gateway entry to the route -n report on a rock64 with a stretch/xfce
> install on it.
> The obvious (to me that is) place would be
> in /etc/network/interfaces.d/eth0,
Greetings;
I have been playing the 10k monkeys scene trying to figure out how to add
a gateway entry to the route -n report on a rock64 with a stretch/xfce
install on it.
Where does this assignment belong in a static defined eth0 configuration?
I know several places where it doesn't work, but
33 matches
Mail list logo
