It's not impossible already to do VLANs with d-i currently (for anyone
reading this after a temporary work around until this is properly fixed)...
Step 1) Get to the screen where d-i presents you with a list of network
interfaces
Step 2) Go to VT2 (using alt-F2) and activate the console
Step
On Mon, May 27, 2024 at 2:02 PM Tyler Stachecki
wrote:
>
> On Thu, Feb 22, 2024 at 09:16:24AM +0100, Lucas Bonnet wrote:
> >
> > Hello dear Debian maintainers,
> >
> > I can confirm that the 2020 patch from Carsten Schoenert still applies
> > to d-i/netcfg releases 1.187 and 1.188, and result in a
On Thu, Feb 22, 2024 at 09:16:24AM +0100, Lucas Bonnet wrote:
>
> Hello dear Debian maintainers,
>
> I can confirm that the 2020 patch from Carsten Schoenert still applies
> to d-i/netcfg releases 1.187 and 1.188, and result in a debian installer
> that knows about VLANs and can be fully automate
Hello dear Debian maintainers,
I can confirm that the 2020 patch from Carsten Schoenert still applies
to d-i/netcfg releases 1.187 and 1.188, and result in a debian installer
that knows about VLANs and can be fully automated with a preseed config
like the following:
d-i netcfg/enable
[image: image.png]
[image: image.png]
Hi there,
it's long ago this issue was opened and some working code was added by
patches. :-)
On Mon, Jun 27, 2016 at 02:13:33PM +, Holger Levsen wrote:
> the server is located in a loud+dusty+dark room, has 4 ethernet devices
> and it seems I mixed them up…
On my day job we now hit exactly
Control: tags -1 - pending
This bug about adding vlan support has a patch, however nothing has been applied
yet.
Thus I'm removing the pending tag.
Holger
--
Holger Wansing
PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Hi,
Has this patch already been accepted? Any more info on how to use it, in
that case?
--
Kind regards / Met vriendelijke groet,
Tim Stoop
Kumina bv
www.kumina.nl
kvk nr 14095795
On Mon, Jun 27, 2016 at 02:05:53PM +0200, Ben Hutchings wrote:
> I've never heard of that situation before.
I think you have: PEBKAC :)
the server is located in a loud+dusty+dark room, has 4 ethernet devices
and it seems I mixed them up…
> Which hardware is this?
> Where is the need for firmwa
On Mon, 2016-06-27 at 11:54 +, Holger Levsen wrote:
> Hi,
>
> I've installed Debian jessie in a setup yesterday, where I needed to use
> vlan, so I was very happy when I saw that this bug has a patch.
>
> However, the network card I used works nicely for configurations without
> vlans without
Hi,
I've installed Debian jessie in a setup yesterday, where I needed to use
vlan, so I was very happy when I saw that this bug has a patch.
However, the network card I used works nicely for configurations without
vlans without loading additional firmware, while it needs a non free
firmware to su
On Fri, Apr 15, 2016 at 03:17:00AM +0100, Dimitri John Ledkov wrote:
> ---
>
> Changes since last version:
> - Corrected Philipp's name
> - Adjusted vlan_failed text message
> - Adding a di_error if vlan_id is preseeded and not supported
> - Added NetworkManager vlan type
> - Sent templates
---
Changes since last version:
- Corrected Philipp's name
- Adjusted vlan_failed text message
- Adding a di_error if vlan_id is preseeded and not supported
- Added NetworkManager vlan type
- Sent templates for review
Makefile | 2 +-
debian/changelog
Hi,
On Tue, Apr 05, 2016 at 10:57:07PM +0100, Dimitri John Ledkov wrote:
> Squished all the patches, and hopefully did the multi-sided merge of
> Yun's, Pkern's, mine and extra debug stuff. This starts to look
> reasonable. Successfully tested this on s390x, and I'm glad I did it
> there, as I
---
Squished all the patches, and hopefully did the multi-sided merge of
Yun's, Pkern's, mine and extra debug stuff. This starts to look
reasonable. Successfully tested this on s390x, and I'm glad I did it
there, as I had to fix up the s390x specific code path too.
I do believe it should be
If only I had had a test environment to test my rewrite against, oh
well.
On Wed, Mar 30, 2016 at 05:18:11PM +0100, Dimitri John Ledkov wrote:
> +Template: netcfg/use_vlan
> +Type: boolean
> +Default: false
> +# :sl6:
> +_Description: Are you configuring on an IEEE 802.1Q VLAN trunk port?
> + Virt
On Wed, 2016-03-30 at 10:26 -0400, Lennart Sorensen wrote:
> On Wed, Mar 30, 2016 at 03:11:03PM +0100, Dimitri John Ledkov wrote:
> >
> > Hi,
> >
> > On Sat, 12 Mar 2016 13:49:57 +0100 Tom H wrote:
> > >
> > > You don't need vlan; iproute2's ip can do it:
> > >
> > > ip link add link eth0 name
---
debian/changelog | 1 +
vlan.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 7b7aebe..941c16d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -15,6 +15,7 @@ netcfg (1.138) UNRELEASED; urgency=medium
* All of above resolves
---
debian/changelog | 2 ++
netcfg-common.c | 1 +
netcfg.h | 3 +++
vlan.c| 16
write_interface.c | 15 +++
5 files changed, 21 insertions(+), 16 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 2a5e4e6..7b7aebe 100644
-
---
Makefile | 2 +-
debian/changelog | 3 ++
debian/netcfg-common.templates | 34 +++--
netcfg.c | 5
netcfg.h | 2 ++
vlan.c | 67 +
On Wed, Mar 30, 2016 at 03:11:03PM +0100, Dimitri John Ledkov wrote:
> Hi,
>
> On Sat, 12 Mar 2016 13:49:57 +0100 Tom H wrote:
> > You don't need vlan; iproute2's ip can do it:
> >
> > ip link add link eth0 name vlan9 type vlan id 9
> > or
> > ip link add link eth0 name eth0.9 type vlan id 9
> >
Hi,
On Sat, 12 Mar 2016 13:49:57 +0100 Tom H wrote:
> You don't need vlan; iproute2's ip can do it:
>
> ip link add link eth0 name vlan9 type vlan id 9
> or
> ip link add link eth0 name eth0.9 type vlan id 9
>
>
I know that. vlan package is needed for the ifupdown hooks to parse
vlan stanza from
You don't need vlan; iproute2's ip can do it:
ip link add link eth0 name vlan9 type vlan id 9
or
ip link add link eth0 name eth0.9 type vlan id 9
Hello,
On Wed, 27 Mar 2013 22:10:51 +0800 YunQiang Su wrote:
> Thanks for Zhengpeng Hou, who points out that I leave a piece of code which is
> not used anymore in this patch. This piece of code make a more malloc while
> not
> free.
>
> And I refresh this patch with the current git.
> This is t
Tim Stoop (2014-10-29):
> Hi,
>
> We're really interested in this, where should we look for a status
> update? I still do not see an option for it in the installer for Wheezy,
> so I guess it's not done yet. Will it be present for Jessie? Anything we
> can do to help?
Philipp, any news on your s
Hi,
We're really interested in this, where should we look for a status
update? I still do not see an option for it in the installer for Wheezy,
so I guess it's not done yet. Will it be present for Jessie? Anything we
can do to help?
--
Kind regards,
Met vriendelijke groet,
Tim Stoop
Kumina bv
ww
Thanks for Zhengpeng Hou, who points out that I leave a piece of code which is
not used anymore in this patch. This piece of code make a more malloc while not
free.
And I refresh this patch with the current git.
This is the new patch.
Any one has progress on rewriting it?
vlan_new.diff
Descript
Hello,
(putting back Luca in the loop just in case)
Philipp Kern (29/12/2012):
> On Sat, Dec 29, 2012 at 08:34:27AM +0100, Christian PERRIER wrote:
> > Taking over KiBi's hat, I would say there is no chance this makes
> > it to wheezy. And taking mine, too, with several addition to
> > localizat
On Sat, Dec 29, 2012 at 4:37 AM, Philipp Kern wrote:
> On Sat, Dec 29, 2012 at 03:41:33AM +0800, Aron Xu wrote:
>> The Linux kernel's vlan udeb is added in linux/3.2.35-1, so there is
>> no outside thing to block us from adding vlan support to netcfg, can
>> anyone review the patch?
>
> It needs a
On Sat, Dec 29, 2012 at 08:34:27AM +0100, Christian PERRIER wrote:
> Taking over KiBi's hat, I would say there is no chance this makes it
> to wheezy. And taking mine, too, with several addition to localization
> bits. The debconf templates need minor edits to compleltely fit with
> the writing sty
Quoting Philipp Kern (pk...@debian.org):
> On Sat, Dec 29, 2012 at 03:41:33AM +0800, Aron Xu wrote:
> > The Linux kernel's vlan udeb is added in linux/3.2.35-1, so there is
> > no outside thing to block us from adding vlan support to netcfg, can
> > anyone review the patch?
>
> It needs a rewrite,
On Sat, Dec 29, 2012 at 03:41:33AM +0800, Aron Xu wrote:
> The Linux kernel's vlan udeb is added in linux/3.2.35-1, so there is
> no outside thing to block us from adding vlan support to netcfg, can
> anyone review the patch?
It needs a rewrite, IMHO. I started reviewing / rewriting it, but I'm no
Hi,
The Linux kernel's vlan udeb is added in linux/3.2.35-1, so there is
no outside thing to block us from adding vlan support to netcfg, can
anyone review the patch?
--
Regards,
Aron Xu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
I patched vlan to work with VLAN for linux and kfreebsd now.
While I have no idea whether we should load 8021q module manually.
I seems that 8021q module is not included in d-i (Linux).
Thanks for Aron Xu to write the templates.
--
YunQiang Su
vlan.diff
Description: Binary data
Hi,
On Sun, Sep 9, 2012 at 11:47 PM, Gaudenz Steinlin wrote:
>
> Hi Aron
>
> Aron Xu writes:
>
>> I'm sending a reminder on this issue, it would be best if d-i can
>> support VLAN using expert mode of installation, configuring VLAN using
>> iproute2 during installation is much more annoying comp
Hi Aron
Aron Xu writes:
> I'm sending a reminder on this issue, it would be best if d-i can
> support VLAN using expert mode of installation, configuring VLAN using
> iproute2 during installation is much more annoying comparing to
> configure it within d-i.
A reminder is nice and if you are lu
I'm sending a reminder on this issue, it would be best if d-i can
support VLAN using expert mode of installation, configuring VLAN using
iproute2 during installation is much more annoying comparing to
configure it within d-i.
--
Regards,
Aron Xu
--
To UNSUBSCRIBE, email to debian-bugs-dist-req
Hi,
On Sat Jan 09, 2010 at 14:04:51 +0100, Frans Pop wrote:
> On Saturday 09 January 2010, Ferenc Wagner wrote:
> > It would be less of a problem if d-i used the Busybox ip applet
>
> It does (and nothing else).
>
> > *and* if that supported VLANs.
>
> That might be an issue. No idea.
~ # ip
On Saturday 09 January 2010, Ferenc Wagner wrote:
> It would be less of a problem if d-i used the Busybox ip applet
It does (and nothing else).
> *and* if that supported VLANs.
That might be an issue. No idea.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subje
Robert LeBlanc writes:
> I too have been bitten by this. For as flexible as the Debian Installer is
> and everything you can do, it's pretty disappointing that it can't do VLANs.
> A lot of enterprises use VLANs, and it seems it would be important to have
> VLAN support to install Debian. It's no
I too have been bitten by this. For as flexible as the Debian Installer is
and everything you can do, it's pretty disappointing that it can't do VLANs.
A lot of enterprises use VLANs, and it seems it would be important to have
VLAN support to install Debian. It's no fun to reconfigure the network j
Hi,
I would really love to see vlan support in DI.
I just had a box with vlans connected already and wanted to install
debian with latest lenny installer but couldn't because of the lack of
vlan support.
I'd prefer to have proper deb-conf vlan support, if possible. Shouldn't
be too hard.
On Wed, Jul 18, 2007 at 07:15:29PM +0200, Geert Stappers wrote:
> Op 17-07-2007 om 16:53 schreef Luca Filipozzi:
> > Package: debian-installer
>
> meanwhile reassigned to netcfg
It depends on which level we support vlans. I see two options:
* full support with the debconf questions and proper s
Op 17-07-2007 om 16:53 schreef Luca Filipozzi:
> Package: debian-installer
meanwhile reassigned to netcfg
> vlan support in the installer would avoid this reconfiguration.
Where to find more information about vlan support?
(Please provide pointer to vlan support in debian)
Cheers
Geert Stapper
Package: debian-installer
Severity: wishlist
Please consider adding vlan support to debian-installer. There are
cases (edge cases, admitedly) where machines and switches have been
configured to use vlan tagging. A reinstall of these machines requires
a network reconfiguration. vlan support in t
46 matches
Mail list logo
