[gentoo-user] Is VLAN configuration manual section up to date?

[gentoo-user] Is VLAN configuration manual section up to date?

[Grant Edwards]

Are the VLAN configuration docs up to date?

  http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap10

The reason I ask is that the Gentoo docs talk about using vconfig,
while other distros have dropped vconfig and now use the ip2route 
packages 'ip' command instead:

  http://wiki.archlinux.org/index.php/VLAN
  
Does Gentoo not have issues with udev trying to automagically rename
vlan network interfaces as described in the Arch Linux page?

  http://wiki.archlinux.org/index.php/VLAN#udev_renames_the_virtual_devices
  
-- 
Grant Edwards               grant.b.edwards        Yow! I am a jelly donut.
                                  at               I am a jelly donut.
                              gmail.com            

Re: [gentoo-user] Is VLAN configuration manual section up to date?

[J. Roeleveld]

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]

On 4 February 2014 22:27:03 CET, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>Are the VLAN configuration docs up to date?
>
>http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap10
>
>The reason I ask is that the Gentoo docs talk about using vconfig,
>while other distros have dropped vconfig and now use the ip2route 
>packages 'ip' command instead:
>
>  http://wiki.archlinux.org/index.php/VLAN
>  
>Does Gentoo not have issues with udev trying to automagically rename
>vlan network interfaces as described in the Arch Linux page?
>
>http://wiki.archlinux.org/index.php/VLAN#udev_renames_the_virtual_devices
>  
>-- 
>Grant Edwards               grant.b.edwards        Yow! I am a jelly
>donut.
>                                  at               I am a jelly donut.
>                              gmail.com            

Grant,

I disabled the udev device name randomizer to ensure I keep the eth* names. (I use bonding for the interfaces, don't care about the names as long as they all end up in the same bond)

For the VLANs, I used the examples in the net.example file in the document folder.
It's somewhere in /usr/doc/net..../ (I think. No access to a gentoo install atm)

I think the documentation you pointed at is out-of-date as I don't have to do it like that.

--
Joost

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 1816 bytes --]

Re: [gentoo-user] Is VLAN configuration manual section up to date?

[Stroller]

[-- Attachment #1: Type: text/plain, Size: 273 bytes --]


On Wed, 5 February 2014, at 5:31 am, J. Roeleveld <joost@antarean.org> wrote:
> … 
> I disabled the udev device name randomizer to ensure I keep the eth* names.

LOL. We seem to have a wholly different understanding of what the word "random" means.

Stroller.



[-- Attachment #2: Type: text/html, Size: 666 bytes --]

Re: [gentoo-user] Is VLAN configuration manual section up to date?

[J. Roeleveld]

[-- Attachment #1: Type: text/plain, Size: 712 bytes --]

On 5 February 2014 14:29:41 CET, Stroller <stroller@stellar.eclipse.co.uk> wrote:
>
>On Wed, 5 February 2014, at 5:31 am, J. Roeleveld <joost@antarean.org>
>wrote:
>> … 
>> I disabled the udev device name randomizer to ensure I keep the eth*
>names.
>
>LOL. We seem to have a wholly different understanding of what the word
>"random" means.
>
>Stroller.

On a host with 1 network device, I expext to be able to find it using a single name.
Eth0 is that.

Udev generates a different value based on some weird logic.
That is what I mean with randomizer. As I cannot predict the interface name prior to boot.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 1338 bytes --]

[gentoo-user] Re: Is VLAN configuration manual section up to date?

[Grant Edwards]

On 2014-02-05, J. Roeleveld <joost@antarean.org> wrote:
> On 4 February 2014 22:27:03 CET, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>>Are the VLAN configuration docs up to date?
>>
>>http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap10
>>
>>The reason I ask is that the Gentoo docs talk about using vconfig,
>>while other distros have dropped vconfig and now use the ip2route 
>>packages 'ip' command instead:
[...]
>>Does Gentoo not have issues with udev trying to automagically rename
>>vlan network interfaces as described in the Arch Linux page?

> I disabled the udev device name randomizer to ensure I keep the eth*
> names. (I use bonding for the interfaces, don't care about the names
> as long as they all end up in the same bond)

Rather than bond them together, I'm going to use them as separate
interfaces.  I'm looking for a way to have 8 to 16 Ethernet interfaces
on some cheap old desktop machines. Connecting the motherboard
Ethernet interface to an external managed VLAN switch seems like the
way to go. So I do care what the names are -- we'll see what tricks
udev tries to play.

> For the VLANs, I used the examples in the net.example file in the
> document folder. It's somewhere in /usr/doc/net..../ (I think. No
> access to a gentoo install atm)

Ah, found it:

/usr/share/doc/netifrc-0.1/net.example.bz2

> I think the documentation you pointed at is out-of-date as I don't
> have to do it like that.

Thanks, that's what I suspected.

-- 
Grant Edwards               grant.b.edwards        Yow! ... I want FORTY-TWO
                                  at               TRYNEL FLOATATION SYSTEMS
                              gmail.com            installed within SIX AND A
                                                   HALF HOURS!!!

Re: [gentoo-user] Re: Is VLAN configuration manual section up to date?

[J. Roeleveld]

On 5 February 2014 15:58:22 CET, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>On 2014-02-05, J. Roeleveld <joost@antarean.org> wrote:
>> On 4 February 2014 22:27:03 CET, Grant Edwards
><grant.b.edwards@gmail.com> wrote:
>>
>>>Are the VLAN configuration docs up to date?
>>>
>>>http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap10
>>>
>>>The reason I ask is that the Gentoo docs talk about using vconfig,
>>>while other distros have dropped vconfig and now use the ip2route 
>>>packages 'ip' command instead:
>[...]
>>>Does Gentoo not have issues with udev trying to automagically rename
>>>vlan network interfaces as described in the Arch Linux page?
>
>> I disabled the udev device name randomizer to ensure I keep the eth*
>> names. (I use bonding for the interfaces, don't care about the names
>> as long as they all end up in the same bond)
>
>Rather than bond them together, I'm going to use them as separate
>interfaces.  I'm looking for a way to have 8 to 16 Ethernet interfaces
>on some cheap old desktop machines. Connecting the motherboard
>Ethernet interface to an external managed VLAN switch seems like the
>way to go. So I do care what the names are -- we'll see what tricks
>udev tries to play.

If you only have 1 interface, disable udevs randomizer and use eth0.
When configuring the vlans you can set the names in the config.

--
Joost

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[gentoo-user] Re: Is VLAN configuration manual section up to date?

[Grant Edwards]

On 2014-02-06, J. Roeleveld <joost@antarean.org> wrote:
> On 5 February 2014 15:58:22 CET, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>>On 2014-02-05, J. Roeleveld <joost@antarean.org> wrote:
>>> On 4 February 2014 22:27:03 CET, Grant Edwards
>><grant.b.edwards@gmail.com> wrote:
>>>
>>>>Are the VLAN configuration docs up to date?
>>>>
>>>>http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap10
>>>>
>>>>The reason I ask is that the Gentoo docs talk about using vconfig,
>>>>while other distros have dropped vconfig and now use the ip2route 
>>>>packages 'ip' command instead:
>>[...]
>>>>Does Gentoo not have issues with udev trying to automagically rename
>>>>vlan network interfaces as described in the Arch Linux page?
>>
>>> I disabled the udev device name randomizer to ensure I keep the eth*
>>> names. (I use bonding for the interfaces, don't care about the names
>>> as long as they all end up in the same bond)
>>
>>Rather than bond them together, I'm going to use them as separate
>>interfaces.  I'm looking for a way to have 8 to 16 Ethernet interfaces
>>on some cheap old desktop machines. Connecting the motherboard
>>Ethernet interface to an external managed VLAN switch seems like the
>>way to go. So I do care what the names are -- we'll see what tricks
>>udev tries to play.
>
> If you only have 1 interface, disable udevs randomizer and use eth0.

Good idea.  The machines currently have two interfaces, but if the
vlan+switch setup works, then I can pull the second NIC out.

> When configuring the vlans you can set the names in the config.

Great!  

Thanks.

-- 
Grant Edwards               grant.b.edwards        Yow! over in west
                                  at               Philadelphia a puppy is
                              gmail.com            vomiting ...

Re: [gentoo-user] Re: Is VLAN configuration manual section up to date?

[J. Roeleveld]

[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]

On 6 February 2014 15:31:58 CET, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>On 2014-02-06, J. Roeleveld <joost@antarean.org> wrote:
>> On 5 February 2014 15:58:22 CET, Grant Edwards
><grant.b.edwards@gmail.com> wrote:
>>>On 2014-02-05, J. Roeleveld <joost@antarean.org> wrote:
>>>> On 4 February 2014 22:27:03 CET, Grant Edwards
>>><grant.b.edwards@gmail.com> wrote:
>>>>
>>>>>Are the VLAN configuration docs up to date?
>>>>>
>>>>>http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap10
>>>>>
>>>>>The reason I ask is that the Gentoo docs talk about using vconfig,
>>>>>while other distros have dropped vconfig and now use the ip2route 
>>>>>packages 'ip' command instead:
>>>[...]
>>>>>Does Gentoo not have issues with udev trying to automagically
>rename
>>>>>vlan network interfaces as described in the Arch Linux page?
>>>
>>>> I disabled the udev device name randomizer to ensure I keep the
>eth*
>>>> names. (I use bonding for the interfaces, don't care about the
>names
>>>> as long as they all end up in the same bond)
>>>
>>>Rather than bond them together, I'm going to use them as separate
>>>interfaces.  I'm looking for a way to have 8 to 16 Ethernet
>interfaces
>>>on some cheap old desktop machines. Connecting the motherboard
>>>Ethernet interface to an external managed VLAN switch seems like the
>>>way to go. So I do care what the names are -- we'll see what tricks
>>>udev tries to play.
>>
>> If you only have 1 interface, disable udevs randomizer and use eth0.
>
>Good idea.  The machines currently have two interfaces, but if the
>vlan+switch setup works, then I can pull the second NIC out.
>
>> When configuring the vlans you can set the names in the config.
>
>Great!  
>
>Thanks.
>
>-- 
>Grant Edwards               grant.b.edwards        Yow! over in west
>                               at               Philadelphia a puppy is
>                              gmail.com            vomiting ...

If the switch supports bonding, use that as well.
I have 4 interfaces in a single bond.
On that bond I have the vlans configured.

Helps with the throughput as I have multiple machines pulling data from there connected to the same switch. 

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 3744 bytes --]

[gentoo-user] Re: Is VLAN configuration manual section up to date?

[Grant Edwards]

On 2014-02-06, J. Roeleveld <joost@antarean.org> wrote:

> If the switch supports bonding, use that as well. I have 4 interfaces
> in a single bond. On that bond I have the vlans configured.
>
> Helps with the throughput as I have multiple machines pulling data
> from there connected to the same switch. 

I hadn't thought about that... it doesn't look like the switch I have
at the moment supports bonding.  Since throughput isn't an issue, I
think I'd rather eliminate the complexity of the second/third/etc. NIC
card(s) in the host.  In the past I had run into problems where an OS
upgrade would cause the interface names to swap on some (but not all)
machines. With just a single interface, and udev-name-randomization
disabled, that problem goes away. :)

-- 
Grant Edwards               grant.b.edwards        Yow! Hmmm ... A hash-singer
                                  at               and a cross-eyed guy were
                              gmail.com            SLEEPING on a deserted
                                                   island, when ...

Re: [gentoo-user] Is VLAN configuration manual section up to date?

[Stroller]

On Thu, 6 February 2014, at 3:35 pm, J. Roeleveld <joost@antarean.org> wrote:
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

A google seems to suggest this client is able to send plain-text messages.

Stroller.

Re: [gentoo-user] Is VLAN configuration manual section up to date?

[J. Roeleveld]

On 6 February 2014 22:13:26 CET, Stroller <stroller@stellar.eclipse.co.uk> wrote:
>
>On Thu, 6 February 2014, at 3:35 pm, J. Roeleveld <joost@antarean.org>
>wrote:
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>A google seems to suggest this client is able to send plain-text
>messages.
>
>Stroller.

My apologies.

I had it set to text only. For some reason it changed it to html. (Only just noticed.)

Is it sending correctly now?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Is VLAN configuration manual section up to date?

[Stroller]

On Thu, 6 February 2014, at 9:20 pm, J. Roeleveld <joost@antarean.org> wrote:
>> 
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> 
>> A google seems to suggest this client is able to send plain-text
>> messages.
> 
> My apologies.
> 
> I had it set to text only. For some reason it changed it to html. (Only just noticed.)
> 
> Is it sending correctly now?

It does now indeed seem to be, yes.

Thank you.

Stroller.