On 02/02/2025 21:01, Rainer Dorsch wrote:
root@outdoor:~# cat /etc/network/interfaces
[...]
auto wlan0
Is there a chance that "allow-hotplug wlan0" might help? I use
NetworkManager for WiFi interfaces, so my remarks may have no sense.
Simply ignore them that case. My expectati
On Tue, 2025-02-04 at 07:05 +1100, George at Clug wrote:
> Rainer,
>
> I believe others have responded.
>
> Just for my curiosity, Is Network Manager installed? Would you be
> able to use nmclli to set a static IP address? Or maybe systemctl ?
I was going to respond with something similar yes
George at Clug writes:
> iptables (which I like), nftables (which I ask, Why?)
For a few years now, well, almost a decade, iptables has been a hollow
shell with nftables inside. Why nftables? Because it unifies firewall
for ipv4, ipv6 and bridges, so we don't need to have separate iptables,
ip6t
, it works:
>
> root@outdoor:~# cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
>
> # The loopback network i
On Sun, 02 Feb 2025 15:01:27 +0100
Rainer Dorsch wrote:
>
> I am trying to bringup the wifi network with an ipv4 address on a
> Cubox-i automatically after boot.
>
> Manually, it works:
> [...]
> root@outdoor:~# ifdown wlan0
> [...]
> ifroot@outdoor:~# ifup wlan0
> [...]
> Any hint or advice is
Looks like your firmware is not available. For broadcomm cards there is an
extra installer, which downloads it seperately.
In Debian the firmware is not shipped in the repo, but an installer is
shipped.
Check for any broadcom related packages.
Hope this helps.
Best
Hans
> In the kernel messa
:01 Rainer Dorsch wrote:
Hello,
I am trying to bringup the wifi network with an ipv4 address on a
Cubox-i
automatically after boot.
Manually, it works:
root@outdoor:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate
Hello,
I am trying to bringup the wifi network with an ipv4 address on a Cubox-i
automatically after boot.
Manually, it works:
root@outdoor:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information
Thank you for your mail.
On Wed, Mar 27, 2024 at 12:42 AM Andy Smith wrote:
> On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote:
> > I changed a gateway on a remote site using /etc/network/interfaces by
> > changing gateway. However, at reboot some old gateway IP
Thank you for your quick reply.
On Wed, Mar 27, 2024 at 12:22 AM Henning Follmann
wrote:
> On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote:
> > I changed a gateway on a remote site using /etc/network/interfaces by
> > changing gateway. However, at reboot some
On Tue, Mar 26, 2024 at 11:27 PM Dustin Jenkins wrote:
> On my Debian 12 system, the connman service was helping itself to interfaces,
> including my bridge interfaces that I wanted left alone. Maybe try disabling
> or removing it?
>
> sudo systemctl stop connman
> sudo systemctl disable connma
Thank your for your quick and detailed reply.
On Tue, Mar 26, 2024 at 7:01 PM Greg Wooledge wrote:
> On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote:
> > I changed a gateway on a remote site using /etc/network/interfaces by
> > changing gateway. However, at
On Tue, Mar 26, 2024 at 7:18 PM Pierre-Elliott Bécue wrote:
> As it's a PVE kernel I guess you rely on Proxmox.
> *Theoretically*, Proxmox VE uses /etc/network/interfaces.new to apply
THIS! (OMG why didn't I see this! Thank you!!)
ohh thanks so much for your quick reply, my "machine" indeed is a
Hello,
On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote:
> I changed a gateway on a remote site using /etc/network/interfaces by
> changing gateway. However, at reboot some old gateway IP reappears. I
> really hate when some magic knows better than an explicitly set valu
On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote:
> Hi,
>
> I changed a gateway on a remote site using /etc/network/interfaces by
> changing gateway. However, at reboot some old gateway IP reappears. I
> really hate when some magic knows better than an explicitly se
e cause if your troubles.
--
PEB
Steffen Dettmer wrote on 26/03/2024 at
18:33:42+0100:
> Hi,
>
> I changed a gateway on a remote site using /etc/network/interfaces by
> changing gateway. However, at reboot some old gateway IP reappears. I
> really hate when some magic knows bett
On Tue, Mar 26, 2024 at 06:33:42PM +0100, Steffen Dettmer wrote:
> I changed a gateway on a remote site using /etc/network/interfaces by
> changing gateway. However, at reboot some old gateway IP reappears.
So then the question is *which* of the many different subsystems is in
use to s
ote:
>
> Hi,
>
> I changed a gateway on a remote site using /etc/network/interfaces by
> changing gateway. However, at reboot some old gateway IP reappears. I
> really hate when some magic knows better than an explicitly set value.
> What happens here? How can I get rid of this?
Hi,
I changed a gateway on a remote site using /etc/network/interfaces by
changing gateway. However, at reboot some old gateway IP reappears. I
really hate when some magic knows better than an explicitly set value.
What happens here? How can I get rid of this? It is 100% reproducible.
I have no
On Friday, December 8th, 2023 at 11:23 PM, John Hasler
wrote:
> Mr. Turritopsis Dohrnii Teo En Ming writes:
>
> > You managed to install OpenWRT on an Ubiquiti router?
>
>
> Yes. It was quite straightforward. Instructions on the OpenWRT site.
> --
> John Hasler
> j...@sugarbit.com
> Elmwood,
On Friday, December 8th, 2023 at 11:23 PM, John Hasler
wrote:
> Mr. Turritopsis Dohrnii Teo En Ming writes:
>
> > You managed to install OpenWRT on an Ubiquiti router?
>
>
> Yes. It was quite straightforward. Instructions on the OpenWRT site.
> --
> John Hasler
> j...@sugarbit.com
>
Mr. Turritopsis Dohrnii Teo En Ming writes:
> You managed to install OpenWRT on an Ubiquiti router?
Yes. It was quite straightforward. Instructions on the OpenWRT site.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Friday, December 8th, 2023 at 6:15 AM, John Hasler wrote:
> Turritopsis Dohrnii Teo En Ming wrote:
>
> > UDM Pro runs Debian 11 (bullseye)
>
>
> I have a Ubiquiti router. Before I installed OpenWRT I explored the OS.
> It uses packages from Bullseye but it is certainly not Debian.
On Friday, December 8th, 2023 at 6:08 AM, jeremy ardley
wrote:
> On 7/12/23 23:52, Turritopsis Dohrnii Teo En Ming wrote:
>
> > Subject: Could not find interfaces configuration file
> > /etc/network/interfaces in Debian Linux 11 (bullseye)
>
>
>
&g
On Friday, December 8th, 2023 at 6:05 AM, Andy Smith
wrote:
> Hello,
>
> On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming
> wrote:
>
> > UDM Pro runs Debian 11 (bullseye)
>
>
> I don't think it does. Just because you found a file on the
> filesystem that sa
On Friday, December 8th, 2023 at 12:19 AM, Dan Purgert wrote:
> On Dec 07, 2023, to...@tuxteam.de wrote:
>
> > On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming
> > wrote:
> >
> > [...]
> >
> > > Problem
> > > =
> > >
> > > On 6 Dec 2023, our client d
On Friday, December 8th, 2023 at 12:12 AM, to...@tuxteam.de
wrote:
> On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming
> wrote:
>
> [...]
>
> > Problem
> > =
> >
> > On 6 Dec 2023, our client discovered that their UDM Pro could not perform
> > firmwa
Turritopsis Dohrnii Teo En Ming wrote:
> UDM Pro runs Debian 11 (bullseye)
I have a Ubiquiti router. Before I installed OpenWRT I explored the OS.
It uses packages from Bullseye but it is certainly not Debian. You
couldn't find that file because it isn't there.
--
John Hasler
j...@sugarbit.com
On 7/12/23 23:52, Turritopsis Dohrnii Teo En Ming wrote:
Subject: Could not find interfaces configuration file /etc/network/interfaces
in Debian Linux 11 (bullseye)
You should confirm that the device is actually using that file.
There are at least three different network configuration
Hello,
On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming wrote:
> UDM Pro runs Debian 11 (bullseye)
I don't think it does. Just because you found a file on the
filesystem that says it does, is as trustworthy as the claims in
your email that your client is called Henry Kiss
On Dec 07, 2023, to...@tuxteam.de wrote:
> On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming
> wrote:
>
> [...]
>
> > Problem
> > =
> >
> > On 6 Dec 2023, our client discovered that their UDM Pro could not perform
> > firmware updates automatically. Their UDM Pr
On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming wrote:
[...]
> Problem
> =
>
> On 6 Dec 2023, our client discovered that their UDM Pro could not perform
> firmware updates automatically. Their UDM Pro was running UniFi OS version
> 3.0.20. Client wants to upgr
Subject: Could not find interfaces configuration file /etc/network/interfaces
in Debian Linux 11 (bullseye)
Good day from Singapore,
Background Information
===
Initially our client has a UniFi Dream Machine Pro (UDM Pro) acting as a
firewall and router. Port 9 (WAN1) on
On Tue, Jul 12, 2022 at 10:28 AM Peter Ehlert wrote:
>
> On 7/11/22 21:35, Tixy wrote:
> > On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
> > [...]
> >> I decided to try a fresh netinstall alongside and Boom:
> >>
> >> ===
> >
On Tue 12 Jul 2022 at 15:44:41 (+0100), Tixy wrote:
> Another idea, is looking for that network name in the logs for the
> current boot.
>
> journalctl -b | grep -B3 enx00e04c534458
>
> That'll give you matches with the three lines before so you can see the
> context.
I'd use grep -B3 -A3 -i
On Tue, 2022-07-12 at 05:35 +0100, Tixy wrote:
> On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
> [...]
> >
> > I decided to try a fresh netinstall alongside and Boom:
> >
> > ===
> > multiple network interfaces
> >
> > eno1: Intel Corpor
On 7/11/22 21:35, Tixy wrote:
On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
[...]
I decided to try a fresh netinstall alongside and Boom:
===
multiple network interfaces
eno1: Intel Corporation Ethernet Connection (2) I218-LM
enp5s0: Intel Corporation 1210 Gigabit Network
On Mon, 2022-07-11 at 19:51 -0700, Peter Ehlert wrote:
[...]
>
> I decided to try a fresh netinstall alongside and Boom:
>
> ===
> multiple network interfaces
>
> eno1: Intel Corporation Ethernet Connection (2) I218-LM
> enp5s0: Intel Corporation 1210 Gi
to try a fresh netinstall alongside and Boom:
===
multiple network interfaces
eno1: Intel Corporation Ethernet Connection (2) I218-LM
enp5s0: Intel Corporation 1210 Gigabit Network Connection
enx00e04c534458: Unknown Interface
===
the first two are old hat, I use eno1 and it just works.
bottom
On 2022-06-14 01:48:16, David Wright wrote:
Perhaps calling the new interface naming scheme "predictable" is
somewhat overselling it, but "persistent" (a better choice IMHO)
was already in use, both in the way quoted above, and as one of
the choices for MAC address generation.
The changed nam
On Thu 09 Jun 2022 at 10:42:07 (+0200), Harald Dunkel wrote:
>
> If I have to hardwire the interface names to their Mac address as you
> suggested, then I don't see a significant difference to the old-style
> /etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except
> that the former
On Thu, Jun 09, 2022 at 10:42:07AM +0200, Harald Dunkel wrote:
>
> If I have to hardwire the interface names to their Mac address as you
> suggested, then I don't see a significant difference to the old-style
> /etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except
> that the form
If I have to hardwire the interface names to their Mac address as you
suggested, then I don't see a significant difference to the old-style
/etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except
that the former was auto-generated and easier to modify.
Regards
Harri
On Wed, Jun 08, 2022 at 02:17:18PM -0600, Charles Curley wrote:
> On Wed, 8 Jun 2022 15:17:04 -0400
> Greg Wooledge wrote:
>
> > I strongly recommend that you create systemd.link(5) files, one for
> > each interface.
>
> Or just get back the original interface naming scheme.
> https://wiki.debia
On Wed, 8 Jun 2022 15:17:04 -0400
Greg Wooledge wrote:
> I strongly recommend that you create systemd.link(5) files, one for
> each interface.
Or just get back the original interface naming scheme.
https://wiki.debian.org/NetworkInterfaceNames#THE_ORIGINAL_SIMPLE_SCHEME
--
Does anybody read si
On 09.06.2022 00:04, Harald Dunkel wrote:
Hi folks,
after the upgrade to Debian 11 some network interfaces in my
Dell R740 got renamed. Before:
# lshw -class network -short
H/W path Device Class Description
/0/2/0
On Wed, Jun 08, 2022 at 09:04:46PM +0200, Harald Dunkel wrote:
> after the upgrade to Debian 11 some network interfaces in my
> Dell R740 got renamed.
I strongly recommend that you create systemd.link(5) files, one for each
interface.
Make up some names of *your* choice for each interfac
Hi folks,
after the upgrade to Debian 11 some network interfaces in my
Dell R740 got renamed. Before:
# lshw -class network -short
H/W path Device Class Description
/0/2/0eno1network
Hello,
On Sat, Mar 26, 2022 at 08:48:35AM -0400, Greg Wooledge wrote:
> Maybe I should remove the trinity-3c-app-mailcom block, since it
> no longer seems to be doing anything helpful...?
Looking at my mailbox I've got hundreds of hits matching that, from
many differently apparently-real people a
On Sat, 26 Mar 2022 at 23:48, Greg Wooledge wrote:
> On Fri, Mar 25, 2022 at 11:43:36PM -0500, David Wright wrote:
> > On Fri 25 Mar 2022 at 07:31:14 (+0100), Stella Ashburne wrote:
> If "Stella" is
> a real person who has been blocked as collateral damage, well, that's
> unfortunate.
You can ju
On Fri, Mar 25, 2022 at 11:43:36PM -0500, David Wright wrote:
> In passing, I'm mystified by your quoting mechanism thinking
> it appropriate to display my time header in Chinese time:
> $ TZ='Asia/Shanghai' date --date='Thu, 24 Mar 2022 21:09:41 -0500'
> Fri Mar 25 10:09:41 CST 2022
> $
>
> On F
On 2022-03-26, David Wright wrote:
>>
>> When the /etc/network/interfaces file has the line
>>
>> source-directory /etc/network/interfaces.d/*
>
> An eccentric choice. But no elaboration, opinion, or reasoning.
>
>> Best wishes.
>
> To you too.
-directory /etc/network/interfaces.d
> >
> > Without knowing the reasoning behind your statement, there's
> > not a lot more help I can give.
> >
>
> My distro is Debian 11
>
> Attempt #1
>
> When the /etc/network/interfaces file has the line
>
Mon cheri
> Sent: Friday, March 25, 2022 at 10:09 AM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
> Please elabora
t; And in some situations, it's connected to a smartphone via USB tethering.
> > > And when I'm in the office, I may connect it to a LAN cable.
> > >
> > > Below are the contents of my /etc/network/interfaces file:
> > >
> > > # This file describes t
Mon cheri
> Sent: Sunday, March 20, 2022 at 10:31 PM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
> On Sat 19 Mar 2
On Wed 23 Mar 2022 at 13:35:13 (+0100), Stella Ashburne wrote:
> From: "David Wright"
> > >
> > > source /etc/network/interfaces.d/*
> >
> > I would change this line to
> >
> > source-directory /etc/network/interfaces.d
> >
> > (which was the default on new buster installations).
> >
> Am I right
debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
> >
> > source /etc/network/interfaces.d/*
>
> I would change this line to
>
> source-directory /etc/network/interfaces
t; > And in some situations, it's connected to a smartphone via USB tethering.
> > > And when I'm in the office, I may connect it to a LAN cable.
> > >
> > > Below are the contents of my /etc/network/interfaces file:
> > >
> > > # This file desc
ice, I may connect it to a LAN cable.
Below are the contents of my /etc/network/interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
I would change this line
cable.
>
> Below are the contents of my /etc/network/interfaces file:
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
I would change
On 19/03/2022 09:06, Stella Ashburne wrote:
No thank you. I won't touch NetworkManager or its variants with a ten foot
pole. Why?
Reason #1
[quote] I am sorry but we do not support NetworkManager.
I would go so far as to say do not use it at all .. but Linux distros think it
is some sort of
On 2022-03-19 13:19, Eduardo M KALINOWSKI wrote:
On 19/03/2022 09:06, Stella Ashburne wrote:
No thank you. I won't touch NetworkManager or its variants with a ten
foot pole. Why?
Reason #1
[quote] I am sorry but we do not support NetworkManager.
I would go so far as to say do not use it at a
Mon cheri
Thanks for your reply.
> Sent: Saturday, March 19, 2022 at 3:17 PM
> From: "Tim Woodall"
> To: "Stella Ashburne"
> Cc: "debian-user mailing list"
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> wa
Mon cheri
> Sent: Saturday, March 19, 2022 at 7:13 PM
> From: "Eduardo M KALINOWSKI"
> To: debian-user@lists.debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
>
> Th
of my /etc/network/interfaces file:
[...]
1. At the moment, if I wish to change to using a mobile hotspot from USB
tethering, I'll edit the /etc/network/interfaces file, uncomment the applicable
lines under #The primary network interface for wireless connections and place a
# in front of all
. And when
I'm in the office, I may connect it to a LAN cable.
Below are the contents of my /etc/network/interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interf
Hi
There are instances in which my machine is connected to a mobile hotspot. And
in some situations, it's connected to a smartphone via USB tethering. And when
I'm in the office, I may connect it to a LAN cable.
Below are the contents of my /etc/network/interfaces file:
# This file
Henning Follmann, 18.3.2019 20:07 +0100:
> Have you considered to switch from /e/n/i to systemd-networkd?
> I think that would solve the problem.
No, I'm not considering to switch the entire way of configuring the
network just to (maybe) get something working which I'd call a pretty
basic feature
HCP server is started while the interface it is
> configured to listen on is not yet up and therefore refuses to work.
> How can I make sure that the kea-dhcp4-server.service is started no
> sooner than after all network interfaces are up?
>
> What I've tried:
> 1 Copied /lib/
and therefore refuses to work.
>>> How can I make sure that the kea-dhcp4-server.service is started no
>>> sooner than after all network interfaces are up?
>>
>> 1) Make sure the interface is marked "auto" and NOT "allow-hotplug"
>>in /etc
re that the kea-dhcp4-server.service is started no
>> sooner than after all network interfaces are up?
>
> 1) Make sure the interface is marked "auto" and NOT "allow-hotplug"
>in /etc/network/interfaces.
>
>Interfaces that are marked "auto" are r
r than after all network interfaces are up?
1) Make sure the interface is marked "auto" and NOT "allow-hotplug"
in /etc/network/interfaces.
Interfaces that are marked "auto" are required to be up before systemd
will consider network-online.target to be satisf
d-networkd-wait-online
>>
>> Thanks, but no, my network configuration is done through
>> /etc/network/interfaces. Therefore this won't help.
>
> Try "systemctl enable ifupdown-wait-online.service" then.
> See bug #912112[1].
Thanks for the info! But alas, since I
On 2019-03-16 19:20 +0100, Markus Schönhaber wrote:
> John Doe, 16.3.2019 14:18 +0100:
>
>> If your interface is configured by 'systemd', you could try:
>>
>> $ systemctl enable systemd-networkd-wait-online
>
> Thanks, but no, my network configuration i
John Doe, 16.3.2019 14:18 +0100:
> If your interface is configured by 'systemd', you could try:
>
> $ systemctl enable systemd-networkd-wait-online
Thanks, but no, my network configuration is done through
/etc/network/interfaces. Therefore this won't help.
--
Regards
mks
e the interface it is
> configured to listen on is not yet up and therefore refuses to work.
> How can I make sure that the kea-dhcp4-server.service is started no
> sooner than after all network interfaces are up?
>
> What I've tried:
> 1 Copied /lib/systemd/system/k
e sure that the kea-dhcp4-server.service is started no
sooner than after all network interfaces are up?
What I've tried:
1 Copied /lib/systemd/system/kea-dhcp4-server.service to
/etc/systemd/system and added
Wants=networking.service
After=networking.service
to the [Unit] section of
Le 27/01/2019 à 22:09, Claudio M a écrit :
Jan 27 20:40:15 my-server systemd[1]: Starting Raise network interfaces...
Jan 27 20:40:20 my-server ifup[489]: Waiting for DAD... Done
Jan 27 20:45:15 my-server systemd[1]: networking.service: Start operation
timed out. Terminating.
Is this what you
configured (even
> though it has really been configured), **prints an error message**, and
> exits with status 0. This behavior may change in the future. *
>
> >> iface eth0 inet6 static
> >>address 2a01:xxxx::xxxx::2
> >>netmask 64
>
On Sun, Jan 27, 2019 at 12:07:37PM -0500, Ric Moore wrote:
> On 1/27/19 10:29 AM, Claudio M wrote:
> >Hi,
> >
> >I'm wondering if anyone came across this recently, because I can't
> >find any bug reports or posts referring to it online (so I'm
> >wondering if I messed something up inadvertenenp8s0t
On 1/27/19 10:29 AM, Claudio M wrote:
Hi,
I'm wondering if anyone came across this recently, because I can't find
any bug reports or posts referring to it online (so I'm wondering if I
messed something up inadvertenenp8s0tly).
Is /dev/eth0 still viable? Mine is now /dev/enp8s0
ifconfig sho
Le 27/01/2019 à 16:29, Claudio M a écrit :
auto eth0
iface eth0 inet static
address a.b.c.d
netmask 255.255.255.224
gateway c.d.e.f
up route add -net a.b.c.x netmask 255.255.255.224 gw c.d.e.x dev eth0
AFAIK, the gateway must be directly reachable on eth0. But c.d.e.x does
not see
ed it (previous uptime 66 days and change) everything
was working fine; now, the inet6 interface is not coming up at boot.
Here's my (redacted) /etc/network/interfaces:
> auto lo
> iface lo inet loopback
> iface lo inet6 loopback
>
> auto eth0
> iface eth0 inet static
> ad
Hi Reco,
works perfectly as you decribe for me.
Many thanks
Rainer
Am Donnerstag, 10. Januar 2019, 05:41:49 CET schrieb Reco:
> Hi.
>
> On Wed, Jan 09, 2019 at 11:09:58PM +0100, Rainer Dorsch wrote:
> > Hi,
> >
> > I have a system with two network interfaces
Hi.
On Wed, Jan 09, 2019 at 11:09:58PM +0100, Rainer Dorsch wrote:
> Hi,
>
> I have a system with two network interfaces, connecting to two subnets.
>
> For some reason the default route is going through eth0.3, I would want to
> have it through eth0.7.
Both
On 1/9/19, Rainer Dorsch wrote:
> Hi,
>
> I have a system with two network interfaces, connecting to two subnets.
>
> For some reason the default route is going through eth0.3, I would want to
> have it through eth0.7.
further down you've got:
rd@master:~$ ip r
default via
Hi,
I have a system with two network interfaces, connecting to two subnets.
For some reason the default route is going through eth0.3, I would want to
have it through eth0.7.
Is the default route determined by the order in /etc/network/interface of the
interfaces or is there another
0, even though I do
> > not request that in /etc/network/interfaces (?).
>
>
>
> > 2: enp1s0: mtu 1500 qdisc pfifo_fast
> > state UP group default qlen 1000
> >
> > link/ether 74:d4:35:7b:0d:d8 brd ff:ff:ff:ff:ff:ff
> > inet6 2a02:8070
Hi.
On Wed, Jan 09, 2019 at 10:42:27AM +0100, Rainer Dorsch wrote:
> Hello,
>
> I am just wondering why ipv6 gets configured for enp1s0, even though I do not
> request that in /etc/network/interfaces (?).
> 2: enp1s0: mtu 1500 qdisc pfifo_fast state
> UP
> gr
Hello,
I am just wondering why ipv6 gets configured for enp1s0, even though I do not
request that in /etc/network/interfaces (?).
I suspect NetworkManager takes care of that, but I always thought, network
manager does not touch interfaces mentioned in /etc/network/interface?
System is stretch
d it's outdated, consider
upgrading. Does not affect your problem though.
> Now I have to rewrite /etc/network/interfaces to implement this function,
> but I got errors, so I want to know if there is demo about how to define
> VRF interface and implement VRF function in /etc/network/in
utube.com/watch?v=uAHmZKEdqDE&feature=youtu.be
Now I have to rewrite /etc/network/interfaces to implement this function,
but I got errors, so I want to know if there is demo about how to define
VRF interface and implement VRF function in /etc/network/interfaces.
As I follow your man file, I
On Fri, Nov 23, 2018 at 11:39:48AM -0200, Luciano Andress Martini wrote:
> 2- Try to change the ip in /etc/network/interfaces
> 3- Run ifdown enp0s3
> 4- Run ifup enp0s3
Perhaps you want to do it this way instead:
2- ifdown enp0s3
3- edit /etc/network/interfaces
4- ifup enp0s3
/interfaces
3- Run systemctl restart networking
ping 8.8.8.8
(network stopped working!)
If system is restarted everything is ok again, and ip is changed properly .
New try, now with ifdown and ifup:
1- Install Debian 9.6 without graphical interface.
2- Try to change the ip in /etc/network/interfaces
3- Run
o change �allow-hotplug� to �auto� to get it to come up on reboot:
root@macpro:~# diff /etc/network/interfaces.ORIG /etc/network/interfaces
11c11
< allow-hotplug enP1p3s15f0
---
auto enP1p3s15f0
Looks good.
If there�s some place that�s mistakenly expecting a name like �eth0�, where
might
ad to change “allow-hotplug” to “auto” to get it to come up on reboot:
>> root@macpro:~# diff /etc/network/interfaces.ORIG /etc/network/interfaces
>> 11c11
>> < allow-hotplug enP1p3s15f0
>> ---
>>> auto enP1p3s15f0
>
> Looks good.
>
>> If there’s so
d be "inet".
>
No Greg, the word "net" s/b "inet".
> > I had to change “allow-hotplug” to “auto” to get it to come up on
> > reboot: root@macpro:~# diff /etc/network/interfaces.ORIG
> > /etc/network/interfaces 11c11
> > < allow-hotplug
come up on reboot:
> root@macpro:~# diff /etc/network/interfaces.ORIG /etc/network/interfaces
> 11c11
> < allow-hotplug enP1p3s15f0
> ---
> > auto enP1p3s15f0
Looks good.
> If there’s some place that’s mistakenly expecting a name like “eth0”, where
> might it be located?
Le 26/09/2017 à 11:38, Rick Thomas a écrit :
# The primary network interface
auto enP1p3s15f0
iface enP1p3s15f0 net dhcp
^^^
It should be "inet". Typo in your post or in the actual file ?
1 - 100 of 598 matches
Mail list logo
