Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #260881 > unrolled thread

setting up network with a hosts file, but your way

Back to article view | Back to linux.debian.user

Contents

  setting up network with a hosts file, but your way gene heskett <gheskett@shentel.net> - 2023-08-12 20:50 +0200
    Re: setting up network with a hosts file, but your way Greg Wooledge <greg@wooledge.org> - 2023-08-12 21:30 +0200
      Re: setting up network with a hosts file, but your way gene heskett <gheskett@shentel.net> - 2023-08-12 22:10 +0200
        Re: setting up network with a hosts file, but your way Greg Wooledge <greg@wooledge.org> - 2023-08-12 23:40 +0200
          Was: setting up network q, now no x gene heskett <gheskett@shentel.net> - 2023-08-13 00:40 +0200
            Re: Was: setting up network q, now no x Greg Wooledge <greg@wooledge.org> - 2023-08-13 01:10 +0200
              Re: Was: setting up network q, now no x gene heskett <gheskett@shentel.net> - 2023-08-13 13:30 +0200
                Kiauh - setting up an ARM based single board computer for 3d printing "Andrew M.A. Cater" <amacater@einval.com> - 2023-08-13 17:10 +0200
                  Re: Kiauh - setting up an ARM based single board computer for 3d  printing gene heskett <gheskett@shentel.net> - 2023-08-13 20:30 +0200
      Re: setting up network with a hosts file, but your way gene heskett <gheskett@shentel.net> - 2023-08-12 22:50 +0200
    Re: setting up network with a hosts file, but your way zithro <slack@rabbit.lu> - 2023-08-14 18:10 +0200
      Re: setting up network with a hosts file, but your way gene heskett <gheskett@shentel.net> - 2023-08-14 21:40 +0200
        Re: setting up network with a hosts file, but your way Brian <ad44@cityscape.co.uk> - 2023-08-14 22:10 +0200

#260881 — setting up network with a hosts file, but your way

I am bringing up a new bananapi-m5, an arm64 device. You don't like my 
way, and have made that boringly plain.

It is booted to a text screen as root, first boot.

Already edited the /etc/hostname, and /etc/hosts files.  The next thing 
from what I see, is a total lack of a route address which s/b 
192.168.71.1. First run made me set both pw's, but never ran N-M.

ipv6:
There is no ipv6 service within 100 miles, so I should set a /proc 
command to kill ipv6, so whats the official syntax? for that.

ipv4:
ip a returns both interfaces data, local looks legit, shows both 
addresses but no ipv4 is listed in the eth0 section. ipv6 is all bogus, 
all commented out in the hosts file.

hosts file resolution works, showing the correct ipv4 addresses
when I try to ping one of those other local machines.

ip r returns a null.

networkctl reports neither interface is managed.
systemd-networkd says its not installed, suggesting using apt to install 
it, but w/o a net, how?

Network-Manager is not present in /bin.

So what is the next step?

Thanks.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [next] | [standalone]

#260885

On Sat, Aug 12, 2023 at 02:49:25PM -0400, gene heskett wrote:
> I am bringing up a new bananapi-m5, an arm64 device. You don't like my way,
> and have made that boringly plain.

Gene.  Please stop saying things like this.  The use of traditional static
addressing without DNS is a common and well-supported configuration.

People do it ALL THE TIME.  It's extremely simple.

> Already edited the /etc/hostname

Good.  This is where your hostname goes.  Your hostname can either be
"short" (no dots), or "long" (with dots).

> and /etc/hosts files.

Also good.  Your hostname should resolve either to your static IP
address, or to 127.0.1.1.  Either way is fine.

> ipv6:
> There is no ipv6 service within 100 miles, so I should set a /proc command
> to kill ipv6, so whats the official syntax? for that.

Do nothing.  Do not touch anything with "ipv6" in its name at all.

> ipv4:

Step one: determine the NAME of your ethernet interface.

Step two: edit /etc/network/interfaces to bring up this interface with
your desired IP address, netmask, and gateway.  If there's a running
DHCP client daemon (because the installer set it up for DHCP instead
of static addressing), you may need to kill that daemon.  Or, if you're
especially clever, you can bring the interface DOWN, BEFORE editing
the file, which will kill the daemon cleanly.  Most people forget this
step, so they just end up killing the daemon later, with "kill" or
by rebooting.

Step three: edit /etc/resolv.conf to set up DNS resolution for outside
hosts, if you intend to use the Internet.

Here's a sample /etc/network/interfaces file:

====================================================
source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet static
    address 10.0.0.7/24
    gateway 10.0.0.1
====================================================

Here's a sample /etc/resolv.conf file:

====================================================
search coyote.den
nameserver 1.1.1.1
====================================================

Of course, if you're running a local recursive DNS nameserver, you would
put "nameserver 127.0.0.1".  Or you might use your ISP's nameserver, or
a recursive nameserver elsewhere on your network.  Use whatever's correct
for your setup.

Finally, here's a sample /etc/hosts file:

====================================================
127.0.0.1   localhost
::1         localhost ip6-localhost ip6-loopback
ff02::1     ip6-allnodes
ff02::2     ip6-allrouters

10.0.0.7    banana1.coyote.den banana1
10.0.0.8    printer.coyote.den printer
10.0.0.19   raspberry1.coyote.den raspberry1
====================================================

Make sure the output of "hostname", which should match the contents of
your /etc/hostname file, matches one of the lines in this file.

And that's the entire thing!  Do not touch anything else.

[toc] | [prev] | [next] | [standalone]

#260886

On 8/12/23 15:27, Greg Wooledge wrote:
> On Sat, Aug 12, 2023 at 02:49:25PM -0400, gene heskett wrote:
>> I am bringing up a new bananapi-m5, an arm64 device. You don't like my way,
>> and have made that boringly plain.
> 
> Gene.  Please stop saying things like this.  The use of traditional static
> addressing without DNS is a common and well-supported configuration.
> 
> People do it ALL THE TIME.  It's extremely simple.
> 
>> Already edited the /etc/hostname
> 
> Good.  This is where your hostname goes.  Your hostname can either be
> "short" (no dots), or "long" (with dots).
> 
>> and /etc/hosts files.
> 
> Also good.  Your hostname should resolve either to your static IP
> address, or to 127.0.1.1.  Either way is fine.
> 
>> ipv6:
>> There is no ipv6 service within 100 miles, so I should set a /proc command
>> to kill ipv6, so whats the official syntax? for that.
> 
> Do nothing.  Do not touch anything with "ipv6" in its name at all.
> 
>> ipv4:
> 
> Step one: determine the NAME of your ethernet interface.

eth0


> Step two: edit /etc/network/interfaces to bring up this interface with
> your desired IP address, netmask, and gateway.  If there's a running
> DHCP client daemon (because the installer set it up for DHCP instead
> of static addressing), you may need to kill that daemon.  Or, if you're
> especially clever, you can bring the interface DOWN, BEFORE editing
> the file, which will kill the daemon cleanly.  Most people forget this
> step, so they just end up killing the daemon later, with "kill" or
> by rebooting.

interface had lo already
added
iface eth0 inet static
address 192.168.71.55
gateway 192.168.71.2

correct? editor saved to do resolv.conf next

That daemons name?
> 
> Step three: edit /etc/resolv.conf to set up DNS resolution for outside
> hosts, if you intend to use the Internet.
> 
> Here's a sample /etc/network/interfaces file:
> 
> ====================================================
> source /etc/network/interfaces.d/*
> 
> auto lo
> iface lo inet loopback
> 
> auto enp2s0
> iface enp2s0 inet static
>      address 10.0.0.7/24
>      gateway 10.0.0.1
> ====================================================
> 
> Here's a sample /etc/resolv.conf file:
> 
> ====================================================
> search coyote.den
> nameserver 1.1.1.1
I use my router @192.168.71.1 as a nameserver relay
saved that, restarted /etc/init.d/networking. got good ipv4 address for 
ip a but no route by ip r.

next?
> ====================================================
> 
> Of course, if you're running a local recursive DNS nameserver, you would
> put "nameserver 127.0.0.1".  Or you might use your ISP's nameserver, or
> a recursive nameserver elsewhere on your network.  Use whatever's correct
> for your setup.
> 
> Finally, here's a sample /etc/hosts file:

eth0

> ====================================================
> 127.0.0.1   localhost
> ::1         localhost ip6-localhost ip6-loopback
> ff02::1     ip6-allnodes
> ff02::2     ip6-allrouters
> 
> 10.0.0.7    banana1.coyote.den banana1
> 10.0.0.8    printer.coyote.den printer
> 10.0.0.19   raspberry1.coyote.den raspberry1
> ====================================================
> 
> Make sure the output of "hostname", which should match the contents of
> your /etc/hostname file, matches one of the lines in this file.
> 
> And that's the entire thing!  Do not touch anything else.

It all matches, but no route for ip r.
> .

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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#260889

On Sat, Aug 12, 2023 at 04:01:49PM -0400, gene heskett wrote:
> > Step one: determine the NAME of your ethernet interface.
> 
> eth0
> 
> 
> > Step two: edit /etc/network/interfaces to bring up this interface with
> > your desired IP address, netmask, and gateway.  If there's a running
> > DHCP client daemon (because the installer set it up for DHCP instead
> > of static addressing), you may need to kill that daemon.  Or, if you're
> > especially clever, you can bring the interface DOWN, BEFORE editing
> > the file, which will kill the daemon cleanly.  Most people forget this
> > step, so they just end up killing the daemon later, with "kill" or
> > by rebooting.
> 
> interface had lo already
> added
> iface eth0 inet static
> address 192.168.71.55
> gateway 192.168.71.2
> 
> correct? editor saved to do resolv.conf next

You're missing "auto eth0".

Are you sure your router's address ends with .2?  Usually networks are
set up with the router at .1.  It's not required, of course.  But it's
unusual for it not to be.

> That daemons name?

How the heck would we know?  You're not running Debian.

ps -ef | grep -i dhc

That should cover variants of names like "dhclient" or "dhcpcd".  I guess
"pump" is also a possibility, but I don't think anyone has used pump in
many years.

Or you could just reboot to ensure it dies.

[toc] | [prev] | [next] | [standalone]

#260892 — Was: setting up network q, now no x

On 8/12/23 17:32, Greg Wooledge wrote:
> On Sat, Aug 12, 2023 at 04:01:49PM -0400, gene heskett wrote:
>>> Step one: determine the NAME of your ethernet interface.
>>
>> eth0
>>
>>
>>> Step two: edit /etc/network/interfaces to bring up this interface with
>>> your desired IP address, netmask, and gateway.  If there's a running
>>> DHCP client daemon (because the installer set it up for DHCP instead
>>> of static addressing), you may need to kill that daemon.  Or, if you're
>>> especially clever, you can bring the interface DOWN, BEFORE editing
>>> the file, which will kill the daemon cleanly.  Most people forget this
>>> step, so they just end up killing the daemon later, with "kill" or
>>> by rebooting.
>>
>> interface had lo already
>> added
>> iface eth0 inet static
>> address 192.168.71.55
>> gateway 192.168.71.2
>>
>> correct? editor saved to do resolv.conf next
> 
> You're missing "auto eth0".
> 
No, I just didn't show it, auto is valid for whatever comes later, so 
"auto lo eth0" is as good as it gets.  And I've no clue where the 1 
turned into a 2. its 1 and works.

> Are you sure your router's address ends with .2?  Usually networks are
> set up with the router at .1.  It's not required, of course.  But it's
> unusual for it not to be.
> 
>> That daemons name?
> 
> How the heck would we know?  You're not running Debian.
> 
> ps -ef | grep -i dhc
> 
> That should cover variants of names like "dhclient" or "dhcpcd".  I guess
> "pump" is also a possibility, but I don't think anyone has used pump in
> many years.
> 
> Or you could just reboot to ensure it dies.

It's good over several reboots.

Now the problem is no X.  I used apt to install gnome which was nearly 
800 packages of gnome, & which failed majorly on mcollective and its 
pluggins (whatever the heck that is, no man pages for it and apt cannot 
now remove them either,) the underlying dpkg is having a cow.  Of the 
top pkg managers, only aptitude will run but that thing has totally 
destroyed my system 4 times over the last decade and change by not 
showing me what it was going to do first. So I don't trust aptitude to 
take the period off the end of a sentence.

Apparently x11 has been totally replaced by xwayland, and xwayland will 
not allow a package manager to run as root. There is probably a 
workaround I'm not acquainted with, so I'm DIW and sinking.

I have another bpi running this same jammy and have had no such problems.

Thanks Greg.

I need X running so I can use firefox to go get and build the rest of 
the software I am building this thing to run.

Next?
> .

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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#260894 — Re: Was: setting up network q, now no x

On Sat, Aug 12, 2023 at 06:37:30PM -0400, gene heskett wrote:
> I need X running so I can use firefox to go get and build the rest of the
> software I am building this thing to run.

Then why on earth are you installing a full Desktop Environment?

If you need to use Firefox to obtain files and then compile them, then
what you need are xorg, firefox-esr, build-essential, and some kind of
simple window manager.  twm would suffice, or fvwm, or whatever you're
comfortable with.  Hell, in theory you could skip the window manager and
just run "startx firefox" or something.  You'd be limited to a single
browser window, but that's not a crippling limitation.

Or, as an alternative, you could obtain the files from another machine,
and copy them over.  Then you only need build-essential, and NONE of the
rest.

(For a given value of "build", of course.  You may need other development
tools beyond build-essential, but we can't advise you on that without more
information.)

I would absolutely NOT install GNOME unless you need it for something
more than just launching a web browser.

[toc] | [prev] | [next] | [standalone]

#260906 — Re: Was: setting up network q, now no x

On 8/12/23 19:07, Greg Wooledge wrote:
> On Sat, Aug 12, 2023 at 06:37:30PM -0400, gene heskett wrote:
>> I need X running so I can use firefox to go get and build the rest of the
>> software I am building this thing to run.
> 
> Then why on earth are you installing a full Desktop Environment?
> 
> If you need to use Firefox to obtain files and then compile them, then
> what you need are xorg, firefox-esr, build-essential, and some kind of
> simple window manager.  twm would suffice, or fvwm, or whatever you're
> comfortable with.  Hell, in theory you could skip the window manager and
> just run "startx firefox" or something.  You'd be limited to a single
> browser window, but that's not a crippling limitation.

Today I'll copy off the net changes, rewrite its sd card with the iso 
and restore the net changes b4 putting the sd card back in the bpi. From 
there I'll install ff, nginx, build-essential, + dhelper maybe and see 
if that pulls in what it needs thru those deps.  Unless you know an even 
better way. build-essential will likely be needed for kiauh.

> Or, as an alternative, you could obtain the files from another machine,
> and copy them over.  Then you only need build-essential, and NONE of the
> rest.
> 
This kit of utils to run a printer is far superior to octoprint, 
installed and maintained by kiauh, needs a full time X and FF to control 
the printer. It a 2-way web server using nginx to run the printer and 
display it. From that install, I can watch the printer and control it, 
from anyplace on my local net. The default browser armbian uses is 
chromium, but chromium has hijacked port 80 for google adv bs so 
chromium doesn't work but FF.esr does. https to 8080 works, http to 80 
doesn't. Googles hunger for your data knows no limits. We need another 
Judge Green.

> (For a given value of "build", of course.  You may need other development
> tools beyond build-essential, but we can't advise you on that without more
> information.)
> 

Maybe this helps...

> I would absolutely NOT install GNOME unless you need it for something
> more than just launching a web browser.
> 
> .
Pulling in nearly 800 pkgs triple underscores that point.
synaptic must also run.

Thanks Greg.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#260912 — Kiauh - setting up an ARM based single board computer for 3d printing

Gene,

A little bit more information in each post would help a whole lot here.

For others following along at home this saga is unclear: for others, here's
my attempted summary:

The ARM machines
================

Gene has a network of small ARM SBCs. They're not Raspberry Pi's, they're
one of the somewhat similar range of OrangePis. Over a period of years,
he's had Intel machines, Raspberry Pi machines, Orange Pis either running
heavy machinery like lathes (see threads on linuxcnc) or now 3D printers.

The Armbian OS
==============
These run Armbian, not vanilla Debian. Armbian is similar, but the impetus
behind the project is to get unsupported boards supported using a vendor's
BSP (board support package) enough to then add Debian packages

Armbian as a project is extremely useful but extremely limited: they barely
have enough time to compe with the huge numbers of boards now in circulation
and insufficient developers. They don't have enough for user support on a 
regular basis.

Using small ARM SBCs - 3D printing
==================================
>From what I can see, Gene has several of the OrangePi boards, each running
a 3D printer.

Package selection
=================
Gene has some some definite preferences in package selection: synaptic
as a graphical tool for package selection rather than apt-get, apt or aptitude
and he will sometimes blame the tools for somehow messing up the packages he
wants to install.

Risk appetite
=============
Unlike some others on the list, he's happy to be an experimentalist and to
run third party tools and all in one packages like Appimages and Flatpaks
if they serve his purpose. He's also prepared to build things from random
sources. In this, he's prepared to be on the very definite bleeding edge
and sometimes suffers for it :)

kiauh https://github.com/th33xitus/kiauh
=====

This is from a Github repository. It is a script, [Klipper Installation And
Update Helper] to pull together an SD card image and various applications
to produce an integrated environment for 3D printing.

Requirements: Raspbian Lite or equivalent small environment. It can be
run on Ubuntu Jammy - the site itself notes that it has some installations
run on Armbian but the status of support is unknown.

Essentially, it pulls in a base list of Debian packages then lots of third
party repositories to provide the functionality.

Takeaways
=========
>From this: Gene, I think you need to start from something really minimal:
I'd suggest you have a look at which packages are in Rasbian Lite and attempt
to emulate that.

Debian with no graphics environment and standard packages might be enough to
bootstrap it - so no initial need for X or Firefox or Chromium.
That means working on the command line - but that's what tasksel and apt
are designed for.

An approach?
============

Write stuff down so you can explain it. Buid a list of steps.
The first step is probably to set up a minimal system and get it networked.

You've already had discussions on how to do this: if all else fails, I 
suggest you look at Gunnar Wolf's advice on Debian Raspberry Pi images and
how he set up /etc/network/interfaces from the outset.

Don't just run kiauh without understanding what the scripts are doing, at least
in outline.

Don't attempt to second guess the script maintainer and try and build your
own that's better until you *REALLY* know how it's meant to work using 
the unmodified script. If needs be, dig up a Raspberry Pi to do it once the way
it's been done previously.

*Do* report back to the kiauh script maintainer what you've needed to do
to get it to work on Armbian.

Once you've got one SD card, you can potentially just duplicate it for 
all of the machines and do a minimal edit set thereafter.

It doesn't look as if you need a web browser on each machine: if you set
up nginx on each to talk to a different network port, you can probably 
cycle around them all and control from one machine.

Oh - and use meaningful subject lines. If need be "kiauh - step one - networking" so that those of us who are interested might help rather than being left in
the dark.

All best, as ever,

Andy Cater

[toc] | [prev] | [next] | [standalone]

#260917 — Re: Kiauh - setting up an ARM based single board computer for 3d printing

On 8/13/23 11:07, Andrew M.A. Cater wrote:
> Gene,
> 
> A little bit more information in each post would help a whole lot here.
> 
> For others following along at home this saga is unclear: for others, here's
> my attempted summary:
> 
> The ARM machines
> ================
> 
> Gene has a network of small ARM SBCs. They're not Raspberry Pi's, they're
> one of the somewhat similar range of OrangePis. 

Only have one orange pi. Still unpowered as its equ to a rpi3b, not fast 
enough to do the job. So I'm running an rpi4b to run my big lathe, and a 
bunch (6 so far) of bananapi-m5's to run 3d printers, essentially a 
slightly faster rpi4b w/o the rpi's radio, but  with 16Gb of emmc memory 
the kernel does not see.  The rest of them are old Dell dimensions with 
i5 brains and have been for as long as wheezy's been around.

Over a period of years,
> he's had Intel machines, Raspberry Pi machines, Orange Pis either running
> heavy machinery like lathes (see threads on linuxcnc) or now 3D printers.
> 
> The Armbian OS
> ==============
> These run Armbian, not vanilla Debian. Armbian is similar, but the impetus
> behind the project is to get unsupported boards supported using a vendor's
> BSP (board support package) enough to then add Debian packages

Correct but armbian can give a full desktop. as can raspiOS.

> Armbian as a project is extremely useful but extremely limited: they barely
> have enough time to compe with the huge numbers of boards now in circulation
> and insufficient developers. They don't have enough for user support on a
> regular basis.

This is also true to the extent I'm tempted to contribute to the beer fund.

> Using small ARM SBCs - 3D printing
> ==================================
>>From what I can see, Gene has several of the OrangePi boards, each running
> a 3D printer.
Never happened. bpi's work great.
> 
> Package selection
> =================
> Gene has some some definite preferences in package selection: synaptic
> as a graphical tool for package selection rather than apt-get, apt or aptitude
> and he will sometimes blame the tools for somehow messing up the packages he
> wants to install.
Another untruth, I'm scared of only aptitude, its destroyed 4 installs 
for me by deleting everything in sight.
> 
> Risk appetite
> =============
> Unlike some others on the list, he's happy to be an experimentalist and to
> run third party tools and all in one packages like Appimages and Flatpaks
> if they serve his purpose. He's also prepared to build things from random
> sources. In this, he's prepared to be on the very definite bleeding edge
> and sometimes suffers for it :)

For everyones enlightenment, at an age of 88 that you all imagine as 
drowning in my breakfast cereal bowl:

Mother did gave me one thing, an IQ that raises eyebrows when I'm 
tested, like the Iowa test in '46 of 147, AFQT in 1952, my 8th grade 
education at that point made a 98 and got me 4F'd. 10 years later I 
walked into a testing session for FCC licenses and passed a 1st phone 
exam w/o cracking a book, another 10 years later I sat for the CET, and 
got 123 of 125 correct w/o a books help. I wasn't impressed with the 
college prof administering the test which was 4 hours long, when he was 
amazed I was done in 45 minutes, he was dubious, laying the answer 
stencil on my sheets and seeing a sea of black raised his eyebrows, he 
had been teaching a course based on electronics for 5 years and I, who 
had just walked in the door with a 20 dollar bill for the test was the 
first to pass it. But I'm fading with age, failing the mensa test about 
6 years back. I explained to the FCC in the 1970's, the distortion in 
the signal that a klystron amplfier does timewise to the NTSC signal, 
using relativity's effect on the mass of the electron as the cause of 
it. We can correct that now or digital tv would not work, but we 
couldn't then i the late '70's.. I helped build the cameras in the later 
'50's that went down 37,000 feet in the mohole. You've, if old enough, 
seen pix in the encyclopedias taken where external water pressure was 
around 18,000 psi. I've seen pix taken with those 2 cameras that prove 
water IS compressible. It just takes an unimaginable amount of psi. I've 
been there, and done that, places many of you would not believe, and 
I've had fun learning about it. Been asked to remove my shoes during 
physicals by parameds who'd been told I probably have webbed feet cuz I 
have walked on water electronically, often enough I use WOWElectronics 
as a business name.

Now I readily admit I'm having trouble keeping up, but I'll try till I 
miss roll call, its in my genes.

So take care and stay well everybody.
> 
> kiauh https://github.com/th33xitus/kiauh
> =====
> 
> This is from a Github repository. It is a script, [Klipper Installation And
> Update Helper] to pull together an SD card image and various applications
> to produce an integrated environment for 3D printing.
> 
> Requirements: Raspbian Lite or equivalent small environment. It can be
> run on Ubuntu Jammy - the site itself notes that it has some installations
> run on Armbian but the status of support is unknown.
> 
> Essentially, it pulls in a base list of Debian packages then lots of third
> party repositories to provide the functionality.
> 
> Takeaways
> =========
>>From this: Gene, I think you need to start from something really minimal:
> I'd suggest you have a look at which packages are in Rasbian Lite and attempt
> to emulate that.
> 
> Debian with no graphics environment and standard packages might be enough to
> bootstrap it - so no initial need for X or Firefox or Chromium.
> That means working on the command line - but that's what tasksel and apt
> are designed for.
> 
> An approach?
> ============
> 
> Write stuff down so you can explain it. Buid a list of steps.
> The first step is probably to set up a minimal system and get it networked.
> 
> You've already had discussions on how to do this: if all else fails, I
> suggest you look at Gunnar Wolf's advice on Debian Raspberry Pi images and
> how he set up /etc/network/interfaces from the outset.
> 
> Don't just run kiauh without understanding what the scripts are doing, at least
> in outline.
> 
> Don't attempt to second guess the script maintainer and try and build your
> own that's better until you *REALLY* know how it's meant to work using
> the unmodified script. If needs be, dig up a Raspberry Pi to do it once the way
> it's been done previously.
> 
> *Do* report back to the kiauh script maintainer what you've needed to do
> to get it to work on Armbian.
> 
> Once you've got one SD card, you can potentially just duplicate it for
> all of the machines and do a minimal edit set thereafter.
> 
> It doesn't look as if you need a web browser on each machine: if you set
> up nginx on each to talk to a different network port, you can probably
> cycle around them all and control from one machine.
> 
> Oh - and use meaningful subject lines. If need be "kiauh - step one - networking" so that those of us who are interested might help rather than being left in
> the dark.
> 
> All best, as ever,
> 
> Andy Cater
> 
> .

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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#260887

On 8/12/23 15:27, Greg Wooledge wrote:
> On Sat, Aug 12, 2023 at 02:49:25PM -0400, gene heskett wrote:
>> I am bringing up a new bananapi-m5, an arm64 device. You don't like my way,
>> and have made that boringly plain.
> 
> Gene.  Please stop saying things like this.  The use of traditional static
> addressing without DNS is a common and well-supported configuration.
> 
> People do it ALL THE TIME.  It's extremely simple.
> 
>> Already edited the /etc/hostname
> 
> Good.  This is where your hostname goes.  Your hostname can either be
> "short" (no dots), or "long" (with dots).
> 
>> and /etc/hosts files.
> 
> Also good.  Your hostname should resolve either to your static IP
> address, or to 127.0.1.1.  Either way is fine.
> 
>> ipv6:
>> There is no ipv6 service within 100 miles, so I should set a /proc command
>> to kill ipv6, so whats the official syntax? for that.
> 
> Do nothing.  Do not touch anything with "ipv6" in its name at all.
> 
>> ipv4:
> 
> Step one: determine the NAME of your ethernet interface.
> 
> Step two: edit /etc/network/interfaces to bring up this interface with
> your desired IP address, netmask, and gateway.  If there's a running
> DHCP client daemon (because the installer set it up for DHCP instead
> of static addressing), you may need to kill that daemon.  Or, if you're
> especially clever, you can bring the interface DOWN, BEFORE editing
> the file, which will kill the daemon cleanly.  Most people forget this
> step, so they just end up killing the daemon later, with "kill" or
> by rebooting.
> 
> Step three: edit /etc/resolv.conf to set up DNS resolution for outside
> hosts, if you intend to use the Internet.
> 
> Here's a sample /etc/network/interfaces file:
> 
> ====================================================
> source /etc/network/interfaces.d/*
> 
> auto lo
> iface lo inet loopback
> 
> auto enp2s0
> iface enp2s0 inet static
>      address 10.0.0.7/24
>      gateway 10.0.0.1
> ====================================================
> 
> Here's a sample /etc/resolv.conf file:
> 
> ====================================================
> search coyote.den
> nameserver 1.1.1.1
> ====================================================
> 
> Of course, if you're running a local recursive DNS nameserver, you would
> put "nameserver 127.0.0.1".  Or you might use your ISP's nameserver, or
> a recursive nameserver elsewhere on your network.  Use whatever's correct
> for your setup.
> 
> Finally, here's a sample /etc/hosts file:
> 
> ====================================================
> 127.0.0.1   localhost
> ::1         localhost ip6-localhost ip6-loopback
> ff02::1     ip6-allnodes
> ff02::2     ip6-allrouters
> 
> 10.0.0.7    banana1.coyote.den banana1
> 10.0.0.8    printer.coyote.den printer
> 10.0.0.19   raspberry1.coyote.den raspberry1
> ====================================================
> 
> Make sure the output of "hostname", which should match the contents of
> your /etc/hostname file, matches one of the lines in this file.
> 
> And that's the entire thing!  Do not touch anything else.
> 
Nvr mind, strange mini keyboard, fixed typu, works.
Update of 92 pkgs in progress. need to shrink text screen about 1 row of 
chars. can't see bottom of text screen on cheap tv w/computer input.. 
Not worth fixing if the gui works. That is not the monitor it will be 
using when operational, a week or so hence. I am building a 3d printer 
from scratch, using an Ender 5 plus frame.

Next is a gui, gnome will work, klipper doesn't care, haven't tried 
startx yet.. So sw is about 25% done.

Now, other than killing ipv6 this is exactly what I'm been doing that 
I've been berated for. The only diff I've seen so far is that now I 
don't see the "#created by network mangler" in this /etc/resolv.conf. 
So we'll see if it survives a reboot. If resolv.conf does not survive a 
reboot, the magic chattr +i gets pulled out and used again.

Thanks Greg.

> .

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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#260932

On 12 Aug 2023 20:49, gene heskett wrote:
> ipv6:
> There is no ipv6 service within 100 miles, so I should set a /proc 
> command to kill ipv6, so whats the official syntax? for that.

I don't know if there is another method, I'll give you mine, which 
consists in telling the kernel to completely disable IPv6, in the kernel 
command line.

Edit "/etc/default/grub", on the line "GRUB_CMDLINE_LINUX" (or 
"GRUB_CMDLINE_LINUX_DEFAULT", depending on your config), add :

   ipv6.disable=1

Don't forget to run "update-grub", then reboot.

If it worked, you will find in the syslog :
"IPv6: Loaded, but administratively disabled, reboot required to enable".

If you're not using GRUB, you will have to find where kernel options 
should be entered (also called kernel command line).

-- 
++
zithro / Cyril

[toc] | [prev] | [next] | [standalone]

#260939

On 8/14/23 12:04, zithro wrote:
> On 12 Aug 2023 20:49, gene heskett wrote:
>> ipv6:
>> There is no ipv6 service within 100 miles, so I should set a /proc 
>> command to kill ipv6, so whats the official syntax? for that.
> 
> I don't know if there is another method, I'll give you mine, which 
> consists in telling the kernel to completely disable IPv6, in the kernel 
> command line.
> 
> Edit "/etc/default/grub", on the line "GRUB_CMDLINE_LINUX" (or 
> "GRUB_CMDLINE_LINUX_DEFAULT", depending on your config), add :
> 
>    ipv6.disable=1
> 
> Don't forget to run "update-grub", then reboot.
> 
> If it worked, you will find in the syslog :
> "IPv6: Loaded, but administratively disabled, reboot required to enable".
> 
> If you're not using GRUB, you will have to find where kernel options 
> should be entered (also called kernel command line).
> 
Thanks zithro, but it appears that it is no longer needed, just follow 
Gregs recipe and it works.

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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#260940

On Mon 14 Aug 2023 at 15:36:10 -0400, gene heskett wrote:

> On 8/14/23 12:04, zithro wrote:
> > On 12 Aug 2023 20:49, gene heskett wrote:
> > > ipv6:
> > > There is no ipv6 service within 100 miles, so I should set a /proc
> > > command to kill ipv6, so whats the official syntax? for that.
> > 
> > I don't know if there is another method, I'll give you mine, which
> > consists in telling the kernel to completely disable IPv6, in the kernel
> > command line.
> > 
> > Edit "/etc/default/grub", on the line "GRUB_CMDLINE_LINUX" (or
> > "GRUB_CMDLINE_LINUX_DEFAULT", depending on your config), add :
> > 
> >    ipv6.disable=1
> > 
> > Don't forget to run "update-grub", then reboot.
> > 
> > If it worked, you will find in the syslog :
> > "IPv6: Loaded, but administratively disabled, reboot required to enable".
> > 
> > If you're not using GRUB, you will have to find where kernel options
> > should be entered (also called kernel command line).
> > 
> Thanks zithro, but it appears that it is no longer needed, just follow Gregs
> recipe and it works.

Happy days! Due to to the help you requested and received we will never
again be plagued by any of your previous self-inflicted network issues ;).

-- 
Brian.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web