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 net
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 th
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
configuration framework at all and just set up
your networking with a shell script, this would work. I think it could
also work with ifupdown if you abused pre-up commands, which would
certainly be preferable to two layers of NAT!
Something like
auto enX0
iface enX0 inet
address 85.119.82.225/
On 28/9/24 06:42, 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
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 global enX0
valid_lft forever prefer
On Tuesday, 30-07-2024 at 02:21 Jan Krapivin wrote:
> There is Debian community in Discord
>
> https://discord.gg/debian
>
> https://forums.debian.net/viewtopic.php?p=803217&hilit=discord#p803217
>
> пн, 29 июл. 2024 г. в 19:15, :
>
> > Michel Verdier wrote:
> > > On 2024-07-28, Michael Gra
Hi,
(I am subscribed to the list, but a CC would be appreciated :) )
On 7/28/24 16:53, Andy Smith wrote:
> Hi,
>
> On Sun, Jul 28, 2024 at 06:15:21PM +0100, Ian Molton wrote:
>> Which web forum has the commuity moved to then? I should like to join it...
>
> Sadly, the Debian project is not will
There is Debian community in Discord
https://discord.gg/debian
https://forums.debian.net/viewtopic.php?p=803217&hilit=discord#p803217
пн, 29 июл. 2024 г. в 19:15, :
> Michel Verdier wrote:
> > On 2024-07-28, Michael Grant wrote:
> >
> > +1 to all you say.
> >
> > > Maybe one of you younger fol
Michel Verdier wrote:
> On 2024-07-28, Michael Grant wrote:
>
> +1 to all you say.
>
> > Maybe one of you younger folks can teach me how one deals with
> > keeping up with a forum like that.
>
> Once upon a time there was usenet. After a while there was a
> mail-to-news gateway. It ease a lot
On Mon, 29 Jul 2024 06:24:35 +0200
wrote:
> On Sun, Jul 28, 2024 at 08:53:18PM +, Andy Smith wrote:
> > Hi,
> >
> > On Sun, Jul 28, 2024 at 06:15:21PM +0100, Ian Molton wrote:
> > > Which web forum has the commuity moved to then? I should like to
> > > join it...
> >
> > Sadly, the Debi
Michel Verdier wrote:
> On 2024-07-28, Michael Grant wrote:
>
> +1 to all you say.
>
> > Maybe one of you younger folks can teach me how one deals with keeping
> > up with a forum like that.
>
> Once upon a time there was usenet. After a while there was a mail-to-news
> gateway. It ease a lot c
On Mon, 29 Jul 2024 02:44:03 -0400
Jeffrey Walton wrote:
Hello Jeffrey,
>don't allow search engines to crawl their sites.
I hadn't even considered that.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
Hi,
On Mon, Jul 29, 2024 at 02:06:09AM +, Walt E wrote:
> In some companies they block web traffic to those big forums like reddit.
> but mail is always possible to access.
Reality check: in a thread about the best way to help end users in
2024, someone suggests that email mailing lists are t
On Mon, Jul 29, 2024 at 1:53 AM Brad Rogers wrote:
>
> On Sun, 28 Jul 2024 21:04:30 -0500
> Nate Bargmann wrote:
>
> Hello Nate,
>
> >Discourse and Discord are two different technologies, AIUI
>
> Discourse also does this;
>
> Unfortunately, your browser is unsupported. Please switch to a support
On 2024-07-28, Michael Grant wrote:
+1 to all you say.
> Maybe one of you younger folks can teach me how one deals with keeping
> up with a forum like that.
Once upon a time there was usenet. After a while there was a mail-to-news
gateway. It ease a lot coping with this change of medium. If the
On Sun, 28 Jul 2024 21:04:30 -0500
Nate Bargmann wrote:
Hello Nate,
>Discourse and Discord are two different technologies, AIUI
Discourse also does this;
Unfortunately, your browser is unsupported. Please switch to a supported
browser to view rich content, log in and reply.
Whilst it's not i
On Sun, Jul 28, 2024 at 08:53:18PM +, Andy Smith wrote:
> Hi,
>
> On Sun, Jul 28, 2024 at 06:15:21PM +0100, Ian Molton wrote:
> > Which web forum has the commuity moved to then? I should like to join it...
>
> Sadly, the Debian project is not willing to move with the times and
> bless a moder
July 29, 2024 at 9:09 AM, "Patrick Wiseman" wrote:
> >
>
> I mostly lurk here but I like this forum/format and hope Debian sticks with
>
> it. IMO Discord pretty much sucks. There's a r/debian subreddit which looks
>
> quite active and I've found other subreddits helpful.
>
> Patrick
>
In s
* On 2024 28 Jul 20:11 -0500, Patrick Wiseman wrote:
> I mostly lurk here but I like this forum/format and hope Debian sticks with
> it. IMO Discord pretty much sucks. There's a r/debian subreddit which looks
> quite active and I've found other subreddits helpful.
Discourse and Discord are two dif
Hi,
On Sun, Jul 28, 2024 at 09:09:39PM -0400, Patrick Wiseman wrote:
> I like this forum/format
Not wanting to try to convince people on a mailing list to not be on
a mailing list, so keeping this brief, but…
> IMO Discord pretty much sucks.
Discourse is not Discord. They are completely differe
Hi,
On Sun, Jul 28, 2024 at 06:32:58PM -0400, Michael Grant wrote:
> I never read web forums, I only really search for things in a
> search engine and then end up on a forum with possible answers.
The fact is that millions of tech questions are asked and answered
on Stack-like sites, probably mor
On Sun, Jul 28, 2024 at 08:53:18PM +, Andy Smith wrote:
> Hi,
>
> On Sun, Jul 28, 2024 at 06:15:21PM +0100, Ian Molton wrote:
> > Which web forum has the commuity moved to then? I should like to join it...
>
> Sadly, the Debian project is not willing to move with the times and
> bless a moder
Hi,
On Sun, Jul 28, 2024 at 06:15:21PM +0100, Ian Molton wrote:
> Which web forum has the commuity moved to then? I should like to join it...
Sadly, the Debian project is not willing to move with the times and
bless a modern web support community such as Discourse (a Stack
Overflow or AskUbuntu-l
On Sun, Jul 28, 2024 at 19:08:58 +, MailGuard01 wrote:
> Is it still reasonable to add my experience to existing bug report,
> or should I submit a new one instead?
Adding to an existing bug report is a good thing, especially if you can
bring new insights, new examples, etc.
On Sun, 28 Jul 2024 18:15:21 +0100 (GMT+01:00)
Ian Molton wrote:
Hello Ian,
>Which web forum has the commuity moved to then? I should like to join
Don't know. Never considered switching.
From the web forums I have used, I've ascertained that they offer
nothing that can't be done on a mailing
On Friday, July 26th, 2024 at PM 10:42, David Wright
wrote:
> There is a bug report #960809, which seems related, and
> might be worth adding your experience to, if you think so.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960809
>
Thank you for letting me know about this. I also n
Which web forum has the commuity moved to then? I should like to join
it...
On 2024-07-28, Ian Molton wrote:
> https://lists.debian.org/stats/debian-user.png
>
> An alarming decline, with a multitude of reasons.
>
> But lack of community will be the one that ends that graph. Be in no doubt.
Members remains around 3000 so I don't see a decline for this.
Messages decline b
On Sun, 28 Jul 2024 09:35:22 +0100 (GMT+01:00)
Ian Molton wrote:
Hello Ian,
>An alarming decline, with a multitude of reasons.
Same for most MLs; People think web forums are better.
Passive/aggressive messages don't help, either.
--
Regards _ "Valid sig separator is {dash}{dash}{spa
Hi,
As I said - the mailing list stats. Public record.
Heres a picture.
https://lists.debian.org/stats/debian-user.png
An alarming decline, with a multitude of reasons.
But lack of community will be the one that ends that graph. Be in no
doubt.
On 2024-07-26, Ian Molton wrote:
> Michael, that was not a personal attack. I am in no doubt that you personally
> try to help.
And *was helped*. So I am not alone :)
> The statistics for this list, however, are public record. And they are indeed
> of concern.
Can you give the statistics which
On Fri, 2024-07-26 at 23:12 +0100, Ian Molton wrote:
> Michael, that was not a personal attack. I am in no doubt that you
> personally try to help.
>
> The statistics for this list, however, are public record. And they
> are
> indeed of concern.
>
> Like so many open source projects, Debian is
Michael, that was not a personal attack. I am in no doubt that you
personally try to help.
The statistics for this list, however, are public record. And they are
indeed of concern.
Like so many open source projects, Debian is clearly showing a loss of
community, and whilst it continues to be
On Wed 24 Jul 2024 at 14:29:34 (+), MailGuard01 wrote:
> I am trying to complete the network configuration on Debian 12 using the
> default
> installed `ifupdown` package. I have noticed some confusing behavior with
> `ifupdown` while following the manual pages.
>
> Sp
On 2024-07-26, Ian Molton wrote:
> The attitude these days seems to be that 'if its not in bugzilla, no one
> cares'
>
> Seems like the Debian project is forgetting that it is a social endeavour, not
> a (increasingly small) handful of Devs vanity project...
I largely disagree with that. I was he
Hi.
Sorry, i cant help with your specific problem.
Just didn't want you to feel alone...
I don't know whats becoming of Debian these days.
Users need to stick together, but the traffic stats for these lists
paint a bleak picture.
The attitude these days seems to be that 'if its not in bugz
Hi all,
I am trying to complete the network configuration on Debian 12 using the default
installed `ifupdown` package. I have noticed some confusing behavior with
`ifupdown` while following the manual pages.
Specifically, when I place `iface eno1 inet6 auto` with `privext 2` after `iface
inet
ExpectedThroughput 15937Kbit/s
>
> Then:
>
> $ sudo nano /etc/network/interfaces
>
> , and added:
>
> ```
> allow-hotplug wlan4
> iface wlan4 inet dhcp
> ```
Here I've just got the 'loopback interface network':
auto lo
iface lo in
ng because the Debian wiki proposes (I think) two different schemes:
- ifupdown with wpasupplicant, iw, wireless-tools, etc.
- iwd enabling `EnableNetworkConfiguration=true` in /etc/iwd/main.conf
and setting the name resolving service with `systemd-resolved`
, and I did neither:
$ systemctl status
On Mon, Aug 30, 2021 at 03:56:09PM -0400, Dan Ritter wrote:
Harald Dunkel wrote:
how comes ifupdown is dropped at upgrade time to bullseye, leaving the
(headless) system without network connection while the upgrade is not completed
yet, and breaking network on the next reboot?
This has not
On Mon 30 Aug 2021 at 21:37:50 (+0200), Harald Dunkel wrote:
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> (headless) system without network connection while the upgrade is not
> completed yet, and breaking network on the next reboot?
I would presu
kel wrote:
> > how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> > (headless) system without network connection while the upgrade is not
> > completed yet, and breaking network on the next reboot?
>
> This has not yet happened to me in nine or ten u
Harald Dunkel wrote:
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> (headless) system without network connection while the upgrade is not
> completed yet, and breaking network on the next reboot?
This has not yet happened to me in nine or ten upgrades to
On Mon 30 Aug 2021 at 21:37:50 +0200, Harald Dunkel wrote:
> Hi folks,
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> (headless) system without network connection while the upgrade is not
That's a good question. Completely devoid of infirmation. Bu
Hi folks,
how comes ifupdown is dropped at upgrade time to bullseye, leaving the
(headless) system without network connection while the upgrade is not completed
yet, and breaking network on the next reboot?
Regards
Harri
d-networkd
> configuration, I decided to switch back to a combination of ifupdown,
> NetworkManager and resolvconf, like I had it in Debian 9. ifupdown for
> normal static configuration of eno1, NetworkManager for starting an
> OpenVPN connection from the GUI and resolvconf to be also
the dynamic IP address
assigned by NetworkManager/dhclient to the wired interface was preferred
over the IP address statically configured in systemd-networkd
configuration, I decided to switch back to a combination of ifupdown,
NetworkManager and resolvconf, like I had it in Debian 9. ifupdown
On Tue 28 Aug 2018 at 14:57:58 (-0400), Gene Heskett wrote:
> On Tuesday 28 August 2018 14:16:15 David Wright wrote:
>
> > On Mon 27 Aug 2018 at 19:21:00 (-0400), Gene Heskett wrote:
> > > On Monday 27 August 2018 15:59:09 David Wright wrote:
> > > > On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene He
On 8/28/18, Gene Heskett wrote:
> On Tuesday 28 August 2018 14:16:15 David Wright wrote:
>
>> On Mon 27 Aug 2018 at 19:21:00 (-0400), Gene Heskett wrote:
>> > On Monday 27 August 2018 15:59:09 David Wright wrote:
>> > > On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
>> > > > On Sunday
On Tuesday 28 August 2018 14:16:15 David Wright wrote:
> On Mon 27 Aug 2018 at 19:21:00 (-0400), Gene Heskett wrote:
> > On Monday 27 August 2018 15:59:09 David Wright wrote:
> > > On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
> > > > On Sunday 26 August 2018 13:36:41 Pascal Hambourg
On Mon 27 Aug 2018 at 19:21:00 (-0400), Gene Heskett wrote:
> On Monday 27 August 2018 15:59:09 David Wright wrote:
> > On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
> > > On Sunday 26 August 2018 13:36:41 Pascal Hambourg wrote:
> > > > Le 26/08/2018 à 17:24, Gene Heskett a écrit :
>
On Monday 27 August 2018 15:59:09 David Wright wrote:
> On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
> > On Sunday 26 August 2018 13:36:41 Pascal Hambourg wrote:
> > > Le 26/08/2018 à 17:24, Gene Heskett a écrit :
> > > > Most recently on a stretch install on a rock64 I had to erect
On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
> On Sunday 26 August 2018 13:36:41 Pascal Hambourg wrote:
> > Le 26/08/2018 à 17:24, Gene Heskett a écrit :
> > > Most recently on a stretch install on a rock64 I had to erect
> > > immutable attributes to resolv.conf after making it a re
keep its hands off a
> given interface.
>
> >> By default, NM does not manage any interface configured in
> >> /etc/network/interfaces. So all you have to do is configure your
> >> interface with an "iface" stanza in /etc/network/interfaces as
> >> usua
does not manage any interface configured in
/etc/network/interfaces. So all you have to do is configure your
interface with an "iface" stanza in /etc/network/interfaces as usual
so that it is managed by ifupdown and not by NM.
I have had N-M tear down a well configured staticly defin
4.00.
> By default, NM does not manage any interface configured in
> /etc/network/interfaces. So all you have to do is configure your
> interface with an "iface" stanza in /etc/network/interfaces as usual
> so that it is managed by ifupdown and not by NM.
I have had N-
have to do is configure your
interface with an "iface" stanza in /etc/network/interfaces as usual so
that it is managed by ifupdown and not by NM.
john doe wrote:
> I would use mapping stanza instead:
>
> http://manpages.ubuntu.com/manpages/trusty/man5/interfaces.5.html
+1
On Mon, Jul 09, 2018 at 09:32:31AM -0400, Greg Wooledge wrote:
> On Mon, Jul 09, 2018 at 11:20:20PM +1000, Zenaan Harkness wrote:
> > configured to say office, I want to be able to run my reset bash
> > script as follows:
> >
> > reset eth0=internet
>
> I suggest you choose a different name, as
On Mon, Jul 09, 2018 at 11:20:20PM +1000, Zenaan Harkness wrote:
> configured to say office, I want to be able to run my reset bash
> script as follows:
>
> reset eth0=internet
I suggest you choose a different name, as reset(1) is already taken.
If your script is supposed to take two pieces of
face
> > 2. Change the network parameters (either by using sed etc to edit the
> > file or to move 'canned' files in/out of
> > /etc/network/interfaces.d)
> > 3. ifup the interface
> >
> > What I would do, in your situation is to have a set of file
down the interface
> 2. Change the network parameters (either by using sed etc to edit the
> file or to move 'canned' files in/out of
> /etc/network/interfaces.d)
> 3. ifup the interface
>
> What I would do, in your situation is to have a set of files in
> /et
our locations. The leading "!"
character makes the configuration invalid to ifupdown, so will be
ignored. Your script can then rename any files that DON'T have a "!" in
front to do so, then rename the requested file to NOT have a "!" in
front e.g.
#!/bin/bash
etc/network/interfaces.d)
3. ifup the interface
What I would do, in your situation is to have a set of files in
/etc/network/interfaces.d called, for example "!home", "!work",
"!travel" or whatever makes sense for your locations. The leading "!"
chara
/i: ifdown may get confused finding parameters
> there corresponding to the future, not to the current connections.
>
> I use ifupdown myself and have hit few problems so far by doing
> changes after doing the ifdown (and before the ifup, of course :)
Ah yes, that could be possible. I shall in
e "reset" script, like so:
>
> dev=eth0
> ifdown $dev
> ifconfig $dev down
> ifup $dev
Perhaps, just perhaps you should be doing "ifdown $dev" *before*
editing your e/n/i: ifdown may get confused finding parameters
there corresponding to the future, not to the
On Mon 09 Jul 2018 at 11:52:36 (+1000), Zenaan Harkness wrote:
> So I change between two internet connections from time to time.
>
> I use /etc/network/interfaces ("/e/n/i")
>
> When I modify /e/n/i , I then run a little "reset" script, like so:
>
> dev=eth0
> ifdown $dev
> ifconfig $dev down
>
So I change between two internet connections from time to time.
I use /etc/network/interfaces ("/e/n/i")
When I modify /e/n/i , I then run a little "reset" script, like so:
dev=eth0
ifdown $dev
ifconfig $dev down
ifup $dev
Here and there I've had problems.
Recently I discovered the ip command.
;ifup ppp0".
The downside I see though is that if I uncomment the "auto ppp0" I get a
root@mohot:~# ifup ppp0
/usr/sbin/pppd: In file /etc/ppp/peers/alditalk: unrecognized option
'/dev/ttyUSB0'
Failed to bring up ppp0.
root@mohot:~#
I suspect it is because at the time
Le 16/08/2016 à 22:07, Rick Thomas a écrit :
On Aug 16, 2016, at 12:59 AM, Pascal Hambourg wrote:
iface eth0 inet6 static
address 2001:1234:2d2:1:f2ad:4eff:fe00:3077
netmask 64
This IPv6 address looks like an autoconfigured address calculated
from the MAC address. You should n
Thanks Pascal!
On Aug 16, 2016, at 12:59 AM, Pascal Hambourg wrote:
> Le 16/08/2016 à 09:03, Rick Thomas a écrit :
>>
>> Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces...
>> Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on
>> /run/network/ifstate.eth0
>>
Le 16/08/2016 à 09:03, Rick Thomas a écrit :
Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces...
Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on
/run/network/ifstate.eth0
Aug 14 17:02:49 sheeva ifup[893]: RTNETLINK answers: File exists
"RTNETLINK answe
Hi Thomas,
yes, had this problem some time ago, but forgot about the reason. I believe,
it was something with my network settings and network-manager.
Your interfaces looks strange, is this correct? See my comments at your
configuration, but maybe I am wrong:
> Anybody else seen this? (Submitte
Anybody else seen this? (Submitted as Bug#834376)
Updated to latest debian Sid
After boot is completed we see:
rbthomas@sheeva:~$ systemctl status networking.service
* networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor
pr
On 13/01/16 12:31, Maciej Wołoszyn wrote:
Hi,
On my Stretch system updating ifupdown conflicts with systemd.
I removed ifupdown.
I got network problems (no loopback) so I wanted to reinstall ifupdown,
with no luck.
In my case, aptitude suggested removing ifupdown and replacing
it by ifupdown2
On Thu, 14 Jan 2016 08:25:45 +
Joe wrote:
> On Wed, 13 Jan 2016 16:59:19 +0300
> Adam Wilson wrote:
>
> > On Wed, 13 Jan 2016 13:31:30 +0100
> > Maciej Wołoszyn wrote:
> >
> > > Hi,
> > >
> > > > On my Stretch system up
On Wed, 13 Jan 2016 16:59:19 +0300
Adam Wilson wrote:
> On Wed, 13 Jan 2016 13:31:30 +0100
> Maciej Wołoszyn wrote:
>
> > Hi,
> >
> > > On my Stretch system updating ifupdown conflicts with systemd.
> > > I removed ifupdown.
> > > I g
Thanks for the explanation. Now I see that my question came simply from the
misinterpreted aptitude's suggestion to remove ifupdown and install ifupdown2.
I made a mistake to assume that ifupdown2 is intended to replace ifupdown, and
to think that successful install of ifupdown2 (which i
On Wed, 13 Jan 2016 13:31:30 +0100
Maciej Wołoszyn wrote:
> Hi,
>
> > On my Stretch system updating ifupdown conflicts with systemd.
> > I removed ifupdown.
> > I got network problems (no loopback) so I wanted to reinstall
> > ifupdown, with no luck.
>
>
> I tried ifupdown2, but at the moment I get only an ip address with dhcp. The
> entries in /etc/network/interfaces are completely igored. Installing
> ifupdown2
> does not make any difference.
>
>> There is no bug.
>> Simply wait until matching versions of syste
On 2016-01-13 16:00:55 +0100, Hans wrote:
> I think, it is very unlucky, to release systremd with these bad dependencies.
> I hope, the dependencies will be fixed as soon as possible or a big warning
> should appear, as network is really an essential function.
The problem is not the dependencies
On 13/01/16 15:00, Hans wrote:
I think, it is very unlucky, to release systremd with these bad dependencies.
I hope, the dependencies will be fixed as soon as possible or a big warning
should appear, as network is really an essential function.
Your warning of these problems is simple: it is the
ip address with dhcp. The
entries in /etc/network/interfaces are completely igored. Installing ifupdown2
does not make any difference.
> There is no bug.
> Simply wait until matching versions of systemd and ifupdown arrive in
> testing. Up until then, hold back with the update, i.e. be cautio
Am 13.01.2016 um 13:31 schrieb Maciej Wołoszyn:
> Hi,
>
>> On my Stretch system updating ifupdown conflicts with systemd.
>> I removed ifupdown.
>> I got network problems (no loopback) so I wanted to reinstall ifupdown,
>> with no luck.
>
> In my case, apti
Hi,
> On my Stretch system updating ifupdown conflicts with systemd.
> I removed ifupdown.
> I got network problems (no loopback) so I wanted to reinstall ifupdown,
> with no luck.
In my case, aptitude suggested removing ifupdown and replacing
it by ifupdown2 ('ifupdown rewritt
Hello,
On my Stretch system updating ifupdown conflicts with systemd.
I removed ifupdown.
I got network problems (no loopback) so I wanted to reinstall ifupdown,
with no luck.
I tried to remove systemd and did not fully succeed, now I get no
login after a reboot.
Booting in safe mode does not
On Wed 04 Feb 2015 at 02:16:48 +0300, Darren Baginski wrote:
> I have been installed Debian Jessie using pressed, after successful
> install and reboot I realized that eth0 is down and ifupdown package
> was missing. Why ?
> Same preseed file on wheezy installs ifupdown by default.
On 02/03/2015 06:16 PM, Darren Baginski wrote:
Looks like iproute2 was installed which
a) conflicts with ifupdown for some reason (why ? I guess it functionally can
replace older iproute )
b) can't initiate interfaces alone (perhaps jessie is using newer network
initialization method of
Hello!
I have been installed Debian Jessie using pressed, after successful install and
reboot I realized that eth0 is down and ifupdown package was missing. Why ?
Same preseed file on wheezy installs ifupdown by default.
Then I tried to do
root@localhost:~# apt-get install ifupdown
Reading
Hi,
On Thu, Sep 04, 2014 at 09:00:01PM -0400, Podrigal, Aron wrote:
> On Thu, Sep 4, 2014 at 2:17 PM, Brian wrote:
>
> > On Thu 04 Sep 2014 at 14:06:28 -0400, Podrigal, Aron wrote:
> >
> > > I had experienced some difficulties using ifupdown in the past, I than
>
On Thu, Sep 4, 2014 at 2:17 PM, Brian wrote:
> On Thu 04 Sep 2014 at 14:06:28 -0400, Podrigal, Aron wrote:
>
> > I had experienced some difficulties using ifupdown in the past, I than
> came
> > across this while searching the web
> >
> http://pureperl.blogspot.c
On Thu 04 Sep 2014 at 14:06:28 -0400, Podrigal, Aron wrote:
> I had experienced some difficulties using ifupdown in the past, I than came
> across this while searching the web
> http://pureperl.blogspot.com/2013/01/the-debian-ifupdown-package-and.html
> my question is, is that st
I had experienced some difficulties using ifupdown in the past, I than came
across this while searching the web
http://pureperl.blogspot.com/2013/01/the-debian-ifupdown-package-and.html
my question is, is that still true? or there was updates to the package
since than?
also what would be a good
On Du, 16 mar 14, 14:04:12, John Magolske wrote:
>
> The issue was that ifupdown was pinned to 0.7.44 :
...
> Taking a look in /etc/apt/preferences I saw this:
>
> Explanation: Pinned by apt-listbugs at Sat Nov 09 17:32:44 -0800 2013
> Explanation: #727073: ifupdow
* Andrei POPESCU [140316 13:12]:
> On Du, 16 mar 14, 10:16:26, John Magolske wrote:
> > For several weeks now when I do `aptitude dist-upgrade` there is:
> >
> > The following packages have unmet dependencies:
> > initscripts : Breaks: ifupdown (< 0
On Du, 16 mar 14, 10:16:26, John Magolske wrote:
> Hi,
>
> For several weeks now when I do `aptitude dist-upgrade` there is:
>
> The following packages have unmet dependencies:
> initscripts : Breaks: ifupdown (< 0.7.46) but 0.7.44 is installed.
> [...]
>
On Sun 16 Mar 2014 at 10:16:26 -0700, John Magolske wrote:
> For several weeks now when I do `aptitude dist-upgrade` there is:
>
> The following packages have unmet dependencies:
> initscripts : Breaks: ifupdown (< 0.7.46) but 0.7.44 is installed.
> [...]
&
On Sun, 2014-03-16 at 10:16 -0700, John Magolske wrote:
> Hi,
>
> For several weeks now when I do `aptitude dist-upgrade` there is:
>
> The following packages have unmet dependencies:
> initscripts : Breaks: ifupdown (< 0.7.46) but 0.7.44 is installed.
> [
1 - 100 of 162 matches
Mail list logo
