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
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
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
Hi,
On Sun, Jan 27, 2019 at 5:55 PM Pascal Hambourg
wrote:
> 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
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, connecting to two subnets.
>
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 of your VLANs are configur
Change your default gateway to 192.168.7.1 (or whatever the router is
on that subnet) & it should pick eno1.7 for the default route.
Regards,
Lee
>
> Is the default route determined by the order in /etc/network/interface of
> the
> interfaces or is there another algorithm behind?
>
algorithm behind?
rd@master:~$ 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 interface
auto lo
iface lo inet loopback
auto
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
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 ?
isions 0
So the interface name is “enP1p3s15f0"
I haven’t done anything to change the name from the original one assigned by
the installer.
Here’s what’s in /e/n/interfaces:
root@macpro:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
#
Le 25/09/2017 à 18:00, Gene Heskett a écrit :
Also, there's http://manpages.debian.org/interfaces
In fact, the man page outright *lies* and says they're synonyms.
No it doesn't. It says that "allow-auto" (not "allow-hotplug") and
"auto" are synonyms, which is correct AFAICS.
On 09/23/2017 08:56 PM, Rick Thomas wrote:
I have two machines (out of a group of ten) that will not bring up their
ethernet interface at boot time if the interfaces is of type �allow-hotplug�.
When I change that to �auto� the interface comes up at boot with no problem�
The remaining eight ma
On Monday 25 September 2017 11:47:36 Greg Wooledge wrote:
> On Mon, Sep 25, 2017 at 11:40:12AM -0400, Gene Heskett wrote:
> > On Monday 25 September 2017 09:00:51 Greg Wooledge wrote:
> > > An interface marked "auto" will be waited-for by services that are
> > > configured to wait for interfaces t
On Mon, Sep 25, 2017 at 11:40:12AM -0400, Gene Heskett wrote:
> On Monday 25 September 2017 09:00:51 Greg Wooledge wrote:
> > An interface marked "auto" will be waited-for by services that are
> > configured to wait for interfaces to be up. E.g. mounting NFS file
> > systems, or starting an NFS se
On Monday 25 September 2017 09:00:51 Greg Wooledge wrote:
> On Sat, Sep 23, 2017 at 08:56:49PM -0700, Rick Thomas wrote:
> > I have two machines (out of a group of ten) that will not bring up
> > their ethernet interface at boot time if the interfaces is of type
> > “allow-hotplug”. When I change
On Sat, Sep 23, 2017 at 08:56:49PM -0700, Rick Thomas wrote:
> I have two machines (out of a group of ten) that will not bring up their
> ethernet interface at boot time if the interfaces is of type “allow-hotplug”.
> When I change that to “auto” the interface comes up at boot with no problem…
>
On Sep 24, 2017, at 6:24 AM, Henrique de Moraes Holschuh
wrote:
> On Sat, 23 Sep 2017, Rick Thomas wrote:
>> I have two machines (out of a group of ten) that will not bring up
>> their ethernet interface at boot time if the interfaces is of type
>> “allow-hotplug”. When I change that to “auto”
On Sat, 23 Sep 2017, Rick Thomas wrote:
> I have two machines (out of a group of ten) that will not bring up
> their ethernet interface at boot time if the interfaces is of type
> “allow-hotplug”. When I change that to “auto” the interface comes up
> at boot with no problem…
...
> Anybody have a
I have two machines (out of a group of ten) that will not bring up their
ethernet interface at boot time if the interfaces is of type “allow-hotplug”.
When I change that to “auto” the interface comes up at boot with no problem…
The remaining eight machines have no problem with allow-hotplug. (w
have manually set static IPv6 addresses.
> > But what I get are SLAAC addresses with $prefix + MAC-derived according to
> > the IEEE-Tutorial EUI-64 .
> > I can cope with a SLAAC address AND an additional manual static address on
> > the same interface - no problem - but
-derived according to
> the
> IEEE-Tutorial EUI-64 .
> I can cope with a SLAAC address AND an additional manual static address on
> the
> same interface - no problem - but what is going on here? Why is the manual
> address in the file "/etc/network/interfaces" ignored
iously what you'd want as a setting.
> I can cope with a SLAAC address AND an additional manual static address on
> the
> same interface - no problem - but what is going on here? Why is the manual
> address in the file "/etc/network/interfaces" ignored?
They shouldn&#
On 05.07.2017 20:09, Eike Lantzsch wrote:
> Hi to all!
>
> I'm trying to teach myself to work with IPv6.
>
> On a Stretch client I'd like to have manually set static IPv6 addresses.
> But what I get are SLAAC addresses with $prefix + MAC-derived according to
> the
> IEEE-Tutorial EUI-64 .
Try
ual static address on the
same interface - no problem - but what is going on here? Why is the manual
address in the file "/etc/network/interfaces" ignored?
What is it that I don't understand?
I don't have such problem with OpenBSD-clients - only with Debian Stretch.
Is it a bu
>> "ifconfig" can not handle multiple IPv4 addresses on one interface
>and
>> needs this kind of crutch.
>>
>> The far more modern command "ip" has no such limitations.
>
>I've found my own brain to have a similar limitation, and find
>interface
>aliases useful for clarity even when I have ip(8)
On Sat, Mar 04, 2017 at 09:10:16PM +0100, Sven Hartge wrote:
> Worth noting: the interface:alias notation was introduced because
> "ifconfig" can not handle multiple IPv4 addresses on one interface and
> needs this kind of crutch.
>
> The far more modern command "ip" has no such limitations.
I'v
Dominik George wrote:
>> I need to know that what is the difference b/w eth1.0101 and eth:1.
>> actually i need to know what is the main difference in "." and ":".
>> any suggestion will be highly appreciated.
> : denotes an alias (second address on same interface), . denotes a VLAN, and
> eth:
sorry what i meant is eth1:1 sorry my mistake.
but thanks for the clarification.
On Sun, Mar 5, 2017 at 12:45 AM, Muhammad Yousuf Khan
wrote:
> sorry what i meant is eth1:1 sorry my mistake.
> but thanks for the clarification.
>
>
> On Sat, Mar 4, 2017 at 11:40 PM, Pascal Hambourg
> wrote:
>
>>
Le 04/03/2017 à 18:40, Dominik George a écrit :
eth:1 is nonsense.
Why ? There could be an interface named "eth".
Hi,
>I need to know that what is the difference b/w eth1.0101 and eth:1.
>actually i need to know what is the main difference in "." and ":".
>any suggestion will be highly appreciated.
: denotes an alias (second address on same interface), . denotes a VLAN, and
eth:1 is nonsense.
Cheers,
Nik
Hi All,
I need to know that what is the difference b/w eth1.0101 and eth:1.
actually i need to know what is the main difference in "." and ":".
any suggestion will be highly appreciated.
Thanks,
Yousuf
On 12/29/2016 11:49 AM, Reco wrote:
>
> auto br0
> iface br0 inet6 auto
> bridge-ports ...
> bridge-maxwait 0
>
> Please note that you have to specify *something* in 'bridge-ports'
> stanza.
>
Thanx, I was too blind to see.
Regards
Harri
Hi.
On Thu, Dec 29, 2016 at 10:01:20AM +0100, Harald Dunkel wrote:
> Hi folks,
>
> how can I define a bridge in /etc/network/interfaces without
> assigning it an IP address and netmask? It is supposed to
> be IPv6 link-layer only.
auto br0
iface br0 inet6 auto
Hi folks,
how can I define a bridge in /etc/network/interfaces without
assigning it an IP address and netmask? It is supposed to
be IPv6 link-layer only.
Regards
Harri
On 12/09/16 23:23, Neal P. Murphy wrote:
You might find something in here useful.
On 12/09/16 21:43, Charlie Kravetz wrote:
Change the bridge_ports to:
bridge_ports eth1 tap0
then add the tap lines:
auto tap0
iface tap0 inet static
address 192.1
On Mon, 12 Sep 2016 21:14:15 +0100
Andrew Wood wrote:
> Im (slowly) trying to setup bridging and TAP interfaces to use with QEMU
> so each VM can have a 'real' IP on the network rather than NAT.
>
>
> I now have a bridge setup (br1) using eth1 which Ive done in
>
1 - 100 of 438 matches
Mail list logo
