On 25/09/17 14:30, Gene Heskett wrote:
On Monday 25 September 2017 05:15:36 Mark Morgan Lloyd wrote:
I believe lo is now inserted automatically.
Its not mentioned as a builtin in the debian handbook pdf, I read the
networking section yesterday looking for clues. I've another machine
about 3
On Monday 25 September 2017 05:15:36 Mark Morgan Lloyd wrote:
> On 25/09/17 03:15, Gene Heskett wrote:
> > On Sunday 24 September 2017 17:50:22 Alan Corey wrote:
> >> Try putting your static route in interfaces, in the eth0 section
> >> with an up, like
> >>
> >> iface eth0 inet static
> >>
On 25/09/17 03:15, Gene Heskett wrote:
On Sunday 24 September 2017 17:50:22 Alan Corey wrote:
Try putting your static route in interfaces, in the eth0 section with
an up, like
iface eth0 inet static
address 192.168.71.3/24
netmask 255.255.255.0
up route add default gw
I was just thinking of how waiting for wifi to connect hangs my pis
booting. Times out at 1 minute 20 seconds or so. If the interface
was supposed to be connected to the router to be considered to be up
that could be a problem.
lo is loopback, 127.0.0.1, always points to the machine you're on.
On Sunday 24 September 2017 17:50:22 Alan Corey wrote:
> Try putting your static route in interfaces, in the eth0 section with
> an up, like
>
> iface eth0 inet static
> address 192.168.71.3/24
> netmask 255.255.255.0
> up route add default gw 192.168.71.1
>
> I think post-up might be
Try putting your static route in interfaces, in the eth0 section with
an up, like
iface eth0 inet static
address 192.168.71.3/24
netmask 255.255.255.0
up route add default gw 192.168.71.1
I think post-up might be too late, maybe there's a pre-up.
On 9/24/17, Gene Heskett
On Sunday 24 September 2017 16:20:31 Mark Morgan Lloyd wrote:
> On 24/09/17 19:45, Gene Heskett wrote:
> >>> I wouldn't put the manual route command in rc.local, I'd put it in
> >>> the network interface definition as in
> >>>
> >>> allow-hotplug eth0
> >>> iface eth0 inet static
> >>>
On 24/09/17 19:45, Gene Heskett wrote:
I wouldn't put the manual route command in rc.local, I'd put it in
the network interface definition as in
allow-hotplug eth0
iface eth0 inet static
address 172.27.200.5/24
post-up route add default gw 172.27.200.1 dev eth0 metric 0
pre-down
On Sunday 24 September 2017 14:08:25 Gene Heskett wrote:
> On Sunday 24 September 2017 13:43:20 Mark Morgan Lloyd wrote:
> > On 24/09/17 16:30, Gene Heskett wrote:
> > > On Sunday 24 September 2017 11:59:57 Alan Corey wrote:
> > >> But what's the purpose of having the gateway fields in interfaces
On Sunday 24 September 2017 13:43:20 Mark Morgan Lloyd wrote:
> On 24/09/17 16:30, Gene Heskett wrote:
> > On Sunday 24 September 2017 11:59:57 Alan Corey wrote:
> >> But what's the purpose of having the gateway fields in interfaces
> >> if not to to be reliant on the routing table?
> >>
> >> But
On 24/09/17 16:30, Gene Heskett wrote:
On Sunday 24 September 2017 11:59:57 Alan Corey wrote:
But what's the purpose of having the gateway fields in interfaces if
not to to be reliant on the routing table?
But it's worth a shot, something like
route add default gw 192.168.71.1
That was it!
On Sunday 24 September 2017 12:36:41 Alan Corey wrote:
> Try obconf from openbox, I have 4 workspaces on my hp laptop done with
> that. I think it's LXDE. They survive reboots for me.
>
This is on the pi? Humm, not found on it either. I'll need to install it?
Thanks Alan.
Cheers, Gene Heskett
On Sunday 24 September 2017 12:26:49 Alan Corey wrote:
> So this is on the rock64 or one of your pis? I thought the rock64 was
> too experimental to be able to use apt. Raspbian or Debian?
>
Once I had a network, apt on the rock64 runs fine. installed sd card
image is:
Try obconf from openbox, I have 4 workspaces on my hp laptop done with
that. I think it's LXDE. They survive reboots for me.
On 9/24/17, Alan Corey wrote:
> So this is on the rock64 or one of your pis? I thought the rock64 was
> too experimental to be able to use apt.
So this is on the rock64 or one of your pis? I thought the rock64 was
too experimental to be able to use apt. Raspbian or Debian?
On 9/24/17, Gene Heskett wrote:
> On Sunday 24 September 2017 11:59:57 Alan Corey wrote:
>
>> But what's the purpose of having the gateway
On Sunday 24 September 2017 11:59:57 Alan Corey wrote:
> But what's the purpose of having the gateway fields in interfaces if
> not to to be reliant on the routing table?
>
> But it's worth a shot, something like
> route add default gw 192.168.71.1
That was it!
Now I've used apt to update 5
But what's the purpose of having the gateway fields in interfaces if
not to to be reliant on the routing table?
But it's worth a shot, something like
route add default gw 192.168.71.1
It's simple enough to undo it with
route del default
to take it back out if it doesn't work.
I dunno, I haven't
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
On Sunday 24 September 2017 04:34:50 Mark Morgan Lloyd wrote:
> On 23/09/17 20:00, Gene Heskett wrote:
> 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
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.
Sent from my Motorola XT1505
On Sep 24, 2017 4:35 AM, "Mark Morgan Lloyd" <
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.
On Sunday 24 September 2017 00:28:34 Alan Corey wrote:
> > I'm out of ideas. And obviously I cannot configure this rock64
> > until the network works.
>
> It sounds like only 1 machine doesn't work, your email got out after
> all.
>
> > and 4 other wheezy machines work as expected thru this
>
>
> I'm out of ideas. And obviously I cannot configure this rock64 until the
> network works.
It sounds like only 1 machine doesn't work, your email got out after all.
> and 4 other wheezy machines work as expected thru this
So the rock64 has a chance of working.
You don't have something
On Saturday 23 September 2017 20:28:08 Alan Corey wrote:
> "Destination Host Unreachable" doesn't mean it didn't resolve, it can
> mean a cable's unplugged or your netmask isn't right or in this case
> it's not getting outside your LAN for whatever reason. Try pinging an
> outside IP like
"Destination Host Unreachable" doesn't mean it didn't resolve, it can
mean a cable's unplugged or your netmask isn't right or in this case
it's not getting outside your LAN for whatever reason. Try pinging an
outside IP like 8.8.8.8 (a public Google DNS server). Ping and dns
lookup are 2
On Saturday 23 September 2017 13:28:51 Mark Morgan Lloyd wrote:
> On 23/09/17 16:45, Gene Heskett wrote:
> > On Saturday 23 September 2017 12:26:23 Mark Morgan Lloyd wrote:
> >> On 23/09/17 15:00, Gene Heskett wrote:
> I've never had problems with dd provided that the USB->SDcard
>
On 23/09/17 16:45, Gene Heskett wrote:
On Saturday 23 September 2017 12:26:23 Mark Morgan Lloyd wrote:
On 23/09/17 15:00, Gene Heskett wrote:
I've never had problems with dd provided that the USB->SDcard
adapter's OK: what command are you using?
The usual syntax:
dd if=somefile bs=512
On Saturday 23 September 2017 12:26:23 Mark Morgan Lloyd wrote:
> On 23/09/17 15:00, Gene Heskett wrote:
> >> I've never had problems with dd provided that the USB->SDcard
> >> adapter's OK: what command are you using?
> >
> > The usual syntax:
> > dd if=somefile bs=512 of=somedevice, and in the
On 23/09/17 15:00, Gene Heskett wrote:
I've never had problems with dd provided that the USB->SDcard
adapter's OK: what command are you using?
The usual syntax:
dd if=somefile bs=512 of=somedevice, and in the case of sd card copying,
Tell us the /exact/ command you're using.
since no 2
Last first, your fstab and your /boot/cmdline.txt have to be pointing
to the partition you want to boot. Those were the only changes I had
to make when I picloned my sd to my hard drive. By default they point
to /dev/mmcblk0, change them to something like /dev/sda. The ones on
the hard drive.
On Fri, 2017-09-22 at 22:07 -0400, Gene Heskett wrote:
> Greetings;
>
> Trying to dd a copy of the micro-sd card the pi-3b is booting from, to
> another micro-sd card in a usb reader/writer, and winding up with
> nothing but an empty lost+found directory on it.
>
> Obviously some sort of a
On Saturday 23 September 2017 10:58:47 Gene Heskett wrote:
> On Saturday 23 September 2017 07:43:14 Jonathan Wilson wrote:
> > On Fri, 2017-09-22 at 22:07 -0400, Gene Heskett wrote:
> > > Greetings;
> > >
> > > Trying to dd a copy of the micro-sd card the pi-3b is booting
> > > from, to another
On Saturday 23 September 2017 07:43:14 Jonathan Wilson wrote:
> On Fri, 2017-09-22 at 22:07 -0400, Gene Heskett wrote:
> > Greetings;
> >
> > Trying to dd a copy of the micro-sd card the pi-3b is booting from,
> > to another micro-sd card in a usb reader/writer, and winding up with
> > nothing
On Saturday 23 September 2017 04:36:49 Mark Morgan Lloyd wrote:
> On 23/09/17 05:45, Gene Heskett wrote:
> > Months at a time here, but anytime I need to do anything as root
> > that involves more than ncurses graphics, I have to go to the
> > machine and do it there, and its a stand-up job with
On 23/09/17 05:45, Gene Heskett wrote:
Months at a time here, but anytime I need to do anything as root that
involves more than ncurses graphics, I have to go to the machine and do
it there, and its a stand-up job with very poor gfx due to the pi's
In that case investigate what's stopping you
On Saturday 23 September 2017 00:12:11 Alan Corey wrote:
> I don't know, it just works for me. Even over VNC, I just tried it
> from vncviewer on an OpenBSD machine. The "copy from device" is blank
> until I click the down arrow on it, then it finds /dev/mmcblk0. I'm
> running it on the
I don't know, it just works for me. Even over VNC, I just tried it
from vncviewer on an OpenBSD machine. The "copy from device" is blank
until I click the down arrow on it, then it finds /dev/mmcblk0. I'm
running it on the machine that's running tightvncserver which I'm
logged into. I use VNC
On Friday 22 September 2017 22:14:48 Alan Corey wrote:
> I thought piclone was great for that. With a couple manual edits you
> can even clone an sd to a hard drive.
I have never been able to make it work. No helpfull manpage, nor does it
have a help option that I've found other than what you
I thought piclone was great for that. With a couple manual edits you
can even clone an sd to a hard drive.
On 9/22/17, Gene Heskett wrote:
> Greetings;
>
> Trying to dd a copy of the micro-sd card the pi-3b is booting from, to
> another micro-sd card in a usb
Greetings;
Trying to dd a copy of the micro-sd card the pi-3b is booting from, to
another micro-sd card in a usb reader/writer, and winding up with
nothing but an empty lost+found directory on it.
Obviously some sort of a syntax error, but it still takes the pi several
hours to do it, with
40 matches
Mail list logo