Hi.
On Mon, Apr 13, 2015 at 09:13:43AM +0200, albcares wrote:
> could I suggest wicd, instead? I mean, You could download-and-install it
> through the time of running connection, and manage your needs with it. I must
> warn
> that could be a conflict with NetworkManager, so you have to chose.
On Monday 13 April 2015 08:13:43 albcares wrote:
> could I suggest *wicd*, instead? I mean, You could download-and-install it
> through the time of running connection, and manage your needs with it. I
> must warn that could be a conflict with NetworkManager, so you have to
> chose.
I was asking ab
could I suggest *wicd*, instead? I mean, You could download-and-install it
through the time of running connection, and manage your needs with it. I
must warn that could be a conflict with NetworkManager, so you have to
chose.
yours sincerely
ac
2015-04-12 23:10 GMT+02:00 Lisi Reisz :
> On Saturda
On Saturday 11 April 2015 04:50:12 M7 wrote:
> i can manually bring it up using vconfig add eth0 4 and have access. Upon
> reboot, ifconfig only shows me lo interface.
>
> Any help would be appreciated!
Have you got NetworkManager running?
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@l
M7 wrote:
> I'm running Debian 7.8 x64 and I'm unable to have my vlan network persist.
> I've installed the package 'vlan'.
You don't need this package. Please remove and purge it. ifupdown is
able to configure VLANs without this package.
> I then ran 'modprobe 8021q' to load the kernel and sa
2015-04-11 05:50 keltezéssel, M7 írta:
> My /etc/network/interfaces looks like this
>
> auto-hotplug eth0.4
There is 'auto' keyword or 'allow-hotplug' but no auto-hotplug.
> iface eth0.4 inet static
>address 10.0.4.100
>netmask 255.255.255.0
>gateway 10.0.4.1
>dns-nameserver 10.
Bonno Bloksma wrote:
> Hi Sven,
>>> What I do NOT want is to have names like eth0.60 for vlan.60
>>> incoming on interface eth0. Because if I decide it would be better
>>> to have vlan60 come in on eth1 I would have to rename all (firewall,
>>> etc.) scripts that refer to that name.
>>> What I w
Hi Sven,
>> What I do NOT want is to have names like eth0.60 for vlan.60 incoming
>> on interface eth0. Because if I decide it would be better to have
>> vlan60 come in on eth1 I would have to rename all (firewall, etc.)
>> scripts that refer to that name.
>> What I would like to have is names
Hi Darac
>> What I do NOT want is to have names like eth0.60 for vlan.60 incoming on
>> interface eth0.
>> Because if I decide it would be better to have vlan60 come in on eth1 I
>> would have to rename all (firewall, etc.) scripts that refer to that name.
>>
>> What I would like to have is nam
Bonno Bloksma wrote:
> What I do NOT want is to have names like eth0.60 for vlan.60 incoming
> on interface eth0. Because if I decide it would be better to have
> vlan60 come in on eth1 I would have to rename all (firewall, etc.)
> scripts that refer to that name.
> What I would like to have is
On Fri, Mar 22, 2013 at 02:27:13PM +, Bonno Bloksma wrote:
> Hi,
>
> I am going to implement vlans on my Linux router. Have been reading about
> this about from when Squeeze was released and was ready to take the plunge
> today when I read this: http://wiki.defcon.no/guides/debian/vlan
> See
On Sun, 13 Apr 2008 20:57:51 +0100
Steve Kemp <[EMAIL PROTECTED]> wrote:
> On Sun Apr 13, 2008 at 12:52:12 -0700, Amit Uttamchandani wrote:
>
> > * VLAN support has been integrated into Linux Kernel since 2.4.14.
>
> Yes.
>
> > * Not all network cards support VLAN tagging. How do I find out
On Sun Apr 13, 2008 at 12:52:12 -0700, Amit Uttamchandani wrote:
> * VLAN support has been integrated into Linux Kernel since 2.4.14.
Yes.
> * Not all network cards support VLAN tagging. How do I find out if it does?
Try it and see?
> * Configuring VLAN is done through the 'vconfig' pro
On Sun Apr 13, 2008 at 13:15:36 -0700, Amit Uttamchandani wrote:
> I should have put in more details of what I've done.
> I apologize.
No problem, and you're welcome. You were just unlucky enough to
receive that section of my mail.
There have been lots of queries recently with people say
On 2008-04-13T12:52:12-0700, Amit Uttamchandani wrote:
> * Not all network cards support VLAN tagging. How do I find out if it does?
Look at the hardware specifications published by vendor, or failing that look
at the retail specifications.
> * Configuring VLAN is done through the 'vconfig' pro
15 matches
Mail list logo
