12 Apr 2025, 03:59 by jeremy_ardley_at_gmail_com_lluoq...@simplelogin.co:
>
> On 12/4/25 08:16, coffeeforblood.pardon...@slmail.me wrote:
>
>> The short version is that if the behavior with "Connect Automatically" and
>> "Make available to other users" is down to NetworkManager, then I
>> sympa
On 12/04/2025 07:16, coffeeforblood.pardon117 wrote:
I performed some very basic testing using a Debian 12.8.0 Live CD.
Likely nobody will be interested in minor bugs for versions released a
couple of years ago. At current moment it is better to try trixie weekly
builds. Upstream developers o
On 12/4/25 11:27, Max Nikulin wrote:
I had both running without conflicts on my old laptop with
Ubuntu-20.04 LTS focal. I hope, Debian does not differ in this case.
Just set what devices each daemon should ignore.
Ethernet and WiFi were under control of NetworkManager (to have tray
indicato
On 12/04/2025 09:58, jeremy ardley wrote:
The thing to remember is you can't have NetworkManager and systemd-
networkd running at the same time.
I had both running without conflicts on my old laptop with Ubuntu-20.04
LTS focal. I hope, Debian does not differ in this case. Just set what
device
On 12/4/25 08:16, coffeeforblood.pardon...@slmail.me wrote:
The short version is that if the behavior with "Connect Automatically" and "Make
available to other users" is down to NetworkManager, then I sympathize with the suggestions
to migrate from it to systemd-networkd. If someone could po
Thank you for the continued responses. I performed some very basic testing
using a Debian 12.8.0 Live CD. The results were confusing and highlighted some
issues with the creation of network profiles in general, at least from my point
of view.
The short version is that if the behavior with "Con
On Mon 07 Apr 2025 at 21:34:42 (+0200), coffeeforblood.pardon...@slmail.me
wrote:
>
> > I am curious what nmcli subcommand reports when the cable is plugged in,
> > but the connection has not activated manually.
> >
> Should I pursue the strange behavior of needing to have "Make available to
>
On Mon, Apr 07, 2025 at 09:34:42PM +0200, coffeeforblood.pardon...@slmail.me
wrote:
Should I pursue the strange behavior of needing to have "Make available
to others users" enabled for the "Connect Automatically" setting to be
respected, in case there is a bug, or close this issue as solved? I'
On 08/04/2025 02:34, coffeeforblood.pardon117 wrote:
I am curious what nmcli subcommand reports when the cable is plugged in,
but the connection has not activated manually.
Should I pursue the strange behavior of needing to have "Make available
to others users" enabled for the "Connect Automat
On 8/4/25 11:18, Titus Newswanger wrote:
FWIW, I generally don't get along with NetworkManager on server
installations and end up uninstalling it and running either
systemd-networkd or netplan. I just got done with a server install
where the network was not coming up until after I logged into
On 4/7/25 14:34, coffeeforblood.pardon...@slmail.me wrote:
Should I pursue the strange behavior of needing to have "Make available to others users"
enabled for the "Connect Automatically" setting to be respected, in case there is a bug,
or close this issue as solved? I'm happy either way.
FW
> I am curious what nmcli subcommand reports when the cable is plugged in, but
> the connection has not activated manually.
>
Should I pursue the strange behavior of needing to have "Make available to
others users" enabled for the "Connect Automatically" setting to be respected,
in case there
On Fri, Apr 4, 2025 at 10:17 PM wrote:
>
> On Thu, Apr 4, 2025 at 11:56 PM Lee wrote:
>
> > Can you try it with Make available to other users ON
>
> Toggling "Make available to other users" to ON solves the problem! First I
> tested this with the built-in Ethernet adapter. After this was successf
On 05/04/2025 07:33, coffeeforblood.pardon117 wrote:
I think there is still the question of why this setting must be ON for
this to work properly. I followed the steps suggested by Max Nikulin and
I think there is something interesting in the output of 'journalctl -f'.
I do not think, GNOME ap
On Thu, Apr 4, 2025 at 11:56 PM wrote:
> Can you try it with Make available to other users ON
Toggling "Make available to other users" to ON solves the problem! First I
tested this with the built-in Ethernet adapter. After this was successful I
configured this to ON for the other adapters and
On Thu, Apr 3, 2025 at 9:32 PM wrote:
>
> Background Information
> ===
>
> Debian 12 Bookworm has been freshly installed on a laptop. The laptop is
> functioning as a simple home server and has three Ethernet devices, two USB
> Ethernet adapters and a built-in Ethernet adapte
On Fri, Apr 04, 2025 at 05:19:08PM +0800, jeremy ardley wrote:
Off Topic I just did a 1 year diploma in advanced networking. I
couldn't even comprehend why the still had crossover cables in the
lab. Perhaps to accommodate pre-2000 CISCO switches?
cisco was one of the companies that was late to
nmcli
nmcli status
nmcli device
Check that devices are not mentioned in /etc/network/interfaces and
/etc/network/interfaces.d/*. Next step in diagnostics is to find moment
of plugging in cable in output of
# journalctl -b
or start
# journalctl -f
and connect other device.
M
On 4/4/25 17:06, Jeffrey Walton wrote:
I would not be surprised to learn that some inexpensive ethernet
controllers lacked some features, like Auto MDI-X, since it is an
optional feature of the 1000BASE-T standard.
For 1000BASE-T I would be very surprised if that was the case as it uses
all
On Fri, Apr 4, 2025 at 12:52 AM jeremy ardley wrote:
>
> On 4/4/25 09:38, Jeffrey Walton wrote:
> > It sounds like the client is connected directly to the server via
> > ethernet, presumably without a cross-over ethernet cable. So both
> > ethernet ports would need to auto-sense the configuration.
On Thu, Apr 03, 2025 at 09:38:29PM -0400, Jeffrey Walton wrote:
... when a cable from the server is connected to the Ethernet port
of a client device, the Debian server will automatically recognize
the new physical connection and then automatically activate that
connection.
It sounds
On 4/4/25 09:38, Jeffrey Walton wrote:
It sounds like the client is connected directly to the server via
ethernet, presumably without a cross-over ethernet cable. So both
ethernet ports would need to auto-sense the configuration.
Can you run the same experiment with a hub or switch in between?
On Thu, Apr 3, 2025 at 9:32 PM wrote:
>
> Background Information
> ===
>
> Debian 12 Bookworm has been freshly installed on a laptop. The laptop is
> functioning as a simple home server and has three Ethernet devices, two USB
> Ethernet adapters and a built-in Ethernet adapte
Background Information
===
Debian 12 Bookworm has been freshly installed on a laptop. The laptop is
functioning as a simple home server and has three Ethernet devices, two USB
Ethernet adapters and a built-in Ethernet adapter. Ethernet cables are
permanently inserted into ea
On 4/4/25 06:56, coffeeforblood.pardon...@slmail.me wrote:
I noted that systemd-networkd service is not running by default. For testing
purposes I enabled and started this service, but there was no improvement.
systemd-networkd is a competitor to NetworkManager. You need to run one
or the
gn firewall zones to specific interfaces, which helps.
> 'ifconfig' is not installed by default. Is this also normal for a
> fresh installation of Debian 12?
Yes. ifconfig is part of the net-tools package. Or you could use ip.
I've been using ifconfig for more than 25 years,
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
/interfaces (which I like), Network Manager
(which I reluctantly accept), systemctl (which I do not appreciate), etc.
Similarly with Firewalls, iptables (which I like), nftables (which I ask,
Why?), and I am not sure what other methods are out there, but I guess there
are more.
Sadly I am far from
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
On Fri, Sep 27, 2024 at 10:42:39PM +, Andy Smith wrote:
> Is it doable with any of the other network configuration frameworks
> (systemd-networkd, NetworkManager, netplan, …)?
It's not directly doable in ifupdown but can be bodged with hook
commands.
It's not doable in netplan. There is a wis
On Sat, Sep 28, 2024 at 07:25:37PM +, Andy Smith wrote:
> I got a reply on Fedi basically to that effect, by someone who had
> recently presented on the subject
And here's Tobias's presentation (21 minutes; link to slides on that
page):
https://ripe88.ripe.net/archives/video/1358/
--
ht
Hi,
On Sat, Sep 28, 2024 at 04:37:31PM +0100, Tim Woodall wrote:
> Fascinating! I had absolutely no idea you could do that!
It is fun. 😀 Having users, even if it was supported in ifupdown,
netplan etc I'm still not sure I would do it just yet as it may be far
too unexpected for them.
> I suspect
On Fri, 27 Sep 2024, Andy Smith wrote:
Hi,
Here is a manual network setup I have created by use of the "ip"
command:
$ ip address show dev enX0
2: enX0: mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 00:16:5e:00:02:39 brd ff:ff:ff:ff:ff:ff
inet 85.119.82.225/32 scope glo
ifupdown's
> > /etc/network/interfaces syntax?
[…]
> > Is it doable with any of the other network configuration frameworks
> > (systemd-networkd, NetworkManager, netplan, …)?
[…]
> In regard to systemd-networkd and likely all other choices it probably won't
> wor
pdown's
/etc/network/interfaces syntax?
If there's no actual syntax for this (particularly, the "gateway" option
says it expects a dotted quad) possibly it can be done with pre-up
commands?
Is it doable with any of the other network configuration frameworks
(systemd-networkd, NetworkM
link-local address.
This works fine, however I had to configure it using the "ip" command:
# ip address add 85.119.82.225/32 dev enX0
# ip -4 route add default via inet6 fe80::1 src 85.119.82.225
Is it possible to configure that using ifupdown's
/etc/network/interfaces syntax?
If the
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
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
ot;machine" indeed is a
Proxmox-Container, and someone made a typo in the container settings,
so Proxmox configures the container accordingly.
For other files, like resolv.conf, Proxmox adds "# --- BEGIN PVE ---"
lines, but not in interfaces.
Thank you
Steffen
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
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 connman
Best
> On Mar 26, 2024, at 10:33, Steffen Dettmer wr
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
t/login from Mate to make sure my user picks up
the new group.
> $ groups # The output should now include "wireshark" group name
Turns out these steps are not sufficient now.
I wonder if Wireshark uses `dumpcap -D` internally to show the list of
interfaces? I can do this now from my user acc
Lee wrote:
> >
> >> >
> >> > However when I startup wireshark from the GUI, it does not show the
> >> > physical interfaces in the list of interfaces to capture from, so I
> >> > cannot really capture anything from the non-root user. When
Hello
On 2023-04-29 17:33, Lee wrote:
On 4/29/23, Victor Sudakov wrote:
Lee wrote:
On 4/29/23, Victor Sudakov wrote:
[dd]
>
> However when I startup wireshark from the GUI, it does not show the
> physical interfaces in the list of interfaces to capture from, so I
> cannot re
On 4/29/23, Victor Sudakov wrote:
> Lee wrote:
>> On 4/29/23, Victor Sudakov wrote:
>
> [dd]
>
>> >
>> > However when I startup wireshark from the GUI, it does not show the
>> > physical interfaces in the list of interfaces to capture from, so I
>
Victor Sudakov wrote:
>
> I don't see any physical interfaces there, this is all I see:
> https://ibb.co/190ytwv
Sorry I forgot to mention that dumpcap sees the NICs, but the
Wireshark GUI does not:
$ whoami ; dumpcap -D
vas
1. enp3s0
2. any
3. lo (Loopback)
4. bluetooth-moni
Lee wrote:
> On 4/29/23, Victor Sudakov wrote:
[dd]
> >
> > However when I startup wireshark from the GUI, it does not show the
> > physical interfaces in the list of interfaces to capture from, so I
> > cannot really capture anything from the non-root user. When st
rk_enp3s0Y3LW31.pcapng
> Packets captured: 126
> Packets received/dropped on interface 'enp3s0': 126/0
> (pcap:0/dumpcap:0/flushed:0/ps_ifdrop:0) (100.0%)
> $
>
> However when I startup wireshark from the GUI, it does not show the
> physical interfaces in the list o
/0
(pcap:0/dumpcap:0/flushed:0/ps_ifdrop:0) (100.0%)
$
However when I startup wireshark from the GUI, it does not show the
physical interfaces in the list of interfaces to capture from, so I
cannot really capture anything from the non-root user. When started
via sudo, it does show enp3s0 and ot
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:
> >>
> >> ===
> >
i was capable of disabling interfaces,
the message looks like it's updating a table/list (etc) and "...no
longer relevant..." messages appear in my syslog if I deliberately
disconnect from wifi.
Please can you provide syslog extracts from just before and during a
time when this
On 7/14/22 09:15, Ram Ramesh wrote:
Hi Ramesh,
There are numerous reports (mostly old, afaics) of the issue you
describe, but with various suggested reasons.
I suspect the avahi related part is a consequence rather than a cause
- I didn't think avahi was capable of disabling interfaces
Hi Ramesh,
There are numerous reports (mostly old, afaics) of the issue you describe, but
with various suggested reasons.
I suspect the avahi related part is a consequence rather than a cause - I didn't think
avahi was capable of disabling interfaces, the message looks like it's
reasons.
I suspect the avahi related part is a consequence rather than a cause - I
didn't think avahi was capable of disabling interfaces, the message looks like
it's updating a table/list (etc) and "...no longer relevant..." messages appear
in my syslog if I deliberately di
Hi Ramesh,
Please could you post some example daemon.log entries and any surrounding
entries that seem related?
Also is there anything in
/var/log/syslog
that seems to relate?
Perhaps
$ sudo cat /var/log/syslog | grep x
where x = the interface name concerned.
Thanks,
Gareth
Hi Gareth,
On 7/12/22 19:21, Ram Ramesh wrote:
On 7/11/22 11:30, Ram Ramesh wrote:
Experts,
I have a firewall machine built recently and it runs debian
bullseye (v11). It has two ethernet interfaces - one internal ($intf)
and one external ($extf). My external port runs dhclient to get its
IP address
On Wed 13 Jul 2022, at 01:21, Ram Ramesh wrote:
> Do you know a simple way to disable autopowerdown of
> just this usb NIC? May be there is something that I can do with ethtool?
I wonder if powertop may be of use here.
It has a "tunables" section where (I think) power-saving features can be
On 7/11/22 11:30, Ram Ramesh wrote:
Experts,
I have a firewall machine built recently and it runs debian bullseye
(v11). It has two ethernet interfaces - one internal ($intf) and one
external ($extf). My external port runs dhclient to get its IP address
and internal port runs dnsmasq to
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 11 Jul 2022, at 17:48, Ram Ramesh wrote:
[...]
> . However, my new machine has this daemon running which notices that $extif
> does not have much activity and disables it after some timeout idle time.
> Today I noticed that my $extif is vanishing and /var/log/daemon.log shows
> some av
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
Experts,
I have a firewall machine built recently and it runs debian bullseye
(v11). It has two ethernet interfaces - one internal ($intf) and one
external ($extf). My external port runs dhclient to get its IP address
and internal port runs dnsmasq to provide DNS service to
internal
Steve McIntyre writes:
> In my experience, the bridge may end up advertising the MAC of any/all
> of the underlying interfaces, and that behaviour can be racy
> sometimes. I noticed locally that *sometimes* I'd lose IPv6
> connectivity from my workstation when I started bridg
t;But how is that MAC address generated? Is it stored somewhere?
>Can I set it to an address of my own preference?
>And why was this changed, why don't we still use the address of
>the physical port connected to it?
In my experience, the bridge may end up advertising the MAC of any/all
of
On 29.06.2022 07:27, Steve Keller wrote:
I upgraded a Debian machine from stretch to bullseye and see
a change of the IP address of a ethernet bridge interface.
The bridge has a physical LAN interface as one fixed bridge port
and additional ports for kvm virtual machines I may start.
Before the
I upgraded a Debian machine from stretch to bullseye and see
a change of the IP address of a ethernet bridge interface.
The bridge has a physical LAN interface as one fixed bridge port
and additional ports for kvm virtual machines I may start.
Before the upgrade the bridge interface got its MAC a
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
face naming scheme.
> https://wiki.debian.org/NetworkInterfaceNames#THE_ORIGINAL_SIMPLE_SCHEME
On a machine with 6 ethernet interfaces, I doubt this will give stable
names either. The original "eth0" scheme is absolutely perfect for a
machine with exactly 1 ethernet interface, but becomes unreliable with
more interfaces.
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
1 - 100 of 995 matches
Mail list logo
