On Sat, 5 Jul 2025 08:48:31 -0400
David Niklas via Dng <dng@???> wrote:
> On Sat, 5 Jul 2025 08:29:46 +0200
> tito <farmatito@???> wrote:
> > On Fri, 4 Jul 2025 22:16:48 -0400
> > David Niklas via Dng <dng@???> wrote:
> >
> > > On Fri, 4 Jul 2025 21:34:38 -0400
> > > David Niklas <deference@???> wrote:
> > >
> > > > On Fri, 04 Jul 2025 03:22:12 -0400
> > > > "Greg Olsen" <dng@???> wrote:
> > > > > On Fri, Jul 4, 2025, at 3:10 AM, Ralph Ronnquist via Dng wrote:
> > > > >
> > > > > > On Fri, Jul 04, 2025 at 12:26:35AM -0400, David Niklas via Dng
> > > > > > wrote:
> > > > > > > Hello,
> > > > > > > I just installed Devuan Daedalus. It connected to the net just
> > > > > > > fine, but after installing a bunch of packages (too many to
> > > > > > > count), I rebooted the system and the network is not brought
> > > > > > > up correctly.
> > > > > > >
> > > > > > > I compared my current sysinit list of services to the new
> > > > > > > systems and there isn't really anything standing out. I found
> > > > > > > /etc/init.d/network was not executable. When I made it so and
> > > > > > > after re-executed it as root (/etc/init.d/network start), I
> > > > > > > have full networking. This is repeatable across reboots.
> > > > > >
> > > > > > I have note found "/etc/init.d/network" in any debian package.
> > > > > > Where does that come from?
> > > > > >
> > > > > > Though the problem is most likely due to avahi-autoipd, and I'm
> > > > > > sure you will be much happier having purged that one.
> > > > > >
> > > > > > Ralph
> > > > > >
> > > > > /etc/init.d/network is incorrect.
> > > > >
> > > > > Correct name is: /etc/init.d/networking
> > > > >
> > > > > # dpkg -S /etc/init.d/networking
> > > > > ifupdown: /etc/init.d/networking
> > > > >
> > > > > Cheers,
> > > > > Greg
> > > > >
> > > >
> > > > Hello,
> > > > You're correct, it's networking, not network.
> > > >
> > > > I uninstalled avahi-autoipd. The situation has not changed.
> > > >
> > > > SteveT, this is a desktop PC, so and I have a static IP set for it.
> > > > The PC does have an address assigned to it. But route -n gives
> > > > nothing:
> > > >
> > > > % sudo route -n
> > > > Kernel IP routing table
> > > > Destination Gateway Genmask Flags Metric Ref
> > > > Use Iface
> > > > %
> > > >
> > > > Thanks,
> > > > David
> > >
> > > Hello,
> > > Testing a little further I have found out that I can't access the
> > > outside world even after running /etc/init.d/networking again. I can
> > > only ping devices on my LAN. Everything else just says the network is
> > > unreachable. Including regular tools like apt install.
> > >
> > > Thanks again,
> > > David
> > Hi,
> > can you ping the outside networks by ip e.g.:
> >
> > ping 139.178.84.217
> >
> > instead of
> >
> > ping kernel.org
> >
> > Are there any nameservers configured in /etc/resolv.conf e.g.:
> >
> > nameserver 8.8.8.8
> > nameserver 8.8.4.4
> >
> > Is your gateway configure correctly?
> >
> > Ciao,
> > Tito
> >
>
> Hello,
> I cannot ping 8.8.8.8 from the newly installed machine. The old machine
> (Devuan ASCII), connected to the same router and switch, is able to ping
> anything including 8.8.8.8.
> I really can't think of what could be wrong. I'm beginning to wonder if
> the firewall, which I did not setup, was modified by one of the
> firewall/security packages (E.G. nftables). But that would be weird.
>
> Thanks,
> David
Did the interfaces' name change? Are there more then one interface?
I would definitely check in that direction.
Ciao,
Tito
P.S.: I can recommend:
arno-iptables-firewall
easy to setup, reliable, well maintained.
I run my routers on it.
Ciao,
Tito
::
Re: [DNG] New install. Network is n…
