From: t.berthel@gmx.net
To: documentation@lists.ipfire.org
Subject: Aw: Re: VLAN Konfig
Date: Mon, 10 Jun 2013 12:46:54 +0200 [thread overview]
Message-ID: <trinity-f78fe872-6384-41ed-a184-5858811fca3f-1370861214351@3capp-gmx-bs48> (raw)
In-Reply-To: <1370859758.11840.91.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]
Hi,
> very nice illustration and colouring :)
thx! :)
> For some reason, you are writing a new script a little bit later which
> manually creates the virtual interfaces. Why is that?
You mean this section: /etc/rc.d/rc3.d/S18network-vlan ?
I have tested VLAN to configurate only in /var/ipfire/ethernet/vlans. There have no createt the Interfaces for blue & orange.
Therefore I have made it so.
> That's not good practice, I know. But it's the way it is at the moment.
I can remind me to the statement. But it works only once.
The BLUE_PARENT_DEV="green0" and in /var/ipfire/ethernet/settings delegate to BLUE_DEV=green0.300, i can test it with blue0.300. let's see what happens here. :) I give a statement when testet.
BG, Thomas
> Gesendet: Montag, 10. Juni 2013 um 12:22 Uhr
> Von: "Michael Tremer" <michael.tremer(a)ipfire.org>
> An: documentation(a)lists.ipfire.org
> Betreff: Re: VLAN Konfig
>
> Hey Thomas,
>
> very nice illustration and colouring :)
>
> But I got some questions:
>
> The part about the configuration file /var/ipfire/ethernet/vlans looks
> right for me.
> For some reason, you are writing a new script a little bit later which
> manually creates the virtual interfaces. Why is that?
> According to you configuration in /var/ipfire/ethernet/vlans, a new
> blue0 and orange0 interface will show up after reboot.
>
> It is very convenient to name the devices blue0, green0, orange0 and
> red0, because some scripts rely on those names. That's not good
> practice, I know. But it's the way it is at the moment.
>
> Then, why all that iptables stuff? I cannot see how this is relevant for
> the VLANs in general.
>
> -Michael
>
> On Sat, 2013-06-08 at 13:42 +0200, Thomas Berthel wrote:
> > Hi zusammen,
> >
> > ich habe hier: http://wiki.ipfire.org/de/optimization/vlan/start die
> > Doku für das VLAN fertig gestellt, könnte das jemand von euch in ein
> > brauchbares Format für die englisch sprechenden Uer vorbereiten.
> > Korregturen dürfen natürlich ebenso vorgenommen werden ;-)
> >
> >
> > Ein schönes Wochenende! Thomas
> > _______________________________________________
> > Documentation mailing list
> > Documentation(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/documentation
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
>
next prev parent reply other threads:[~2013-06-10 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 11:42 Thomas Berthel
2013-06-09 4:54 ` Erik K.
2013-06-09 7:37 ` Thomas Berthel
2013-06-10 10:22 ` Michael Tremer
2013-06-10 10:46 ` t.berthel [this message]
2013-06-11 12:42 ` Aw: " t.berthel
2013-06-13 9:45 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-f78fe872-6384-41ed-a184-5858811fca3f-1370861214351@3capp-gmx-bs48 \
--to=t.berthel@gmx.net \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox