Re: RTL8812/8821 network cards

[Michael Milliman]

On 06/02/2017 04:03 AM, Michael Lange wrote:
> Hi,
> 
> On Thu, 1 Jun 2017 19:34:20 -0500
> Michael Milliman  wrote:
> 
>> Have you tried the package firmware-realtek??  I'm not absolutely
>> positive that the drivers available in this package will work with your
>> specific 8812/8821 chipset (there are more than one), but it does have
>> drivers for some 8812/8821 chipsets that may work.
> 
> from a quick glance at the page the OP has linked I doubt that any of the
> drivers that are currently included in the linux kernel will work with
> this chipset if you just add some firmware file(s), I guess this is the
> reason why the developers bothered to write that driver ;)
> 
> I have here a similar problem with a realtek8723bs chipset, the 8723ae
> and 8723be drivers are no good for that one.
> 
I've had a similar problem in the past (quite some time ago).  AIR, I
had to do some searching to find a driver that would compile under
Debian and install it myself.  I haven't used the device that required
that in quite a while, and it is not needed on my current system, but I
think that a usable driver did eventually find its way into the
Debian distribution.  One of the side-effects of Debian policy is that
it takes quite a while for these things to work their way through the
system to the distro.
>>From what the project page suggests, building and installing the 8821au
> driver seems to be easy enough (no patches and no additional firmware
> files required) so I think it should be possible to build a debian
> package which could be added to a custom debian iso.
> 
>>From what the OP writes however I am not sure if they meant to include the
> driver in the official debian distro instead. This would surely require
> the driver to be added to the official kernel first. Even if this happens
> there is no guarantee that debian will include it in their kernel
> packages (as is currently the case with the rtl8723bs driver which
> finally made it into the kernel but is not included in debian's 4.11
> kernel package).
> 
> Regards
> 
> Michael
> 
> 
>>
>> On 06/01/2017 05:49 PM, Jessica Litwin wrote:
>>>
>>>
>>> On Thu, Jun 1, 2017 at 6:31 PM, Wei-Shun Lo >> > wrote:
>>>
>>> Dear Debian,
>>>
>>> Is it possible to include below driver in the kernel for network
>>> installation?  
>>> Many cards are using this driver.
>>>
>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>> 
>>>
>>> Best regards,
>>> Ralic 
>>> -- 
>>> 
>>> ************************************
>>> * _Contact Info_
>>> ** *
>>>  *US Mobile: 1-408-609-7628 >> 20609-7628>   * 
>>> Em
>>> ail: rali...@gmail.com
>>>  Line/ Skype :
>>> ralic_lo
>>> ************************************
>>> *
>>>
>>> *
>>>
>>>
>>>
>>> In the past I have made my own ISOs and included the contents of
>>> linux-firmware. Perhaps this may be something you can do also?
>>>
>>> // jkl
>>
>> -- 
>> 73's,
>> WB5VQX -- The Very Quick X-ray
>>
>>
> 
> 
> 
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
> 
> Uncontrolled power will turn even saints into savages.  And we can all
> be counted on to live down to our lowest impulses.
>   -- Parmen, "Plato's Stepchildren", stardate 5784.3
> 

-- 
73's,
WB5VQX -- The Very Quick X-ray

Re: RTL8812/8821 network cards

[Greg Wooledge]

On Thu, Jun 01, 2017 at 10:53:08PM +, Wei-Shun Lo wrote:
> Yes, that is possible, however this card is supplied as a nano USB card
> that enable old computers that had no wifi card, so I would like to make a
> suggestion to include this card's firmware to Debian live's image.

Oh, you want it in debian-live, not in Debian.

The debian-live mailing list's web page is
.  I'd suggest posting debian-live
requests to that mailing list, instead of this one.

Re: RTL8812/8821 network cards

[Michael Lange]

Hi,

On Thu, 1 Jun 2017 19:34:20 -0500
Michael Milliman  wrote:

> Have you tried the package firmware-realtek??  I'm not absolutely
> positive that the drivers available in this package will work with your
> specific 8812/8821 chipset (there are more than one), but it does have
> drivers for some 8812/8821 chipsets that may work.

from a quick glance at the page the OP has linked I doubt that any of the
drivers that are currently included in the linux kernel will work with
this chipset if you just add some firmware file(s), I guess this is the
reason why the developers bothered to write that driver ;)

I have here a similar problem with a realtek8723bs chipset, the 8723ae
and 8723be drivers are no good for that one.

>From what the project page suggests, building and installing the 8821au
driver seems to be easy enough (no patches and no additional firmware
files required) so I think it should be possible to build a debian
package which could be added to a custom debian iso.

>From what the OP writes however I am not sure if they meant to include the
driver in the official debian distro instead. This would surely require
the driver to be added to the official kernel first. Even if this happens
there is no guarantee that debian will include it in their kernel
packages (as is currently the case with the rtl8723bs driver which
finally made it into the kernel but is not included in debian's 4.11
kernel package).

Regards

Michael


> 
> On 06/01/2017 05:49 PM, Jessica Litwin wrote:
> > 
> > 
> > On Thu, Jun 1, 2017 at 6:31 PM, Wei-Shun Lo  > > wrote:
> > 
> > Dear Debian,
> > 
> > Is it possible to include below driver in the kernel for network
> > installation?  
> > Many cards are using this driver.
> > 
> > https://github.com/abperiasamy/rtl8812AU_8821AU_linux
> > 
> > 
> > Best regards,
> > Ralic 
> > -- 
> > 
> > ************************************
> > * _Contact Info_
> > ** *
> >  *US Mobile: 1-408-609-7628  > 20609-7628>   * 
> > Em
> > ail: rali...@gmail.com
> >  Line/ Skype :
> > ralic_lo
> > ************************************
> > *
> > 
> > *
> > 
> > 
> > 
> > In the past I have made my own ISOs and included the contents of
> > linux-firmware. Perhaps this may be something you can do also?
> > 
> > // jkl
> 
> -- 
> 73's,
> WB5VQX -- The Very Quick X-ray
> 
> 



.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Uncontrolled power will turn even saints into savages.  And we can all
be counted on to live down to our lowest impulses.
-- Parmen, "Plato's Stepchildren", stardate 5784.3

Re: RTL8812/8821 network cards

[Michael Milliman]

Have you tried the package firmware-realtek??  I'm not absolutely
positive that the drivers available in this package will work with your
specific 8812/8821 chipset (there are more than one), but it does have
drivers for some 8812/8821 chipsets that may work.

On 06/01/2017 05:49 PM, Jessica Litwin wrote:
> 
> 
> On Thu, Jun 1, 2017 at 6:31 PM, Wei-Shun Lo  > wrote:
> 
> Dear Debian,
> 
> Is it possible to include below driver in the kernel for network
> installation?  
> Many cards are using this driver.
> 
> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
> 
> 
> Best regards,
> Ralic 
> -- 
> 
> ************************************
> * _Contact Info_** 
>*
>  *US Mobile: 1-408-609-7628    *
>  
> Em
> ail: rali...@gmail.com  
>  Line/ Skype : ralic_lo
> 
> ************************************
> *
> 
> *
> 
> 
> 
> In the past I have made my own ISOs and included the contents of
> linux-firmware. Perhaps this may be something you can do also?
> 
> // jkl

-- 
73's,
WB5VQX -- The Very Quick X-ray

Re: RTL8812/8821 network cards

[Wei-Shun Lo]

Dear Jessica,

Yes, that is possible, however this card is supplied as a nano USB card
that enable old computers that had no wifi card, so I would like to make a
suggestion to include this card's firmware to Debian live's image.

Best,
Ralic

On Thu, Jun 1, 2017 at 3:50 PM Jessica Litwin  wrote:

> On Thu, Jun 1, 2017 at 6:31 PM, Wei-Shun Lo  wrote:
>
>> Dear Debian,
>>
>> Is it possible to include below driver in the kernel for network
>> installation?
>> Many cards are using this driver.
>>
>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>
>> Best regards,
>> Ralic
>> --
>> ************************
>> ************
>> * Contact Info*
>>
>>  *US Mobile: 1-408-609-7628 <(408)%20609-7628>   *
>>
>> Em
>> ail: rali...@gmail.com
>>  Line/ Skype : ralic_lo
>> ************************
>> ************
>>
>>
>>
>
> In the past I have made my own ISOs and included the contents of
> linux-firmware. Perhaps this may be something you can do also?
>
> // jkl
>
-- 
************************
************
* Contact Info*
 *US Mobile: 1-408-609-7628   *

Em
ail: rali...@gmail.com
 Line/ Skype : ralic_lo
************************
************

Re: RTL8812/8821 network cards

[Jessica Litwin]

On Thu, Jun 1, 2017 at 6:31 PM, Wei-Shun Lo  wrote:

> Dear Debian,
>
> Is it possible to include below driver in the kernel for network
> installation?
> Many cards are using this driver.
>
> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>
> Best regards,
> Ralic
> --
> ************************
> ************
> * Contact Info*
>
>  *US Mobile: 1-408-609-7628 <(408)%20609-7628>   *
>
> Em
> ail: rali...@gmail.com
>  Line/ Skype : ralic_lo
> ************************
> ************
>
>
>

In the past I have made my own ISOs and included the contents of
linux-firmware. Perhaps this may be something you can do also?

// jkl

RTL8812/8821 network cards

[Wei-Shun Lo]

Dear Debian,

Is it possible to include below driver in the kernel for network
installation?
Many cards are using this driver.

https://github.com/abperiasamy/rtl8812AU_8821AU_linux

Best regards,
Ralic
-- 
************************
************
* Contact Info*
 *US Mobile: 1-408-609-7628   *

Em
ail: rali...@gmail.com
 Line/ Skype : ralic_lo
************************
************

Driver for Realtek network cards

[Wei-Shun Lo]

Dear Debian,

Is it possible to include below driver in the kernel for network

https://github.com/abperiasamy/rtl8812AU_8821AU_linux

Best regards,
Ralic
-- 
************************
************
* Contact Info*
 *US Mobile: 1-408-609-7628   *

Em
ail: rali...@gmail.com
 Line/ Skype : ralic_lo
************************
************

Two network cards

[michael-spree-michael]

Hello,

It used to be that one can use two network cards at the same time, after
configuring /etc/network/interfaces and making the networks static.

This I did.

The results; the wifi card won't connect and the wired connected.

Is this something different in Jessie?

Thanks a lot in advance.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55686af5.4050...@gmx.de

Re: Two network cards

[Liam O'Toole]

On 2015-05-29, michael-spree-michael michael-spree-mich...@gmx.de wrote:
 Hello,

 It used to be that one can use two network cards at the same time, after
 configuring /etc/network/interfaces and making the networks static.

 This I did.

 The results; the wifi card won't connect and the wired connected.

 Is this something different in Jessie?

 Thanks a lot in advance.


What's the wifi card? It could be that it requires non-free firmware.

-- 

Liam



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmmh2v7.7jg.liam.p.otoole@dipsy.tubbynet

Re: Two network cards

[Bob Proulx]

michael-spree-michael wrote:
 It used to be that one can use two network cards at the same time, after
 configuring /etc/network/interfaces and making the networks static.

Yes.  This is a standard and widely used feature.

 This I did.
 
 The results; the wifi card won't connect and the wired connected.
 
 Is this something different in Jessie?

The differences between Wheezy 7 and Jessie 8 are very long.  You can
look in the release notes for all of the documentation of the details
the changes.  The expectation is that none of those will prevent
multiple network interfaces from working.  And for all of us running
Jessie 8 with multiple network cards it is in fact working.

You have said very little about what problem you are having nor what
software you are using.  Makes it rather difficult for anyone to help
you.  All we can say is works for me and that isn't going to be very
satisfying to you.

For best results please say what software you are using, exactly what
you have tried, and what was the output.

Bob


signature.asc
Description: Digital signature

How to configure udev to rename USB network cards correctly

[Steffen Dettmer]

Hi,

we have USB network cards and udev rules for them, for example:

SUBSYSTEM==net, ACTION==add, ATTRS{manufacturer}==Novatel
Wireless*, ATTRS{serial}==?*, NAME=ethnovatel%n

when booting, we see e.g., ethnovatel3 and ethnovatel4, as expected.

When unplugging/replugging (or power cycling) the USB devices, it
often happens that one devices is called rename22 (with an
arbitrary, increasing number). My guess is that this happens because
%n is unfortunately not a unique counter but the number of the device
befor renaming it, and that it happens that first device gets kernel
name eth4, is renamed to ethnovatel4, second device gets eth4
from kernel (no conflict) and cannot be renamed to ethnovatel4,
because already existing.

I looked to udev scripts, which seem to be quite complicated and
difficult to write and debug, so I assume it is not intended to change
them.

How to configure udev to rename USB network cards correctly?

Regards,
Steffen


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caobounpmuba55zcp5xdjdgkayqbc6rwxd4qk4gqpa9ck370...@mail.gmail.com

Re: 2 Network Cards

[Brian McKee]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


On 1-Feb-08, at 11:59 PM, Raquel wrote:


I think that I understand what you're saying.  However, what's the
difference?  If the machine is capable of handling 15 VirtualHosts
with 1 nic and 1 IP number, why can it not handle 15 VirtualHosts with
2 nics and 2 IP numbers?  What am I not understanding?


Two nics = 2 pieces of hardware that can fail, both consuming hydro.

On the other hand, tripping over one wire only gets one website.

Ya win some, ya lose some  :-)

Brian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Verify this email or encrypt your email for free - see gnupg.org

iD8DBQFHpxxeGnOmb9xIQHQRAl6zAKCVR7vNyRhp/UVL9vz+9JJX7SSZcwCfcMTJ
IB2pc1DzYPUXm1kmHNmqDAo=
=CS8b
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Ken Irving]

On Fri, Feb 01, 2008 at 09:44:47PM -0900, Ken Irving wrote:
  On Fri, Feb 01, 2008 at 04:37:03PM -0800, Raquel wrote:
   On Fri, 1 Feb 2008 16:09:00 -0800 Raquel wrote:
   
I have 2 network cards in this machine.  Currently only one of those
cards is setup but now I have need to setup another.  The
current /etc/network/interfaces looks like:
...
   Is there anything else I need to watch out for?  I know that the
   firewall needs to be changed.
 ... 
 I dimly recall that there's something in how the kernel works with
 interfaces and ip address that's perhaps not intuitive, and easy to
 get wrong.

ARP (Address Resolution Protocol) flux looks like something you might
want to look into.
 
-- 
Ken Irving, [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

2 Network Cards

[Raquel]

I have 2 network cards in this machine.  Currently only one of those
cards is setup but now I have need to setup another.  The
current /etc/network/interfaces looks like:
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 99.999.999.137
netmask 255.255.255.248
network 99.999.999.136
broadcast 99.999.999.999
gateway 99.999.999.999
dns-nameservers 99.999.999.999 99.999.999.999
dns-search domain.com

To setup the other network card, can I do:
# The secondary network interface
allow-hotplug eth0
iface eth0 inet static
address 99.999.999.138
netmask 255.255.255.248
network 99.999.999.136
broadcast 99.999.999.999
gateway 99.999.999.999
dns-nameservers 99.999.999.999 99.999.999.999
dns-search domain.com

In addition to changing /etc/hosts, what about /etc/hostname?
Anything else I need to watch out for?

-- 
Raquel

In recognizing the humanity of our fellow beings, we pay ourselves
the highest tribute.

  --Thurgood Marshall


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Raquel]

On Fri, 1 Feb 2008 16:09:00 -0800
Raquel [EMAIL PROTECTED] wrote:

 I have 2 network cards in this machine.  Currently only one of those
 cards is setup but now I have need to setup another.  The
 current /etc/network/interfaces looks like:
 # The primary network interface
 allow-hotplug eth0
 iface eth0 inet static
 address 99.999.999.137
 netmask 255.255.255.248
 network 99.999.999.136
 broadcast 99.999.999.999
 gateway 99.999.999.999
 dns-nameservers 99.999.999.999 99.999.999.999
 dns-search domain.com
 

Let me make a few changes.  In order to get eth1 to also work, can I
add to /etc/network/interfaces:

# The secondary network interface
allow-hotplug eth1
iface eth1 inet static
address 99.999.999.138
netmask 255.255.255.248
network 99.999.999.136
broadcast 99.999.999.999
gateway 99.999.999.999
dns-nameservers 99.999.999.999 99.999.999.999
dns-search domain.com

Is there anything else I need to watch out for?  I know that the
firewall needs to be changed.

-- 
Raquel

The arc of the moral universe is long, but it bends towards justice.

  --Martin Luther King, Jr.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Ken Irving]

On Fri, Feb 01, 2008 at 04:37:03PM -0800, Raquel wrote:
 On Fri, 1 Feb 2008 16:09:00 -0800 Raquel wrote:
 
  I have 2 network cards in this machine.  Currently only one of those
  cards is setup but now I have need to setup another.  The
  current /etc/network/interfaces looks like:
  # The primary network interface
  allow-hotplug eth0
  iface eth0 inet static
  address 99.999.999.137
  netmask 255.255.255.248
  network 99.999.999.136
  broadcast 99.999.999.999
  gateway 99.999.999.999
  dns-nameservers 99.999.999.999 99.999.999.999
  dns-search domain.com
 
 Let me make a few changes.  In order to get eth1 to also work, can I
 add to /etc/network/interfaces:
 
 # The secondary network interface
 allow-hotplug eth1
 iface eth1 inet static
 address 99.999.999.138
 netmask 255.255.255.248
 network 99.999.999.136
 broadcast 99.999.999.999
 gateway 99.999.999.999
 dns-nameservers 99.999.999.999 99.999.999.999
 dns-search domain.com
 
 Is there anything else I need to watch out for?  I know that the
 firewall needs to be changed.

I don't think it's quite as simple as providing two separate IPs on a
single subnet, but what are you trying to do?  All you say is that you
need to setup the second card, but why?  I have plenty of systems
with 2 cards, but I've only done it to host a local net on one card,
with an upstream net connection on the other.  While you haven't said
much about the firewall, I'd suggest looking at shorewall and its docs,
only because that's where I've read about doing this sort of thing.

Ken

-- 
Ken Irving, [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Douglas A. Tutty]

On Fri, Feb 01, 2008 at 04:37:03PM -0800, Raquel wrote:
 On Fri, 1 Feb 2008 16:09:00 -0800
 Raquel [EMAIL PROTECTED] wrote:
 
  I have 2 network cards in this machine.  Currently only one of those
  cards is setup but now I have need to setup another.  The
  current /etc/network/interfaces looks like:
  # The primary network interface
  allow-hotplug eth0
  iface eth0 inet static
  address 99.999.999.137
  netmask 255.255.255.248
  network 99.999.999.136
  broadcast 99.999.999.999
  gateway 99.999.999.999
  dns-nameservers 99.999.999.999 99.999.999.999
  dns-search domain.com
  
 
 Let me make a few changes.  In order to get eth1 to also work, can I
 add to /etc/network/interfaces:
 
 # The secondary network interface
 allow-hotplug eth1
 iface eth1 inet static
 address 99.999.999.138
 netmask 255.255.255.248
 network 99.999.999.136
 broadcast 99.999.999.999
 gateway 99.999.999.999
 dns-nameservers 99.999.999.999 99.999.999.999
 dns-search domain.com
 
 Is there anything else I need to watch out for?  I know that the
 firewall needs to be changed.
 

Looks fine to me, as long as all the 9s are place-holders for real
numbers.  It doesn't make sense to have two NICs in one box on the same
network.

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Raquel]

On Fri, 1 Feb 2008 20:44:11 -0500
Douglas A. Tutty [EMAIL PROTECTED] wrote:

 On Fri, Feb 01, 2008 at 04:37:03PM -0800, Raquel wrote:
  On Fri, 1 Feb 2008 16:09:00 -0800
  Raquel [EMAIL PROTECTED] wrote:
  
   I have 2 network cards in this machine.  Currently only one of
   those cards is setup but now I have need to setup another.  The
   current /etc/network/interfaces looks like:
   # The primary network interface
   allow-hotplug eth0
   iface eth0 inet static
   address 99.999.999.137
   netmask 255.255.255.248
   network 99.999.999.136
   broadcast 99.999.999.999
   gateway 99.999.999.999
   dns-nameservers 99.999.999.999 99.999.999.999
   dns-search domain.com
   
  
  Let me make a few changes.  In order to get eth1 to also work,
  can I add to /etc/network/interfaces:
  
  # The secondary network interface
  allow-hotplug eth1
  iface eth1 inet static
  address 99.999.999.138
  netmask 255.255.255.248
  network 99.999.999.136
  broadcast 99.999.999.999
  gateway 99.999.999.999
  dns-nameservers 99.999.999.999 99.999.999.999
  dns-search domain.com
  
  Is there anything else I need to watch out for?  I know that the
  firewall needs to be changed.
  
 
 Looks fine to me, as long as all the 9s are place-holders for real
 numbers.  It doesn't make sense to have two NICs in one box on the
 same network.
 
 Doug.
 

Thanks, Doug.  Yes.  The 9s are place-holders.  I've not been using
the second nic because it wasn't needed.  However, now I want to host
2 different SSL hosts using named virtual hosts.  So, I need a second
IP and I'm dipping into my range of IP numbers.

-- 
Raquel

The arc of the moral universe is long, but it bends towards justice.

  --Martin Luther King, Jr.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Douglas A. Tutty]

On Fri, Feb 01, 2008 at 06:37:04PM -0800, Raquel wrote:
 
 Thanks, Doug.  Yes.  The 9s are place-holders.  I've not been using
 the second nic because it wasn't needed.  However, now I want to host
 2 different SSL hosts using named virtual hosts.  So, I need a second
 IP and I'm dipping into my range of IP numbers.

If they truely are on the same physical pice of wire, why not use
virtual/aliases.  Eg, instead of eth0 and eth1, you would have eth0 and
eth0:1 or something (never done it, check the man pages).

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Raquel]

On Fri, 1 Feb 2008 21:54:37 -0500
Douglas A. Tutty [EMAIL PROTECTED] wrote:

 On Fri, Feb 01, 2008 at 06:37:04PM -0800, Raquel wrote:
  
  Thanks, Doug.  Yes.  The 9s are place-holders.  I've not been
  using the second nic because it wasn't needed.  However, now I
  want to host 2 different SSL hosts using named virtual hosts.
  So, I need a second IP and I'm dipping into my range of IP
  numbers.
 
 If they truely are on the same physical pice of wire, why not use
 virtual/aliases.  Eg, instead of eth0 and eth1, you would have eth0
 and eth0:1 or something (never done it, check the man pages).
 
 Doug.
 

Don't I end up doing the same thing?  I thought of aliasing eth0, but
why?  I have a nic not being used in the machine and running another
wire from my switch to it will give me what I need.  If I alias eth0
to eth0:1 I'd still need to assign eth0:1 another IP number. Right?

-- 
Raquel

The arc of the moral universe is long, but it bends towards justice.

  --Martin Luther King, Jr.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Douglas A. Tutty]

On Fri, Feb 01, 2008 at 07:28:47PM -0800, Raquel wrote:
 On Fri, 1 Feb 2008 21:54:37 -0500
 Douglas A. Tutty [EMAIL PROTECTED] wrote:
 
  On Fri, Feb 01, 2008 at 06:37:04PM -0800, Raquel wrote:
   
   Thanks, Doug.  Yes.  The 9s are place-holders.  I've not been
   using the second nic because it wasn't needed.  However, now I
   want to host 2 different SSL hosts using named virtual hosts.
   So, I need a second IP and I'm dipping into my range of IP
   numbers.
  
  If they truely are on the same physical pice of wire, why not use
  virtual/aliases.  Eg, instead of eth0 and eth1, you would have eth0
  and eth0:1 or something (never done it, check the man pages).
 
 Don't I end up doing the same thing?  I thought of aliasing eth0, but
 why?  I have a nic not being used in the machine and running another
 wire from my switch to it will give me what I need.  If I alias eth0
 to eth0:1 I'd still need to assign eth0:1 another IP number. Right?

Sure.  It would make sense if the hardware could keep up with two NICs
going full-out, so it depends on the network speed (10/100/1000), the
speed and quality of the NICs, and the power of the computer.  Either
way, every packet has to go through the kernel and the firewall code.  I
don't know which is faster.  It takes a monster of a box to keep a GB
ethernet saturated, yet alone 2.

Look at it this way:

Lets say we're dealing with a 100 MB/s ethernet.  Lets say that all the
boxes on the network are all capable of saturating their 100 MB/s
ethernet.  If all the NICs all try to talk at once, as long as they are
talking in pairs, then the switch should handle it.  In this case,
having two NICs in your box makes sense because, being two virtual
boxes, it is conceivable that two different client boxes will want to
talk to the server box at full speed, as long as the server box can keep
2 100 MB/s NICs well fed while doing the serving.  Also, as long as the
switch back-plane has the throughput.  

Remember, a second NIC will mean twice the hardware to be interrupting
the CPU.  

I would rather spend the money on one good NIC than two cheaper ones.  

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Raquel]

On Fri, 1 Feb 2008 22:45:30 -0500
Douglas A. Tutty [EMAIL PROTECTED] wrote:

 Sure.  It would make sense if the hardware could keep up with two
 NICs going full-out, so it depends on the network speed
 (10/100/1000), the speed and quality of the NICs, and the power of
 the computer.  Either way, every packet has to go through the
 kernel and the firewall code.  I don't know which is faster.  It
 takes a monster of a box to keep a GB ethernet saturated, yet alone
 2.
 
 Look at it this way:
 
 Lets say we're dealing with a 100 MB/s ethernet.  Lets say that all
 the boxes on the network are all capable of saturating their 100
 MB/s ethernet.  If all the NICs all try to talk at once, as long as
 they are talking in pairs, then the switch should handle it.  In
 this case, having two NICs in your box makes sense because, being
 two virtual boxes, it is conceivable that two different client
 boxes will want to talk to the server box at full speed, as long as
 the server box can keep 2 100 MB/s NICs well fed while doing the
 serving.  Also, as long as the switch back-plane has the
 throughput.  
 
 Remember, a second NIC will mean twice the hardware to be
 interrupting the CPU.  
 
 I would rather spend the money on one good NIC than two cheaper
 ones.  
 
 Doug.

I think that I understand what you're saying.  However, what's the
difference?  If the machine is capable of handling 15 VirtualHosts
with 1 nic and 1 IP number, why can it not handle 15 VirtualHosts with
2 nics and 2 IP numbers?  What am I not understanding?

Scenario #1:
domainA and domainB are being hosted on 1 machine with 1 nic.  Out of
need, different IP numbers are needed, so eth0 is being aliased,
creating eth0:1.

Scenario #2
domainA and domainB are being hosted on 1 machine with 2 nic.  Out of
need, different IP numbers are needed, so nic#0 is eth0 and nic#1 is
eth1.

The only difference I can see is that, in essence, Scenario #1 is
possibly throttling what reaches the CPU by virtue of what can get
through the nic.

-- 
Raquel

The arc of the moral universe is long, but it bends towards justice.

  --Martin Luther King, Jr.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: 2 Network Cards

[Alex Samad]

On Fri, Feb 01, 2008 at 08:59:38PM -0800, Raquel wrote:
 On Fri, 1 Feb 2008 22:45:30 -0500
 Douglas A. Tutty [EMAIL PROTECTED] wrote:
 
  Sure.  It would make sense if the hardware could keep up with two
  NICs going full-out, so it depends on the network speed
  (10/100/1000), the speed and quality of the NICs, and the power of
  the computer.  Either way, every packet has to go through the
  kernel and the firewall code.  I don't know which is faster.  It
  takes a monster of a box to keep a GB ethernet saturated, yet alone
  2.
  
  Look at it this way:
  
  Lets say we're dealing with a 100 MB/s ethernet.  Lets say that all
  the boxes on the network are all capable of saturating their 100
  MB/s ethernet.  If all the NICs all try to talk at once, as long as
  they are talking in pairs, then the switch should handle it.  In
  this case, having two NICs in your box makes sense because, being
  two virtual boxes, it is conceivable that two different client
  boxes will want to talk to the server box at full speed, as long as
  the server box can keep 2 100 MB/s NICs well fed while doing the
  serving.  Also, as long as the switch back-plane has the
  throughput.  
  
  Remember, a second NIC will mean twice the hardware to be
  interrupting the CPU.  
  
  I would rather spend the money on one good NIC than two cheaper
  ones.  
  
  Doug.
 
 I think that I understand what you're saying.  However, what's the
 difference?  If the machine is capable of handling 15 VirtualHosts
 with 1 nic and 1 IP number, why can it not handle 15 VirtualHosts with
 2 nics and 2 IP numbers?  What am I not understanding?

broadcasts will cause an interrupt on both interfaces. Something to remember 
eth0 will answer arp requests for the ip address on eth1 (there are sysctl's to 
stop this)

you will need to check to make sure you packets are leaving via eth1 (if eth0 
came up first). been a while since I have done this but your routing table is 
going to look something like


a.b.c.137 dev eth0 link mtu 1500 advmss 1460
a.b.c.138 dev eth1 link mtu 1500 advmss 1460
a.b.c.0/24 dev eth0 proto kernel scope link src a.b.c.137 mtu 1500 advmss 1460 
(- this depends which one come up first [i believe])

some when it comes time to route an outbound packet it will go via eth0 

plus you will probably have something like this

default via a.b.c.1 dev eth0 mtu 1500 advmss 1460 (so all non local ip packet 
will go via eth0)

and depending on arp replies, if eth0 replies on behalf of eth1, all packets 
destined for the ip address on eth1 will come in via eth0 (again this can be 
changed with a sysctl)


a




 
 Scenario #1:
 domainA and domainB are being hosted on 1 machine with 1 nic.  Out of
 need, different IP numbers are needed, so eth0 is being aliased,
 creating eth0:1.
 
 Scenario #2
 domainA and domainB are being hosted on 1 machine with 2 nic.  Out of
 need, different IP numbers are needed, so nic#0 is eth0 and nic#1 is
 eth1.
 
 The only difference I can see is that, in essence, Scenario #1 is
 possibly throttling what reaches the CPU by virtue of what can get
 through the nic.
 
 -- 
 Raquel
 
 The arc of the moral universe is long, but it bends towards justice.
 
   --Martin Luther King, Jr.
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 

-- 
If we don't stop extending our troops all around the world in nation-building 
missions, then we're going to have a serious problem coming down the road.

- George W. Bush
10/03/2000
Boston, MA
First Presidential Debate with Al Gore


signature.asc
Description: Digital signature

Re: 2 Network Cards

[Ken Irving]

On Fri, Feb 01, 2008 at 04:35:18PM -0900, Ken Irving wrote:
 On Fri, Feb 01, 2008 at 04:37:03PM -0800, Raquel wrote:
  On Fri, 1 Feb 2008 16:09:00 -0800 Raquel wrote:
  
   I have 2 network cards in this machine.  Currently only one of those
   cards is setup but now I have need to setup another.  The
   current /etc/network/interfaces looks like:
   # The primary network interface
   allow-hotplug eth0
   iface eth0 inet static
   address 99.999.999.137
   netmask 255.255.255.248
   network 99.999.999.136
   broadcast 99.999.999.999
   gateway 99.999.999.999
   dns-nameservers 99.999.999.999 99.999.999.999
   dns-search domain.com
  
  Let me make a few changes.  In order to get eth1 to also work, can I
  add to /etc/network/interfaces:
  
  # The secondary network interface
  allow-hotplug eth1
  iface eth1 inet static
  address 99.999.999.138
  netmask 255.255.255.248
  network 99.999.999.136
  broadcast 99.999.999.999
  gateway 99.999.999.999
  dns-nameservers 99.999.999.999 99.999.999.999
  dns-search domain.com
  
  Is there anything else I need to watch out for?  I know that the
  firewall needs to be changed.
 
 I don't think it's quite as simple as providing two separate IPs on a
 single subnet, but what are you trying to do?  All you say is that you
 need to setup the second card, but why?  I have plenty of systems
 with 2 cards, but I've only done it to host a local net on one card,
 with an upstream net connection on the other.  While you haven't said
 much about the firewall, I'd suggest looking at shorewall and its docs,
 only because that's where I've read about doing this sort of thing.

I haven't seen any response to this, but had the impression from the
use of 137 and 138 in the addresses above that both would be on the
same subnet.  The obfuscated network entries look to me to be host
address, so I don't know what you're dealing with.  I googled a bit and
found some informative links, and suggest you do the same.

I dimly recall that there's something in how the kernel works with
interfaces and ip address that's perhaps not intuitive, and easy to
get wrong.

-- 
 Ken Irving, [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: RE : Re: Kernel issues due to identical network cards

[Douglas A. Tutty]

On Sat, Jan 05, 2008 at 01:11:41PM +0100, David MAGNY wrote:
 --- Douglas A. Tutty [EMAIL PROTECTED] a ?crit
  On Fri, Jan 04, 2008 at 11:06:31PM +0100, David
  MAGNY wrote:
   Hello,
   
   I am upgrading a firewall from Sarge to Etch.
   
   On this machine, I have 3 network cards.
   
   2 networks cards are identical. It is PCI network
   cards and it is SMC1233A-TX.
   
   On Sarge, everything worked well.
   
   The issue is that only one card of both is
  available.
  
  What exactly does this line mean?  Do you mean that
  of the two identical
  cards, only one is available?
 
 Yes, only one is available
 
  so at least you know that the kernel is finding the
  card.  
  
[snip dmesg that shows all three cards] 
  This suggests that eth0 is the intel card, while
  eth1 and eth2 are the
  two ADMtek comets.
 
 Yes you are right. But, I use ifrename (/etc/iftab) in
 order to be sure that a network interface has always
 the same name when I restart the server.
 
 if my /etc/iftab I mention that,
 ethO is one of ADMtek comet
 eth1 is the intel card
 eth2 is the other ADMtek card
 
 and in fact eth2 is not available.
 
 

What if you don't use iftab?  If, as a test, you just go ahead and set
up all three cards?  Does /sbin/ifconfig then show three cards
configured?  If so, then dmesg and the kernel are just fine, the problem
is in ifrename.  I've never needed ifrename so I don't know about it.

 
  What does your /etc/network/interfaces look like?
 #eth0 is connected to Internet
 auto eth0
 iface eth0 inet static
 address X.X.X.X
 netmask X.X.X.X
 network X.X.X.X
 broadcast X.X.X.X
 gateway X.X.X.X
 
 #eth1 is connected to the private network
 auto eth1
 iface eth1 inet static
 address 192.168.0.254
 netmask 255.255.255.0
 network 192.168.0.0
 broadcast 192.168.0.255
 
 #eth2 is connected to the DMZ
 auto eth2
 iface eth2 inet static
 address 192.168.2.254
 netmask 255.255.255.0
 network 192.168.2.0
 broadcast 192.168.2.255
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Kernel issues due to identical network cards

[David MAGNY]

Hello,

I am upgrading a firewall from Sarge to Etch.

On this machine, I have 3 network cards.

2 networks cards are identical. It is PCI network
cards and it is SMC1233A-TX.

On Sarge, everything worked well.

The issue is that only one card of both is available.
The used kernel is  2.6.18.

Within the dmesg log file, I have the following
information :


Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-17)
([EMAIL PROTECTED]) (gcc version 4.1.2 20061115
(prerelease) (Debian 4.1.1-21)) #1 SMP Mon Dec 24
16:41:07 UTC 2007
BIOS-provided physical RAM map:
 BIOS-e820:  - 000a
(usable)
 BIOS-e820: 000f - 0010
(reserved)
 BIOS-e820: 0010 - 1fe8cc00
(usable)
 BIOS-e820: 1fe8cc00 - 1fe8ec00 (ACPI
NVS)
 BIOS-e820: 1fe8ec00 - 1fe90c00 (ACPI
data)
 BIOS-e820: 1fe90c00 - 2000
(reserved)
 BIOS-e820: e000 - f000
(reserved)
 BIOS-e820: fec0 - fed00400
(reserved)
 BIOS-e820: fed2 - feda
(reserved)
 BIOS-e820: fee0 - fef0
(reserved)
 BIOS-e820: ffb0 - 0001
(reserved)
0MB HIGHMEM available.
510MB LOWMEM available.
found SMP MP-table at 000fe710
On node 0 totalpages: 130700
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 126604 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 DELL 
) @ 0x000fec10
ACPI: RSDT (v001 DELLPE1420  0x0007 ASL 
0x0061) @ 0x000fcb6c
ACPI: FADT (v001 DELLPE1420  0x0007 ASL 
0x0061) @ 0x000fcbac
ACPI: SSDT (v001   DELLst_ex 0x1000 MSFT
0x010d) @ 0xfffc4a0c
ACPI: MADT (v001 DELLPE1420  0x0007 ASL 
0x0061) @ 0x000fcc20
ACPI: BOOT (v001 DELLPE1420  0x0007 ASL 
0x0061) @ 0x000fccaa
ACPI: ASF! (v016 DELLPE1420  0x0007 ASL 
0x0061) @ 0x000fccd2
ACPI: MCFG (v001 DELLPE1420  0x0007 ASL 
0x0061) @ 0x000fcd39
ACPI: HPET (v001 DELLPE1420  0x0007 ASL 
0x0061) @ 0x000fcd77
ACPI: DSDT (v001   DELLdt_ex 0x1000 MSFT
0x010d) @ 0x
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee0
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec0]
gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec0,
GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xfec8]
gsi_base[24])
IOAPIC[1]: apic_id 9, version 32, address 0xfec8,
GSI 24-47
ACPI: IOAPIC (id[0x0a] address[0xfec80800]
gsi_base[48])
IOAPIC[2]: apic_id 10, version 32, address 0xfec80800,
GSI 48-71
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl
dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 3 I/O APICs
ACPI: HPET id: 0x8086a201 base: 0xfed0
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 3000 (gap:
2000:c000)
Detected 2793.335 MHz processor.
Built 1 zonelists.  Total pages: 130700
Kernel command line: root=/dev/sda1 ro pci=routeirq 
mapped APIC to d000 (fee0)
mapped IOAPIC to c000 (fec0)
mapped IOAPIC to b000 (fec8)
mapped IOAPIC to a000 (fec80800)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6,
262144 bytes)
Inode-cache hash table entries: 32768 (order: 5,
131072 bytes)
Memory: 510652k/522800k available (1541k kernel code,
11580k reserved, 576k data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in
supervisor mode... Ok.
hpet0: at MMIO 0xfed0 (virtual 0xe080), IRQs
2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
Using HPET for base-timer
Calibrating delay using timer specific routine..
5590.14 BogoMIPS (lpj=11180287)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 2000
  641d  
CPU: After vendor identify, caps: bfebfbff 2000
  641d  
monitor/mwait feature present.
using mwait in idle threads.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 2000 
0180 641d  
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs

Re: Kernel issues due to identical network cards

[Douglas A. Tutty]

On Fri, Jan 04, 2008 at 11:06:31PM +0100, David MAGNY wrote:
 Hello,
 
 I am upgrading a firewall from Sarge to Etch.
 
 On this machine, I have 3 network cards.
 
 2 networks cards are identical. It is PCI network
 cards and it is SMC1233A-TX.
 
 On Sarge, everything worked well.
 
 The issue is that only one card of both is available.

What exactly does this line mean?  Do you mean that of the two identical
cards, only one is available?

 The used kernel is  2.6.18.
 
 Within the dmesg log file, I have the following
 information :
 

 I noticed that the two identical network cards are
 detected  :
 
 eth1: ADMtek Comet rev 17 at 0001c800,
 00:50:BF:B0:CB:4B, IRQ 217.
 ACPI: PCI Interrupt :03:0d.0[A] - GSI 49 (level,
 low) - IRQ 225
 tulip1:  MII transceiver #1 config 1000 status 786d
 advertising 05e1.
 eth2: ADMtek Comet rev 17 at 0001cc00,
 00:50:BF:B7:F2:79, IRQ 225.
 
 I added the following parameters to the kernel
 pci=irprouting, and I always have the same issue.

You also have this (culled from your dmesg)

 e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
 Connection
 usb 1-1: device not accepting address 2, error -71
   Vendor: ATA   Model: WDC WD800AAJS-18  Rev: 01.0
   Type:   Direct-Access  ANSI SCSI
 revision: 05
 ACPI: PCI Interrupt :03:0c.0[A] - GSI 53 (level,
 low) - IRQ 217
 tulip0:  MII transceiver #1 config 1000 status 786d
 advertising 05e1.
 
so at least you know that the kernel is finding the card.  

I don't like the 2.6 dmesg with messages from different modules being
intermixed.  Since I don't know the kernel internals, its hard for me to
tell what line belongs to which device if it doesn't start with a device
node.  So, in this case, I don't know if the third line (usb 1-1...)
relates to the problem or not.

This suggests that eth0 is the intel card, while eth1 and eth2 are the
two ADMtek comets.

What does your /etc/network/interfaces look like?

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Kernel issues due to identical network cards

[Andrew Sackville-West]

On Fri, Jan 04, 2008 at 11:06:31PM +0100, David MAGNY wrote:
 Hello,
 
 I am upgrading a firewall from Sarge to Etch.
 
 On this machine, I have 3 network cards.
 
 2 networks cards are identical. It is PCI network
 cards and it is SMC1233A-TX.
 
 On Sarge, everything worked well.
 
 The issue is that only one card of both is available.
 The used kernel is  2.6.18.
 
 Within the dmesg log file, I have the following
 information :
...
 e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
 Connection

found 1 card, though it's not very helpful info.

...
 eth1: ADMtek Comet rev 17 at 0001c800,
 00:50:BF:B0:CB:4B, IRQ 217.
...

found another card, with MAC and irq.

 eth2: ADMtek Comet rev 17 at 0001cc00,
 00:50:BF:B7:F2:79, IRQ 225.

ditto.

...
 ADDRCONF(NETDEV_UP): eth2: link is not ready
 e1000: eth2: e1000_watchdog: NIC Link is Up 100 Mbps
 Full Duplex
 ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready

hmmm... do the ADMtek cards use e1000 driver or did eth0 get moved to
eth2, thus bumping eth2 elsewhere? 

 
 
 
 I noticed that the two identical network cards are
 detected  :
 
 eth1: ADMtek Comet rev 17 at 0001c800,
 00:50:BF:B0:CB:4B, IRQ 217.
 ACPI: PCI Interrupt :03:0d.0[A] - GSI 49 (level,
 low) - IRQ 225
 tulip1:  MII transceiver #1 config 1000 status 786d
 advertising 05e1.
 eth2: ADMtek Comet rev 17 at 0001cc00,
 00:50:BF:B7:F2:79, IRQ 225.
 
 I added the following parameters to the kernel
 pci=irprouting, and I always have the same issue.

why did you do this? is that a typo? irqrouting maybe?

what output from 

lspci -v

what output from 

ls /sys/bus/pci/drivers/

and 

ls /sys/bus/pci/drivers/e1000

A


signature.asc
Description: Digital signature

Re: Network cards changed after kernel upgrade in Etch

[Florian Kulzer]

On Wed, Sep 05, 2007 at 20:25:12 -0300, Eriberto wrote:
 Hi!
 
 I am having problems when I upgrade the Etch in my servers. The NICs
 designations are changing. For example, in a machine the NIC was eth0
 with 2.6.18-4-686 kernel. After the first upgrade, the NIC was renamed
 to eth1. The same fact occurs with 2.6.21-2 kernel (Etch-backports).
 What is the cause of this problem?

Changed module load order in the new kernels and/or a problem with your
/etc/udev/rules.d/z25_persistent-net.rules. You have to make sure that
this file has exactly one entry for each NIC in your computer and that
the correct MAC address is associated with the each eth* name.

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Network cards changed after kernel upgrade in Etch

[Eriberto]

Hi!

I am having problems when I upgrade the Etch in my servers. The NICs
designations are changing. For example, in a machine the NIC was eth0
with 2.6.18-4-686 kernel. After the first upgrade, the NIC was renamed
to eth1. The same fact occurs with 2.6.21-2 kernel (Etch-backports).
What is the cause of this problem?

Thanks in advanced.

Eriberto - Brazil


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: two network cards on a server

[Roberto C . Sánchez]

On Wed, Apr 18, 2007 at 09:18:10PM -0400, Faheem Mitha wrote:
 
 eth0  Link encap:Ethernet  HWaddr 00:E0:81:31:33:8C
   inet addr:152.3.172.111  Bcast:152.3.173.255  Mask:255.255.254.0
 
 eth1  Link encap:Ethernet  HWaddr 00:E0:81:31:33:64
   inet addr:152.3.172.60  Bcast:152.3.173.255  Mask:255.255.254.0

You can see here that they are on the same subnet.  The problem, as I
mentioned previously, is that having two physical interfaces on the same
subnet can confuse your system quite badly.  What is the output of
`/sbin/route -n` ?

Regards,

-Roberto
-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: two network cards on a server

[Roberto C . Sánchez]

On Thu, Apr 19, 2007 at 05:06:47PM -0400, Faheem Mitha wrote:
 
 /sbin/route -n
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse 
 Iface
 152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth1
 152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth0
 0.0.0.0 152.3.172.1 0.0.0.0 UG0  00 eth1
 
 Somebody suggested that using two network addresses with one network card 
 should be possible. Would this make these problems go away?
 

Yes.  I have one server (firewall actually) with 8 IPs on one physical
interface.  It simplifies things greatly.  You want to search for how to
do aliases.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: two network cards on a server

[Faheem Mitha]

On Thu, 19 Apr 2007, Roberto C. Sánchez wrote:


On Wed, Apr 18, 2007 at 09:18:10PM -0400, Faheem Mitha wrote:


eth0  Link encap:Ethernet  HWaddr 00:E0:81:31:33:8C
  inet addr:152.3.172.111  Bcast:152.3.173.255  Mask:255.255.254.0

eth1  Link encap:Ethernet  HWaddr 00:E0:81:31:33:64
  inet addr:152.3.172.60  Bcast:152.3.173.255  Mask:255.255.254.0


You can see here that they are on the same subnet.  The problem, as I
mentioned previously, is that having two physical interfaces on the same
subnet can confuse your system quite badly.  What is the output of
`/sbin/route -n` ?


/sbin/route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth1
152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth0
0.0.0.0 152.3.172.1 0.0.0.0 UG0  00 eth1

Somebody suggested that using two network addresses with one network card 
should be possible. Would this make these problems go away?


Thanks.Faheem.

Re: two network cards on a server

[Alex Samad]

On Thu, Apr 19, 2007 at 05:15:25PM -0400, Roberto C. Sánchez wrote:
 On Thu, Apr 19, 2007 at 05:06:47PM -0400, Faheem Mitha wrote:
  
  /sbin/route -n
  
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse 
  Iface
  152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth1
  152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth0
  0.0.0.0 152.3.172.1 0.0.0.0 UG0  00 eth1
  
  Somebody suggested that using two network addresses with one network card 
   should be possible. Would this make these problems go away?
sorry, what are the problems that you are seeing ?

  
 
 Yes.  I have one server (firewall actually) with 8 IPs on one physical
 interface.  It simplifies things greatly.  You want to search for how to
 do aliases.

have a look for ip (it part of the iproute package)

Usage: ip addr {add|del} IFADDR dev STRING
   ip addr {show|flush} [ dev STRING ] [ scope SCOPE-ID ]
[ to PREFIX ] [ FLAG-LIST ] [ label PATTERN ]
IFADDR := PREFIX | ADDR peer PREFIX
  [ broadcast ADDR ] [ anycast ADDR ]
  [ label STRING ] [ scope SCOPE-ID ]
SCOPE-ID := [ host | link | global | NUMBER ]
FLAG-LIST := [ FLAG-LIST ] FLAG
FLAG  := [ permanent | dynamic | secondary | primary |
   tentative | deprecated ]


 
 Regards,
 
 -Roberto
 
 -- 
 Roberto C. Sánchez
 http://people.connexer.com/~roberto
 http://www.connexer.com




signature.asc
Description: Digital signature

Re: two network cards on a server

[Roberto C . Sánchez]

On Thu, Apr 19, 2007 at 06:12:24PM -0400, Faheem Mitha wrote:
 
 On Fri, 20 Apr 2007, Alex Samad wrote:
 
 
 have a look for ip (it part of the iproute package)
 
 Usage: ip addr {add|del} IFADDR dev STRING
   ip addr {show|flush} [ dev STRING ] [ scope SCOPE-ID ]
[ to PREFIX ] [ FLAG-LIST ] [ label PATTERN ]
 IFADDR := PREFIX | ADDR peer PREFIX
  [ broadcast ADDR ] [ anycast ADDR ]
  [ label STRING ] [ scope SCOPE-ID ]
 SCOPE-ID := [ host | link | global | NUMBER ]
 FLAG-LIST := [ FLAG-LIST ] FLAG
 FLAG  := [ permanent | dynamic | secondary | primary |
   tentative | deprecated ]
 
 Er, why is this relevant? Sorry if I am being clueless.
 
You can use the ip command to setup aliases.  Personally, I just set
them up in /etc/network/interfaces (I am not sure if that just calls
ip).

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: two network cards on a server

[Faheem Mitha]

On Fri, 20 Apr 2007, Alex Samad wrote:


On Thu, Apr 19, 2007 at 05:15:25PM -0400, Roberto C. Sánchez wrote:

On Thu, Apr 19, 2007 at 05:06:47PM -0400, Faheem Mitha wrote:


/sbin/route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth1
152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 eth0
0.0.0.0 152.3.172.1 0.0.0.0 UG0  00 eth1

Somebody suggested that using two network addresses with one network card

 should be possible. Would this make these problems go away?

sorry, what are the problems that you are seeing ?


They were described in the first post to this thread. Namely one of the 
two network cards on this machine (the one configured later) behaves 
eratically, is only intermittently reachable from outside, and is 
constantly broadcasting dhcp requests.



Yes.  I have one server (firewall actually) with 8 IPs on one physical
interface.  It simplifies things greatly.  You want to search for how to
do aliases.


have a look for ip (it part of the iproute package)

Usage: ip addr {add|del} IFADDR dev STRING
  ip addr {show|flush} [ dev STRING ] [ scope SCOPE-ID ]
   [ to PREFIX ] [ FLAG-LIST ] [ label PATTERN ]
IFADDR := PREFIX | ADDR peer PREFIX
 [ broadcast ADDR ] [ anycast ADDR ]
 [ label STRING ] [ scope SCOPE-ID ]
SCOPE-ID := [ host | link | global | NUMBER ]
FLAG-LIST := [ FLAG-LIST ] FLAG
FLAG  := [ permanent | dynamic | secondary | primary |
  tentative | deprecated ]


Er, why is this relevant? Sorry if I am being clueless.

Thanks. Faheem.

Re: two network cards on a server

[Alex Samad]

On Thu, Apr 19, 2007 at 06:12:24PM -0400, Faheem Mitha wrote:
 
 
 On Fri, 20 Apr 2007, Alex Samad wrote:
 
 On Thu, Apr 19, 2007 at 05:15:25PM -0400, Roberto C. Sánchez wrote:
 On Thu, Apr 19, 2007 at 05:06:47PM -0400, Faheem Mitha wrote:
 
 /sbin/route -n
 
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse
 Iface
 152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 
 eth1
 152.3.172.0 0.0.0.0 255.255.254.0   U 0  00 
 eth0
 0.0.0.0 152.3.172.1 0.0.0.0 UG0  00 
 eth1
 
 Somebody suggested that using two network addresses with one network card
  should be possible. Would this make these problems go away?
 sorry, what are the problems that you are seeing ?
 
 They were described in the first post to this thread. Namely one of the 
 two network cards on this machine (the one configured later) behaves 
 eratically, is only intermittently reachable from outside, and is 
 constantly broadcasting dhcp requests.
 
 Yes.  I have one server (firewall actually) with 8 IPs on one physical
okay I thought it might be have a look at 

ip-sysctl.txt (in the kernel source tree doc/networking

arp_filter - BOOLEAN
1 - Allows you to have multiple network interfaces on the same
subnet, and have the ARPs for each interface be answered
based on whether or not the kernel would route a packet from
the ARP'd IP out that interface (therefore you must use source
based routing for this to work). In other words it allows control
of which cards (usually 1) will respond to an arp request.

0 - (default) The kernel can respond to arp requests with addresses
from other interfaces. This may seem wrong but it usually makes
sense, because it increases the chance of successful communication.
IP addresses are owned by the complete host on Linux, not by
particular interfaces. Only for more complex setups like load-
balancing, does this behaviour cause problems.

arp_filter for the interface will be enabled if at least one of
conf/{all,interface}/arp_filter is set to TRUE,
it will be disabled otherwise

I think you are looking for 1.  You could also bond the interfaces - not sure
exactly what your trying to do (end result)


 interface.  It simplifies things greatly.  You want to search for how to
 do aliases.
 
 have a look for ip (it part of the iproute package)
 
 Usage: ip addr {add|del} IFADDR dev STRING
   ip addr {show|flush} [ dev STRING ] [ scope SCOPE-ID ]
[ to PREFIX ] [ FLAG-LIST ] [ label PATTERN ]
 IFADDR := PREFIX | ADDR peer PREFIX
  [ broadcast ADDR ] [ anycast ADDR ]
  [ label STRING ] [ scope SCOPE-ID ]
 SCOPE-ID := [ host | link | global | NUMBER ]
 FLAG-LIST := [ FLAG-LIST ] FLAG
 FLAG  := [ permanent | dynamic | secondary | primary |
   tentative | deprecated ]
 
 Er, why is this relevant? Sorry if I am being clueless.

ip is the new tool of choice for setting things (ip address links etc)
the above is the help for ip address - if you want to add a secondary address
to an interface



 
 Thanks. Faheem.



signature.asc
Description: Digital signature

two network cards on a server

[Faheem Mitha]

Hi everyone,

I've got a server on which there are two network cards. One of the network 
cards has been configured, and has been running satisfactorily for a 
while. I recently plugged in the other network card and started using it 
for a different IP address. However, I've been having persistent problems 
with that interface. Namely, some of the time I can't connect to the 
interface, which seems to go up and down unpredictably, and floods the 
system logs with DHCP requests. Clearly something is badly wrong here, and 
I am hoping this is something simple that can be fixed easily.


This typically looks like

Apr 18 15:16:42 florence kernel: e100: eth0: e100_watchdog: link up, 100Mbps, 
full-duplex
Apr 18 15:16:43 florence dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 3
Apr 18 15:16:43 florence dhclient: receive_packet failed on eth0: Network is 
down
Apr 18 15:16:45 florence dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 3
Apr 18 15:16:46 florence dhclient: DHCPOFFER from 152.3.172.1
Apr 18 15:16:46 florence dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Apr 18 15:16:46 florence dhclient: DHCPACK from 152.3.172.1
Apr 18 15:16:46 florence dhclient: bound to 152.3.172.111 -- renewal in 43200 
seconds.
Apr 18 15:16:48 florence dhclient: DHCPREQUEST on eth1 to 152.3.250.61 port 67
Apr 18 15:16:48 florence dhclient: DHCPACK from 152.3.250.61
Apr 18 15:16:48 florence dhclient: bound to 152.3.172.60 -- renewal in 43200 
seconds.
Apr 18 15:16:53 florence kernel: eth0: no IPv6 routers present

If any has any ideas about this, please let me know. Please copy me at 
[EMAIL PROTECTED] Thanks.


Faheem.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: two network cards on a server

[Roberto C . Sánchez]

On Wed, Apr 18, 2007 at 04:20:49PM -0400, Faheem Mitha wrote:
 
 Hi everyone,
 
 I've got a server on which there are two network cards. One of the network 
 cards has been configured, and has been running satisfactorily for a 
 while. I recently plugged in the other network card and started using it 
 for a different IP address. However, I've been having persistent problems 
 with that interface. Namely, some of the time I can't connect to the 
 interface, which seems to go up and down unpredictably, and floods the 
 system logs with DHCP requests. Clearly something is badly wrong here, and 
 I am hoping this is something simple that can be fixed easily.
 
Are eth1 and eth0 configured to be on the same subnet?

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: two network cards on a server

[Faheem Mitha]

On Wed, 18 Apr 2007, Roberto C. Sánchez wrote:


On Wed, Apr 18, 2007 at 04:20:49PM -0400, Faheem Mitha wrote:


Hi everyone,

I've got a server on which there are two network cards. One of the network
cards has been configured, and has been running satisfactorily for a
while. I recently plugged in the other network card and started using it
for a different IP address. However, I've been having persistent problems
with that interface. Namely, some of the time I can't connect to the
interface, which seems to go up and down unpredictably, and floods the
system logs with DHCP requests. Clearly something is badly wrong here, and
I am hoping this is something simple that can be fixed easily.


Are eth1 and eth0 configured to be on the same subnet?

Regards,

-Roberto


Yes. I can send you the output of ifconfig if useful.

The addresses are both in the 152.3.172.* subnet.

  Faheem.

Re: two network cards on a server

[Roberto C . Sánchez]

On Wed, Apr 18, 2007 at 05:39:40PM -0400, Faheem Mitha wrote:
 
 
 On Wed, 18 Apr 2007, Roberto C. Sánchez wrote:
 
 On Wed, Apr 18, 2007 at 04:20:49PM -0400, Faheem Mitha wrote:
 
 Hi everyone,
 
 I've got a server on which there are two network cards. One of the network
 cards has been configured, and has been running satisfactorily for a
 while. I recently plugged in the other network card and started using it
 for a different IP address. However, I've been having persistent problems
 with that interface. Namely, some of the time I can't connect to the
 interface, which seems to go up and down unpredictably, and floods the
 system logs with DHCP requests. Clearly something is badly wrong here, and
 I am hoping this is something simple that can be fixed easily.
 
 Are eth1 and eth0 configured to be on the same subnet?
 
 Regards,
 
 -Roberto
 
 Yes. I can send you the output of ifconfig if useful.
 
 The addresses are both in the 152.3.172.* subnet.
 
Well, there is your problem.

Having two physical interfaces on the same subnet is generally a bad
idea:

http://lists.debian.org/debian-user/2007/01/msg01633.html
http://lists.debian.org/debian-firewall/2005/03/msg00073.html

You have to really know what you are doing.  It appears that you have
overlooked something in your configuration.  If you can provide more
details, I or someone else might be able to help get you going in the
right direction.

Regards,

-Roberto
-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: two network cards on a server

[Faheem Mitha]

On Wed, 18 Apr 2007, Roberto C. Sánchez wrote:


Well, there is your problem.

Having two physical interfaces on the same subnet is generally a bad
idea:

http://lists.debian.org/debian-user/2007/01/msg01633.html
http://lists.debian.org/debian-firewall/2005/03/msg00073.html

You have to really know what you are doing.  It appears that you have
overlooked something in your configuration.  If you can provide more
details, I or someone else might be able to help get you going in the
right direction.

Regards,

-Roberto


I'd be very happy to provide details, if you could tell me what details 
are relevant.


 Faheem.

Re: two network cards on a server

[Faheem Mitha]

On Wed, 18 Apr 2007, Roberto C. Sánchez wrote:


Well, there is your problem.

Having two physical interfaces on the same subnet is generally a bad
idea:

http://lists.debian.org/debian-user/2007/01/msg01633.html
http://lists.debian.org/debian-firewall/2005/03/msg00073.html

You have to really know what you are doing.  It appears that you have
overlooked something in your configuration.  If you can provide more
details, I or someone else might be able to help get you going in the
right direction.

Regards,

-Roberto


Just to be clear, the interfaces are both of the form 152.3.172.*.

If for example they were reconfigured so that one was of the form 
152.3.171.* and the other was of the form 152.3.172. (say) then would the 
problem just disappear?


Thanks.  Faheem.

Re: two network cards on a server

[Jeff D]

On Wed, 18 Apr 2007, Faheem Mitha wrote:




On Wed, 18 Apr 2007, Roberto C. S?nchez wrote:


Well, there is your problem.

Having two physical interfaces on the same subnet is generally a bad
idea:

http://lists.debian.org/debian-user/2007/01/msg01633.html
http://lists.debian.org/debian-firewall/2005/03/msg00073.html

You have to really know what you are doing.  It appears that you have
overlooked something in your configuration.  If you can provide more
details, I or someone else might be able to help get you going in the
right direction.

Regards,

-Roberto


I'd be very happy to provide details, if you could tell me what details are 
relevant.


Faheem.


One quick test, what happens if you unplug the interface that is working 
now and just plug in the one that you are having issues with?  That way we 
can at least rule out hardware.



 -+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.

Re: two network cards on a server

[Roberto C . Sánchez]

On Wed, Apr 18, 2007 at 06:28:29PM -0400, Faheem Mitha wrote:
 
 Just to be clear, the interfaces are both of the form 152.3.172.*.
 
 If for example they were reconfigured so that one was of the form 
 152.3.171.* and the other was of the form 152.3.172. (say) then would the 
 problem just disappear?

That largely depends on your subnet mask and how your network is routed.
What is the output of `/sbin/ifconfig` with both interfaces up?

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: two network cards on a server

[Faheem Mitha]

On Wed, 18 Apr 2007, Roberto C. Sánchez wrote:


On Wed, Apr 18, 2007 at 06:28:29PM -0400, Faheem Mitha wrote:


Just to be clear, the interfaces are both of the form 152.3.172.*.

If for example they were reconfigured so that one was of the form
152.3.171.* and the other was of the form 152.3.172. (say) then would the
problem just disappear?


That largely depends on your subnet mask and how your network is routed.
What is the output of `/sbin/ifconfig` with both interfaces up?


See below. The problem interface is eth0. The original one, which still 
seems to work Ok, is eth1.


Thanks.  Faheem.



eth0  Link encap:Ethernet  HWaddr 00:E0:81:31:33:8C
  inet addr:152.3.172.111  Bcast:152.3.173.255  Mask:255.255.254.0
  inet6 addr: fe80::2e0:81ff:fe31:338c/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:2362483 errors:0 dropped:0 overruns:0 frame:0
  TX packets:3663 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:156143284 (148.9 MiB)  TX bytes:617795 (603.3 KiB)

eth1  Link encap:Ethernet  HWaddr 00:E0:81:31:33:64
  inet addr:152.3.172.60  Bcast:152.3.173.255  Mask:255.255.254.0
  inet6 addr: fe80::2e0:81ff:fe31:3364/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:14220041 errors:0 dropped:0 overruns:0 frame:0
  TX packets:26761605 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:2763292401 (2.5 GiB)  TX bytes:35308449413 (32.8 GiB)
  Interrupt:169

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:2317579 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2317579 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:3617337316 (3.3 GiB)  TX bytes:3617337316 (3.3 GiB)

Re: two network cards on a server

[Jeff D]

On Wed, 18 Apr 2007, Faheem Mitha wrote:



Hi everyone,

I've got a server on which there are two network cards. One of the network 
cards has been configured, and has been running satisfactorily for a while. I 
recently plugged in the other network card and started using it for a 
different IP address. However, I've been having persistent problems with that 
interface. Namely, some of the time I can't connect to the interface, which 
seems to go up and down unpredictably, and floods the system logs with DHCP 
requests. Clearly something is badly wrong here, and I am hoping this is 
something simple that can be fixed easily.


This typically looks like

Apr 18 15:16:42 florence kernel: e100: eth0: e100_watchdog: link up, 100Mbps, 
full-duplex
Apr 18 15:16:43 florence dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 
port 67 interval 3
Apr 18 15:16:43 florence dhclient: receive_packet failed on eth0: Network is 
down
Apr 18 15:16:45 florence dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 
port 67 interval 3

Apr 18 15:16:46 florence dhclient: DHCPOFFER from 152.3.172.1
Apr 18 15:16:46 florence dhclient: DHCPREQUEST on eth0 to 255.255.255.255 
port 67

Apr 18 15:16:46 florence dhclient: DHCPACK from 152.3.172.1
Apr 18 15:16:46 florence dhclient: bound to 152.3.172.111 -- renewal in 43200 
seconds.
Apr 18 15:16:48 florence dhclient: DHCPREQUEST on eth1 to 152.3.250.61 port 
67

Apr 18 15:16:48 florence dhclient: DHCPACK from 152.3.250.61
Apr 18 15:16:48 florence dhclient: bound to 152.3.172.60 -- renewal in 43200 
seconds.

Apr 18 15:16:53 florence kernel: eth0: no IPv6 routers present

If any has any ideas about this, please let me know. Please copy me at 
[EMAIL PROTECTED] Thanks.


   Faheem.



One more thing you could try is to swap your ethernet cables around.  It 
could be sometihng as simple as a bad cable.  See if the problem follows 
the cable.



 -+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

multiple network cards and dns

[Andrew Critchlow]

When you have 2 network cards in use with debian with DNS server configured on 
each which one does it choose to query for an address?
 
 
Is configuring 2 network cards on debian as simple as configuring one card?
 
 
thanks everyone.

Re: multiple network cards and dns

[Ryan Castleberry]

Andrew Critchlow wrote:
When you have 2 network cards in use with debian with DNS server 
configured on each which one does it choose to query for an address?
 
 
Is configuring 2 network cards on debian as simple as configuring one 
card?
 
 
thanks everyone.
DNS is a map of names to numbers and numbers to names. You can basically 
assign any name to each IP for each NIC. If you assign the same name to 
two IP address, BIND DNS will rotate the responses in a round robin 
fashion.


So:
foo.bar.   IN   A   192.168.1.1
foo.bar.   IN   A   192.168.1.2

Will first respond to queries:
192.168.1.1 192.168.1.2
Then will respond:
192.168.1.2 192.168.1.1

This is a load balancing feature of BIND 4.9 and later versions, if this 
is what you are trying to accomplish. Otherwise if it's a firewall, 
assign a different name to the internal and external IPs.


Configuring two NICs is as simple as adding another entry in 
/etc/network/interfaces for the new NIC. Be careful as sometimes after 
adding a second NIC the original NIC may become eth1 rather than eth0 
(this has been PCI slot placement dependent for me).


Here's the /etc/network/interfaces file from my firewall:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto lo eth0 eth1

# The loopback network interface
iface lo inet loopback

# The internal (onboard) network interface
iface eth1 inet static
   address 192.168.1.254
   netmask 255.255.255.0
   network 192.168.1.0
   broadcast 192.168.1.255
   #gateway 192.168.1.254

# The external (pci) network interface
iface eth0 inet static
   address 55.55.55.105
   netmask 255.255.255.0
   network 55.55.55.0
   broadcast 55.55.55.255
   gateway 55.55.55.254


Note the commented out gateway for eth1. Since this is a firewall the 
appropriate gateway is the external one and if both gateways are enabled 
routes get screwed up. I know as I've had this hang me up before...


-Ryan

RE: multiple network cards and dns

[Andrew Critchlow]

That's brilliant thanks for that!
I am going to be setting up a proxy server using Squid with 2 network cards. I 
am right in saying the routing table should have a default out the external 
interface.
Also the reason i was asking about dns is that as im using this box as a proxy 
what dns servers should i specify? Ones on the inside network, the isp's 
(external network), or both of them?
 
 
 
 
many thanks


Date: Sun, 31 Dec 2006 12:30:50 -0700From: [EMAIL PROTECTED]: [EMAIL 
PROTECTED]: Re: multiple network cards and dns
Andrew Critchlow wrote: 


When you have 2 network cards in use with debian with DNS server configured on 
each which one does it choose to query for an address?  Is configuring 2 
network cards on debian as simple as configuring one card?  thanks everyone.DNS 
is a map of names to numbers and numbers to names. You can basically assign any 
name to each IP for each NIC. If you assign the same name to two IP address, 
BIND DNS will rotate the responses in a round robin fashion. So:foo.bar.   IN   
A   192.168.1.1foo.bar.   IN   A   192.168.1.2Will first respond to 
queries:192.168.1.1 192.168.1.2Then will respond:192.168.1.2 192.168.1.1This is 
a load balancing feature of BIND 4.9 and later versions, if this is what you 
are trying to accomplish. Otherwise if it's a firewall, assign a different name 
to the internal and external IPs.Configuring two NICs is as simple as adding 
another entry in /etc/network/interfaces for the new NIC. Be careful as 
sometimes after adding a second NIC the original NIC may become eth1 rather 
than eth0 (this has been PCI slot placement dependent for me).Here's the 
/etc/network/interfaces file from my firewall:# This file describes the network 
interfaces available on your system# and how to activate them. For more 
information, see interfaces(5).auto lo eth0 eth1# The loopback network 
interfaceiface lo inet loopback# The internal (onboard) network interfaceiface 
eth1 inet staticaddress 192.168.1.254netmask 255.255.255.0  
  network 192.168.1.0broadcast 192.168.1.255#gateway 
192.168.1.254# The external (pci) network interfaceiface eth0 inet static   
 address 55.55.55.105netmask 255.255.255.0network 55.55.55.0
broadcast 55.55.55.255gateway 55.55.55.254Note the commented out 
gateway for eth1. Since this is a firewall the appropriate gateway is the 
external one and if both gateways are enabled routes get screwed up. I know as 
I've had this hang me up before...-Ryan

Re: Setting network cards to full duplex at boot...

[Andrei Popescu]

On Wed, Dec 13, 2006 at 08:08:57PM +1300, Simon wrote:
 Hi There,
 
 Is there a way to set network cards to full duplex at boot time?
 
 Thanks Simon

Mine is set that way automatically. It would be helpful if you would
specify which card and chipset, Debian release, kernel version, ...

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Setting network cards to full duplex at boot...

[Mirto Silvio Busico]

Andrei Popescu ha scritto:
 On Wed, Dec 13, 2006 at 08:08:57PM +1300, Simon wrote:
   
 Hi There,

 Is there a way to set network cards to full duplex at boot time?

 Thanks Simon
 

 Mine is set that way automatically. It would be helpful if you would
 specify which card and chipset, Debian release, kernel version, ...

 Regards,
 Andrei
   
Well, I have a switch that doesn' t work well with negotiation. So I
added these  MII lines in /etc/init.d/networking (in the start section):

==
start)
process_options
log_action_begin_msg Configuring network interfaces
if ifup -a; then
log_action_end_msg $?
else
log_action_end_msg $?
fi
/sbin/mii-tool -F 100BaseTx-HD eth0
/sbin/mii-tool -v eth0
;;
==

These have to be done for every network card (HD stays for Half Duplex,
you need FD - Full Duplex - see the mii-tool manual).
For me this works.

Regards
Mirto

-- 

__
Mirto Silvio Busico ICT Consultant
Tel. +39 333 4562651
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Setting network cards to full duplex at boot...

[David Goodenough]

On Wednesday 13 December 2006 08:52, Mirto Silvio Busico wrote:
 Andrei Popescu ha scritto:
  On Wed, Dec 13, 2006 at 08:08:57PM +1300, Simon wrote:
  Hi There,
 
  Is there a way to set network cards to full duplex at boot time?
 
  Thanks Simon
 
  Mine is set that way automatically. It would be helpful if you would
  specify which card and chipset, Debian release, kernel version, ...
 
  Regards,
  Andrei

 Well, I have a switch that doesn' t work well with negotiation. So I
 added these  MII lines in /etc/init.d/networking (in the start section):

 ==
 start)
 process_options
 log_action_begin_msg Configuring network interfaces
 if ifup -a; then
 log_action_end_msg $?
 else
 log_action_end_msg $?
 fi
 /sbin/mii-tool -F 100BaseTx-HD eth0
 /sbin/mii-tool -v eth0
 ;;
 ==

 These have to be done for every network card (HD stays for Half Duplex,
 you need FD - Full Duplex - see the mii-tool manual).
 For me this works.
Theoretically you could also add a line:-
up mii-tool -F 100BaseTx-FD eth0
to /etc/networking/interfaces.  BUT this does not always work, and some
have suggested:-
up sleep 30; mii-tool -F 100BaseTx-FD eth0
Some drivers also support parameters that will force the speed and duplex
settings, but the tg3 driver for one does not.

Some drivers do not work well with mii-tool, for those try ethtool.

David

 Regards
 Mirto

 --

 __
 Mirto Silvio Busico   ICT Consultant
 Tel. +39 333 4562651


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Setting network cards to full duplex at boot...

[Simon]

Hi There,

Is there a way to set network cards to full duplex at boot time?

Thanks Simon


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Two network cards - firewall starts twice or more

[Matus UHLAR - fantomas]

On 16.11.06 08:44, Chris Bannister wrote:
 On Tue, Nov 14, 2006 at 11:44:48AM +0100, Jarek Buczy?ski wrote:
  PS.
  My firewall logs me all messages to console, it's good idea to set 
  KLOGD=-c 4 In /etc/init.d/klogd?
 
 /etc/sysctl.conf

I think that the above (KLOGD=-c 4) is much better. If one uses syslog-ng
(which conflicts with klogd), CONSOLE_LOG_LEVEL=4 can be put into
/etc/default/syslog-ng

-- 
Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
- Holmes, what kind of school did you study to be a detective?
- Elementary, Watson.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Two network cards - firewall starts twice or more

[Chris Bannister]

On Tue, Nov 14, 2006 at 11:44:48AM +0100, Jarek Buczy?ski wrote:
 PS.
 My firewall logs me all messages to console, it's good idea to set 
 KLOGD=-c 4 In /etc/init.d/klogd?

/etc/sysctl.conf

-- 
Chris.
==
 ... the official version cannot be abandoned because the implication of
rejecting it is far too disturbing: that we are subject to a government
conspiracy of `X-Files' proportions and insidiousness.
Letter to the LA Times Magazine, September 18, 2005.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

RE: Two network cards - firewall starts twice or more

[Jarek Buczyński]

Hello

 /etc/sysctl.conf

Could You give me some more information, please

--
Best regards


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

RE: Two network cards - firewall starts twice or more

[David Clymer]

On Thu, 2006-11-16 at 00:54 +0100, Jarek Buczyński wrote: 
 Hello
 
  /etc/sysctl.conf
 
 Could You give me some more information, please
 

man sysctl; man sysctl.conf? ;o)

I think the one you want is kernel.printk

info on what to set it to, here:

http://lists.samba.org/archive/linux/2002-January/001726.html


-davidc

-- 
gpg-key: http://www.zettazebra.com/files/key.gpg


signature.asc
Description: This is a digitally signed message part

RE: Two network cards - firewall starts twice or more

[Jarek Buczyński]

Hello

Thank You for replay

 First of all, you probably don't want to start your firewall prior to
 your interface being brought up (pre-up). This would causa ..

You're right, I've moved my script again to /etc/network/if-up.d. I've
thought it's better have script in if-pre-up.d (more secure, becaouse
firewall starts before interface being brought up, but I was mistaken) 

 To only run when a particular interface is brought up, just check the
 contents of the IFACE before loading the rules:

I've added this to my script and now firewall starts once :) Great
Thanks

PS.
My firewall logs me all messages to console, it's good idea to set 
KLOGD=-c 4 In /etc/init.d/klogd?

--
Best regards


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Two network cards - firewall starts twice or more

[Jarek Buczyński]

Hi All

I have two network cards eth0 (public IP Internet) eth1 (private LAN).
I have firewall script in /etc/network/if-pre-up.d. Unfortunately
when my system boots script runs three times.

How change this (I'd like script starts once)?

--
Best regards


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Two network cards - firewall starts twice or more

[David Clymer]

On Mon, 2006-11-13 at 22:50 +0100, Jarek Buczyński wrote:
 Hi All
 
 I have two network cards eth0 (public IP Internet) eth1 (private LAN).
 I have firewall script in /etc/network/if-pre-up.d. Unfortunately
 when my system boots script runs three times.
 
 How change this (I'd like script starts once)?
 

First of all, you probably don't want to start your firewall prior to
your interface being brought up (pre-up). This would cause any interface
dependant rules to fail to load. For example,

# this will not load if interface eth0 is not up yet.
iptables --in-interface eth0 --destination 192.168.10.50 --jump DROP

Instead, you probably want to load your firewall rules from a post-up
script.

To only run when a particular interface is brought up, just check the
contents of the IFACE before loading the rules:

if [ _$IFACE = _eth1 ]; then
  # load rules here
fi

or something like that. Alternatively, you could specify a script to run
in your network interfaces file:

iface eth0 dhcp
  post-up /script/to/run.sh

-davidc

-- 
gpg-key: http://www.zettazebra.com/files/key.gpg


signature.asc
Description: This is a digitally signed message part

Re: Wireless Network Cards

[Bob]

Magnus Therning wrote:
 On Mon, May 08, 2006 at 05:13:02PM +0200, Jochen Schulz wrote:

[snipped...]

 Your biggest problem will be to find out what chipset a specific card
 you are holding in your hands has. But every project I mentioned
 maintains some sort of compatiblity list.

 Yes, that is a BIG problem. Especially since quite a few manufacturers
 are in the habit of switching the chipset without disclosing that
 anywhere on the boxes :-( When I was shoping around I ended up buying
 from an online store that offered Linux compatible HW. It ended up being
 about £5 more (including shipping) but it was worth not having to worry
 about compatibility.

 The RT cards are also well supported in Linux, the package is called
 rt2500-source and the module can be built with module-assistant.

I don't know what chipset is uses, but I bought a Linksys WMP54G card.
One of the reviews said they'd got it running under Kubuntu via native
support. I'm assuming I'll still need to install this wireless-tools
package. Does anyone now what other kind of config I'll need to do, or
will Debian just pick it up like any other network card...?

Cheers,

--
bob [at] bobarnott [dot] com   http://www.bobarnott.com/

Crash programs fail because they are based on theory that,
 with nine women pregnant, you can get a baby in a month.
-- Wernher von Braun


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wireless Network Cards

[Christoph Nenning]

Am Donnerstag, 18. Mai 2006 18:19 schrieb Bob:
 Magnus Therning wrote:
   On Mon, May 08, 2006 at 05:13:02PM +0200, Jochen Schulz wrote:

 [snipped...]

   Your biggest problem will be to find out what chipset a specific card
   you are holding in your hands has. But every project I mentioned
   maintains some sort of compatiblity list.
  
   Yes, that is a BIG problem. Especially since quite a few manufacturers
   are in the habit of switching the chipset without disclosing that
   anywhere on the boxes :-( When I was shoping around I ended up buying
   from an online store that offered Linux compatible HW. It ended up being
   about £5 more (including shipping) but it was worth not having to worry
   about compatibility.
  
   The RT cards are also well supported in Linux, the package is called
   rt2500-source and the module can be built with module-assistant.

 I don't know what chipset is uses, but I bought a Linksys WMP54G card.
 One of the reviews said they'd got it running under Kubuntu via native
 support. I'm assuming I'll still need to install this wireless-tools
 package. Does anyone now what other kind of config I'll need to do, or
 will Debian just pick it up like any other network card...?

AFAIK there are not much wlan drivers in the kernel, so you have to find out 
which chipset your card uses (with lspci) and install the driver manually. Or 
maybe you are lucky and there is a package for that driver. And configuration 
depends on the driver.

regards

Christoph

Re: Wireless Network Cards

[Rogério Brito]

On May 08 2006, Magnus Therning wrote:
 The RT cards are also well supported in Linux, the package is called
 rt2500-source and the module can be built with module-assistant.

I second that. I have D-Link cards with the rt chipsets and they work
well for my needs under Linux.


Regards, Rogério Brito.

-- 
Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Wireless Network Cards

[Bob]

Hello list, I've never installed a PCI wireless network card before,
I've always run my boxes with wires. However, I've moved to a new house
and the easiest thing to do is put wireless cards in my boxes.

Is it as easy as pluging the card in and it all just working, or do I
need to install some other packages? I'm running Etch with a 2.6 kernel.

Cheers,

--
Bobhttp://www.bobarnott.com/

Lager is an imitation Continental beer drunk only by refined ladies,
 people with digestive ailments, tourists, and other weaklings.
   - Munchen Süddeutsche Zeitung


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Wireless Network Cards

[Matt Zagrabelny]

On Mon, 2006-05-08 at 15:42 +0100, Bob wrote:
 Hello list, I've never installed a PCI wireless network card before,
 I've always run my boxes with wires. However, I've moved to a new house
 and the easiest thing to do is put wireless cards in my boxes.
 
 Is it as easy as pluging the card in and it all just working, or do I
 need to install some other packages? I'm running Etch with a 2.6 kernel.

# aptitude install wireless-tools

you may need to compile some modules or whatnot, i compile my own
kernels, so i cannot speak about the debian kernels.

-- 
Matt Zagrabelny - [EMAIL PROTECTED] - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems  Services
PGP key 1024D/84E22DA2 2005-11-07
Fingerprint: 78F9 18B3 EF58 56F5 FC85  C5CA 53E7 887F 84E2 2DA2

He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot


signature.asc
Description: This is a digitally signed message part

Re: Wireless Network Cards

[Jochen Schulz]

Bob:
 
 Is it as easy as pluging the card in and it all just working, or do I
 need to install some other packages? I'm running Etch with a 2.6 kernel.

It depends on your card. And most probably (if you go out and just buy
some random card) it will involve some work. It may even be impossible
if you pick the wrong card.

You might want to google around for supported cards. Chipsets which I
have positive experience with are prism54, ipw2100, ipw2200 and the
atheros chips (supported by madwifi). All except the latter one are in
the vanilla kernel (but I don't think there are PCI versions of the ipw
chips). It helps if you know how to compile a custom kernel and/or how
to compile kernel modules against the appropriate linux-headers package.

Your biggest problem will be to find out what chipset a specific card
you are holding in your hands has. But every project I mentioned
maintains some sort of compatiblity list.

J.
-- 
If I won the lottery I would keep all the money and wallpaper my house
with it.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Re: Wireless Network Cards

[Magnus Therning]

On Mon, May 08, 2006 at 05:13:02PM +0200, Jochen Schulz wrote:
Bob:
 
 Is it as easy as pluging the card in and it all just working, or do I
 need to install some other packages? I'm running Etch with a 2.6 kernel.

It depends on your card. And most probably (if you go out and just buy
some random card) it will involve some work. It may even be impossible
if you pick the wrong card.

You might want to google around for supported cards. Chipsets which I
have positive experience with are prism54, ipw2100, ipw2200 and the
atheros chips (supported by madwifi). All except the latter one are in
the vanilla kernel (but I don't think there are PCI versions of the ipw
chips). It helps if you know how to compile a custom kernel and/or how
to compile kernel modules against the appropriate linux-headers
package.

Your biggest problem will be to find out what chipset a specific card
you are holding in your hands has. But every project I mentioned
maintains some sort of compatiblity list.

Yes, that is a BIG problem. Especially since quite a few manufacturers
are in the habit of switching the chipset without disclosing that
anywhere on the boxes :-( When I was shoping around I ended up buying
from an online store that offered Linux compatible HW. It ended up being
about £5 more (including shipping) but it was worth not having to worry
about compatibility.

The RT cards are also well supported in Linux, the package is called
rt2500-source and the module can be built with module-assistant.

/M

-- 
Magnus Therning(OpenPGP: 0xAB4DFBA4)
[EMAIL PROTECTED]
http://therning.org/magnus

Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

Here's the social reason that DRM fails: keeping an honest user honest
is like keeping a tall user tall.
 -- Cory Doctorow, Microsoft Research DRM talk


pgpDhnL7KvSQt.pgp
Description: PGP signature

Re: Wireless Network Cards

[Jan Schledermann]

Magnus Therning wrote:

snip
 
 Yes, that is a BIG problem. Especially since quite a few manufacturers
 are in the habit of switching the chipset without disclosing that
 anywhere on the boxes :-( When I was shoping around I ended up buying
 from an online store that offered Linux compatible HW. It ended up being
 about £5 more (including shipping) but it was worth not having to worry
 about compatibility.
 
 The RT cards are also well supported in Linux, the package is called
 rt2500-source and the module can be built with module-assistant.
 
 /M
 

Ofcourse native Linux support is politically more correct.
However ndiswrapper with the Windoze driver will also do the trick.
Jan

-- 
** Do NOT use the reply-to address. You'll end up in the trash can
** Mail me at: jan AT schledermann D0T org 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian and wireless network cards

[Thomas H. George]

On Sat, Jul 23, 2005 at 09:07:50AM -0400, Thomas H. George wrote:
 On Thu, Jul 21, 2005 at 08:06:17PM -0400, Leonid Grinberg wrote:
  Hello,
  
  I was asked by a friend to install Debian on his system. He asked me
  about which wireless network cards Debian supports. Can anybody tell
  me which ones (I personally don't use a wireless network so I wouldn't
  know).
 
 I posted this question last week when I lost the antenna to my Netgear
 MA211 wireless lan card and was advised the best uptodate info was at
 
   http://Linux-Wireless.org
 
 That didn't help much.  I then went to 
 
   www.linux-wlan.org/docs/wlan-adapters.html.gz
 
 because I use the linux-wlan-ng=0.2.1-pre26 driver with my Netgear MA311
 card.  From the table I ordered a 3com 3crdw696 PCI wireless lan card
 for my second computer.  I have not yet received the card and will
 confirm that it works with the linux-wlan-ng driver when it comes.  This
 is old technology - 802.11b - but with a DSL connection downloads run at
 70 to 90 kBps.  New 3com cards were being sold at $ 29.

The 3com card does work with the linux-wlan-ng driver but the range is
terrible.  In the same location where the Netgear MA311 card is
connecting with a weak but acceptable signal the 3com card drops 25% of
the packets when pinging the base station.
 
 Others may have better advice - it was frustrating trying to find the
 latest and best information.
 
 Tom George
 
  
  Thanks,
  Leonid Grinberg
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian and wireless network cards

[Nate Duehr]

Thomas H. George wrote:


Others may have better advice - it was frustrating trying to find the
latest and best information.


Mostly the manufacturer's fault.  When there's four devices called 
[model number] and no version numbers, who's to blame for all the 
confusion?


Or perhaps they enjoy confusing customers who buy their products based 
on the product name.


Still looking for a hardware vendor to support that is actively avoiding 
this silliness who also provides ample support to the Linux driver 
writers for their cards.


Nate


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian and wireless network cards

[Thomas H. George]

On Thu, Jul 21, 2005 at 08:06:17PM -0400, Leonid Grinberg wrote:
 Hello,
 
 I was asked by a friend to install Debian on his system. He asked me
 about which wireless network cards Debian supports. Can anybody tell
 me which ones (I personally don't use a wireless network so I wouldn't
 know).

I posted this question last week when I lost the antenna to my Netgear
MA211 wireless lan card and was advised the best uptodate info was at

http://Linux-Wireless.org

That didn't help much.  I then went to 

www.linux-wlan.org/docs/wlan-adapters.html.gz

because I use the linux-wlan-ng=0.2.1-pre26 driver with my Netgear MA311
card.  From the table I ordered a 3com 3crdw696 PCI wireless lan card
for my second computer.  I have not yet received the card and will
confirm that it works with the linux-wlan-ng driver when it comes.  This
is old technology - 802.11b - but with a DSL connection downloads run at
70 to 90 kBps.  New 3com cards were being sold at $ 29.

Others may have better advice - it was frustrating trying to find the
latest and best information.

Tom George

 
 Thanks,
 Leonid Grinberg


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian and wireless network cards

[Damon Chesser]

On Thursday 21 July 2005 19:06, Leonid Grinberg wrote:
 Hello,

 I was asked by a friend to install Debian on his system. He asked me
 about which wireless network cards Debian supports. Can anybody tell
 me which ones (I personally don't use a wireless network so I wouldn't
 know).

 Thanks,
 Leonid Grinberg
Leonid,
Two cards have worked for me: 1. SMC EX Connect G Mod# SMC2835W it uses the 
Prism54 driver which is in 2.6 series kernel, you need to download the 
Firmware (a file the tells the card how to work) and put it 
in /usr/lib/hotplug/firmware ( see http://prism54.org/~mcgrof/firmware/ and 
www.prism54.org )

2. Orinoco gold 11b/g PC card Mod# 8470-FC .  This card is by far the better 
of the two in that it allows you to use WPA if you need it.  Both use WEP.  
The Orinoco uses Atheros drivers and is slightly harder to install.  see 
http://sourceforge.net/projects/madwifi/, http://madwifi.sourceforge.net/, 
the best up and running instructions are http://www.madwifi.net/.  You will 
need to have a dev. environment set up (gcc, debhelper, sysutils, and a few 
more I don't remember) But don't dispare!  on irc Freenode server #madwifi 
channel you can get friendly help.  It all is realy easy, but time consuming 
the first time and requires a kernel compile or kernel headers installed.  

I hope that helps.  Yes it all is very hard to get info on wireless.  But that 
is becuse of the MFG all just change the chipset on the fly and don't bother 
to change the model numbers.  That and the drivers are protected IP (such as 
the Prism54 family) and have to be backwards engineered.  


-- 
Damon L. Chesser
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian and wireless network cards

[Damon Chesser]

On Thursday 21 July 2005 19:06, Leonid Grinberg wrote:
 Hello,

 I was asked by a friend to install Debian on his system. He asked me
 about which wireless network cards Debian supports. Can anybody tell
 me which ones (I personally don't use a wireless network so I wouldn't
 know).

 Thanks,
 Leonid Grinberg
Leonid,
Two cards have worked for me: 1. SMC EX Connect G Mod# SMC2835W it uses the 
Prism54 driver which is in 2.6 series kernel, you need to download the 
Firmware (a file the tells the card how to work) and put it 
in /usr/lib/hotplug/firmware ( see http://prism54.org/~mcgrof/firmware/ and 
www.prism54.org )

2. Orinoco gold 11b/g PC card Mod# 8470-FC .  This card is by far the better 
of the two in that it allows you to use WPA if you need it.  Both use WEP.  
The Orinoco uses Atheros drivers and is slightly harder to install.  see 
http://sourceforge.net/projects/madwifi/, http://madwifi.sourceforge.net/, 
the best up and running instructions are http://www.madwifi.net/.  You will 
need to have a dev. environment set up (gcc, debhelper, sysutils, and a few 
more I don't remember) But don't dispare!  on irc Freenode server #madwifi 
channel you can get friendly help.  It all is realy easy, but time consuming 
the first time and requires a kernel compile or kernel headers installed.  

I hope that helps.  Yes it all is very hard to get info on wireless.  But that 
is becuse of the MFG all just change the chipset on the fly and don't bother 
to change the model numbers.  That and the drivers are protected IP (such as 
the Prism54 family) and have to be backwards engineered.  

Addendium: Omitted the first time:

The Orinoco goes by the name of Proxim and  can be purchased online.  To use 
WPA I advise you apt-getting wpasupplicant.  
Read /usr/share/doc/wpasupplicant to set it up.  Once again, it is easy, but 
you have to read.


-- 
Damon L. Chesser
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian and wireless network cards

[Brian Kimball]

I just solved this dilemma two days ago.  I found the hawking hwp54g 
works well and is pretty inexpensive.  Hawking has used a few different 
chipsets but IIRC they all have linux drivers in varying degrees of 
development.  The one that I bought has a Ralink rt2500 chipset, and 
the driver for it is actually based on code donated to the community 
from Ralink, which is always a good sign.

http://www.hawkingtech.com/prodSpec.php?ProdID=180
http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page


Leonid Grinberg wrote:
 Hello,

 I was asked by a friend to install Debian on his system. He asked me
 about which wireless network cards Debian supports. Can anybody tell
 me which ones (I personally don't use a wireless network so I
 wouldn't know).

 Thanks,
 Leonid Grinberg


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian and wireless network cards

[Maykon Silveira]

I have an D-link DWL-650 working with Debian Sarge kernel 2.6.

2005/7/21, Leonid Grinberg [EMAIL PROTECTED]:
 Hello,
 
 I was asked by a friend to install Debian on his system. He asked me
 about which wireless network cards Debian supports. Can anybody tell
 me which ones (I personally don't use a wireless network so I wouldn't
 know).
 
 Thanks,
 Leonid Grinberg
 
 


-- 
Maykon Silveira

Debian and wireless network cards

[Leonid Grinberg]

Hello,

I was asked by a friend to install Debian on his system. He asked me
about which wireless network cards Debian supports. Can anybody tell
me which ones (I personally don't use a wireless network so I wouldn't
know).

Thanks,
Leonid Grinberg

Re: Debian and wireless network cards

[Alvin Oga]

On Thu, 21 Jul 2005, Leonid Grinberg wrote:

 Hello,
 
 I was asked by a friend to install Debian on his system. He asked me
 about which wireless network cards Debian supports. Can anybody tell
 me which ones (I personally don't use a wireless network so I wouldn't
 know).

all wireless cards will work  if you're willing to sacrifice features
- linux can use the ndiswrapper and use the windoze driver
from the cdrom that came with the nic



if you want to build a wireless AP or wpa ..

- you will need either the hostap driver or madwifi driver
and see which cards it supports

- be careful of old models and new models with the same part
number but differs in which wifi chip is used on the pci/pcmcia 
cards

---

if you want wep, you can use most any other linux supported wifi cards

- if you're using wep as your security mechanism, 
than consider your machine pre-hacked and keep all your
bank info elsewhere


- run everything with ssh/ssl if you're paranoid 
ssh, pop3s, imaps, https, ..

---

easier way:
a. see what is on sale and search for the linux drivers
b. see what your buddy is using and use that wifi card


more wifi fun
Linux-Wireless.org

c ya
alvin

-- for those that are looking to do a mediaum range 5-10 miles wifi,
   i've got two 24db wifi antenna that we'll be testing


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Problems with network cards in old board

[Jim MacBaine]

Hello,

I'm trying to replace a 10MBit card in an older computer by a 100MBit
card. The system is an Pentium-133, PIIX chipset, running Sarge with
kernel-image-2.6.8-1-386.  Previously the system had an 10Mbit Intel
EEPro ISA card, which worked flawlessly. The system is an X terminal.

First I tried a D-Link DFE-530TX, which normally runs flawlessly in
other systems with sarge.  The via-rhine driver for this card loads,
creates eth0, detects a 100Mbit FD link, but when I try to send data,
I see eth0: transmit timed out.

Then I tried a 3Com 3C905C-TX-M card, which also runs with Sarge in
other systems. This time the kernel tells me Warning: IRQ 0 is
unlikely to work. and advises me to use pci=biosirq.  I tried that
too: This parameter makes the kernel oops, before it comes to
userspace.

I also tried to assign an irq in the bios manually, but this has no
effects.  Can anybody give me a tip, how to get this to work?

Kind regards,
Jim

Re: Switching between two network cards

[Andrei Badea]

Karl E. Jorgensen wrote:
On Thu, Oct 07, 2004 at 10:54:35PM +0200, Andrei Badea wrote:
...
I've got two network cards: one integrated on my motherboard 
(uses the sk98lin driver) and a PCI card (fealnx driver). Both drivers are 
compiled as modules and upon startup I'm loading only fealnx via 
/etc/modules (I'm not loading sk98lin at all). The network runs fine.

After my system starts, I want to switch to the other network card (the 
sk98lin one), but I only want its module loaded, so I do:

ifdown eth0
rmmod fealnx
modprobe sk98lin
ifup eth0
Why not load *both* modules all the time (i.e. put them both in
/etc/modules), and then simply use:
ifdown eth0
ifup eth1
and
ifdown eth1
ifup eth0
to switch?
The order in /etc/modules then dictates which one becomes eth0 and which
one becomes eth1.
This works fine, however, I wanted to have only one module in memory since 
I'm only needing one. More about this at the end of my reply.

It sounds like the two drivers are dissagreeing with being unloaded, but
there isn't much to go on.  Do you get anything in dmesg (~
/var/log/kern.log) when you load/unload the modules?  Is it different if
you boot with the other module loaded?
Whoops, dmesg shows this when unloading sk98lin:
Badness in remove_proc_entry at fs/proc/generic.c:692
 [c01726c3] remove_proc_entry+0xfa/0x137
 [e08df2e1] skge_cleanup_module+0xcd/0x1db [sk98lin]
 [c0127aee] sys_delete_module+0x143/0x17b
 [c013cd4c] do_munmap+0x142/0x17f
 [c010590f] syscall_call+0x7/0xb
This would mean that sk98lin doesn't like to be unloaded, so I can't boot 
with sk98lin, then unload it and load fealnx and expect it to work. 
However, I could at least expect the opposite order (boot with fealnx, 
unload it and load sk98lin) to work, but it doesn't either. Fealnx doesn't 
give any error messages, even when I load it with debug=1.

To conclude, loading both modules on startup and then switching their 
loading order causes both eth0 and eth1 to stop working.

Messages in dmesg say the network is up and running. But it isn't, it 
seems I can't ping nor make net connections. However, when I (for example) 
run a ping and look at the LEDs on the card, I see them bliking in the 
ping way. I can also see the echo request and reply packets in tcpdump. 
But ping doesn't get them and reports 100% loss.
!? If this is tcpdump on the same machine, then I'm thoroughly
confused..
Yep, this is tcpdump on the same machine. It behaves a litte strangely 
though. About 20 seconds after I run it, it doesn't show any packets, 
though I have a ping running in another terminal. It doesn't respond to 
Ctrl+C in these 20 secs.

If this is tcpdump on another box on the same network (more likely I
hope), then the firewalling rules should be eyeballed. 

and which maching is doing the pinging?
My machine.
If I unload sk98lin and reload fealnx, the net works fine. Now comes the 
interesting part: if I put sk98lin in /etc/modules instead of fealnx and 
restart, the net comes up. Only this time I can't switch to fealnx. This 
shows both the cards are working.
Have you ever had both working at the same time? 
I loaded both modules and switch from eth0 to eth1 and backwards using 
ifup/ifdown. This works.

I thought this was caused by iptables settings, so after loading the other 
module I rerun the script which setups my firewall rules. Didn't help.
Assuming that you use the same firewalling rules all the time, that
indicates that the firewalling rules are not the problem here.
But you can make your firewalling rules generic by specifying eth+
rather than eth0 (i.e. it will match all interfaces starting with
eth).
I don't specify the interface in any of my firewall rules.
To completely eliminate the possiblity of bad firewalling rules, you
could try clearing them
/etc/init.d/iptables clear
and try again. I'm not 100% sure that the firewalling rules can be
eliminated as the cause.
A related question: How do you reload the firewalling rules? Are they
being cleared down first? i.e. is there an accumulative effect going
on here?
I have a Bash script containing iptables calls. Its first commands are:
iptables -F
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT ACCEPT
Not that is it important, as my net is 
running with any of the cards if I restart, I'm just curious. However, I'd 
like to point out that I don't want both modules to be loaded. I want to 
be able to unload the running one and load another without having to 
restart.
But why insist on unloading the other module? Why isn't ifdown
sufficient?  

I assume that there is a reason (surely it cannot be because you don't
want an eth1, is it?), but it is not clear from your post.  

There may be different ways of solving your original problem
PS: Why put an extra network card in the box if you only want to use one
network at any given time?
This is not a problem actually. I had a PCI card in my machine and I 
recently bought a mainboard which contains an integrated

Re: Switching between two network cards

[Andrei Badea]

Jason Rennie wrote:
On Thu, Oct 07, 2004 at 10:54:35PM +0200, Andrei Badea wrote:
After my system starts, I want to switch to the other network card (the 
sk98lin one), but I only want its module loaded, so I do:

ifdown eth0
rmmod fealnx
modprobe sk98lin
ifup eth0
I'm no expert in networking.  Might be totally off base here.  But,
could it be that fealnx gets eth0 and sk98lin gets eth1?  i.e. might
this work?
ifdown eth0
modprobe sk98lin
ifup eth1
This works. But I have to keep fealnx loaded, which is exactly what I 
don't want. If I unload fealnx before modprobing sk98lin, then sk98lin 
gets eth0 and it doesn't work.

Andrei
--
[EMAIL PROTECTED] # http://movzx.net # ICQ: 52641547


signature.asc
Description: OpenPGP digital signature

Re: Switching between two network cards

[Jason Rennie]

On Thu, Oct 07, 2004 at 10:54:35PM +0200, Andrei Badea wrote:
 After my system starts, I want to switch to the other network card (the 
 sk98lin one), but I only want its module loaded, so I do:
 
 ifdown eth0
 rmmod fealnx
 modprobe sk98lin
 ifup eth0

I'm no expert in networking.  Might be totally off base here.  But,
could it be that fealnx gets eth0 and sk98lin gets eth1?  i.e. might
this work?

ifdown eth0
modprobe sk98lin
ifup eth1

I have a vaguely similar situation w/ my laptop...  When undocked, the
PCMCIA card gets eth0, when docked, the dock station ethernet gets
eth0 and PCMCIA card gets eth1.  I use the check-mac-address.sh script
to make sure that only the PCMCIA card gets networking.  Something
similar might work for you if you don't want fealnx to come up at all.

Jason


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Switching between two network cards

[Karl E. Jorgensen]

On Thu, Oct 07, 2004 at 10:54:35PM +0200, Andrei Badea wrote:
 ...
 I've got two network cards: one integrated on my motherboard 
 (uses the sk98lin driver) and a PCI card (fealnx driver). Both drivers are 
 compiled as modules and upon startup I'm loading only fealnx via 
 /etc/modules (I'm not loading sk98lin at all). The network runs fine.
 
 After my system starts, I want to switch to the other network card (the 
 sk98lin one), but I only want its module loaded, so I do:
 
 ifdown eth0
 rmmod fealnx
 modprobe sk98lin
 ifup eth0

Why not load *both* modules all the time (i.e. put them both in
/etc/modules), and then simply use:
ifdown eth0
ifup eth1
and
ifdown eth1
ifup eth0
to switch?

The order in /etc/modules then dictates which one becomes eth0 and which
one becomes eth1.

It sounds like the two drivers are dissagreeing with being unloaded, but
there isn't much to go on.  Do you get anything in dmesg (~
/var/log/kern.log) when you load/unload the modules?  Is it different if
you boot with the other module loaded?

Some modules can be enticed into giving more verbose information... I
don't have those modules available, but 
modinfo fealnx
modinfo sk98lin
should give information about the module-specific options. In either
case, the kernel docs for those modules should be handy...

 Messages in dmesg say the network is up and running. But it isn't, it 
 seems I can't ping nor make net connections. However, when I (for example) 
 run a ping and look at the LEDs on the card, I see them bliking in the 
 ping way. I can also see the echo request and reply packets in tcpdump. 
 But ping doesn't get them and reports 100% loss.

!? If this is tcpdump on the same machine, then I'm thoroughly
confused..

If this is tcpdump on another box on the same network (more likely I
hope), then the firewalling rules should be eyeballed. 

and which maching is doing the pinging?

 If I unload sk98lin and reload fealnx, the net works fine. Now comes the 
 interesting part: if I put sk98lin in /etc/modules instead of fealnx and 
 restart, the net comes up. Only this time I can't switch to fealnx. This 
 shows both the cards are working.

Have you ever had both working at the same time? 

 I thought this was caused by iptables settings, so after loading the other 
 module I rerun the script which setups my firewall rules. Didn't help.

Assuming that you use the same firewalling rules all the time, that
indicates that the firewalling rules are not the problem here.

But you can make your firewalling rules generic by specifying eth+
rather than eth0 (i.e. it will match all interfaces starting with
eth).

To completely eliminate the possiblity of bad firewalling rules, you
could try clearing them
/etc/init.d/iptables clear
and try again. I'm not 100% sure that the firewalling rules can be
eliminated as the cause.

A related question: How do you reload the firewalling rules? Are they
being cleared down first? i.e. is there an accumulative effect going
on here?

 Not that is it important, as my net is 
 running with any of the cards if I restart, I'm just curious. However, I'd 
 like to point out that I don't want both modules to be loaded. I want to 
 be able to unload the running one and load another without having to 
 restart.

But why insist on unloading the other module? Why isn't ifdown
sufficient?  

I assume that there is a reason (surely it cannot be because you don't
want an eth1, is it?), but it is not clear from your post.  

There may be different ways of solving your original problem

PS: Why put an extra network card in the box if you only want to use one
network at any given time?

Hope this helps

-- 
Karl E. Jørgensen
[EMAIL PROTECTED]   http://karl.jorgensen.com
 Today's fortune:
When you say that you agree to a thing in principle, you mean that
you have not the slightest intention of carrying it out in practice.
-- Otto Von Bismarck


signature.asc
Description: Digital signature

Switching between two network cards

[Andrei Badea]

Hello all,
this is not quite a Debian related problem (except that I'm running sid), 
but anyway... I've got two network cards: one integrated on my motherboard 
(uses the sk98lin driver) and a PCI card (fealnx driver). Both drivers are 
compiled as modules and upon startup I'm loading only fealnx via 
/etc/modules (I'm not loading sk98lin at all). The network runs fine.

After my system starts, I want to switch to the other network card (the 
sk98lin one), but I only want its module loaded, so I do:

ifdown eth0
rmmod fealnx
modprobe sk98lin
ifup eth0
Messages in dmesg say the network is up and running. But it isn't, it 
seems I can't ping nor make net connections. However, when I (for example) 
run a ping and look at the LEDs on the card, I see them bliking in the 
ping way. I can also see the echo request and reply packets in tcpdump. 
But ping doesn't get them and reports 100% loss.

If I unload sk98lin and reload fealnx, the net works fine. Now comes the 
interesting part: if I put sk98lin in /etc/modules instead of fealnx and 
restart, the net comes up. Only this time I can't switch to fealnx. This 
shows both the cards are working.

I thought this was caused by iptables settings, so after loading the other 
module I rerun the script which setups my firewall rules. Didn't help.

I'm running Debian sid with self-compiled kernel 2.6.7.
Any ideas why this is happening? Not that is it important, as my net is 
running with any of the cards if I restart, I'm just curious. However, I'd 
like to point out that I don't want both modules to be loaded. I want to 
be able to unload the running one and load another without having to restart.

Thanks in advance!
Best regards,
Andrei
--
[EMAIL PROTECTED] # http://movzx.net # ICQ: 52641547


signature.asc
Description: OpenPGP digital signature

RE: Switching between two network cards

[Steven Jones]

I dont quite understand why you need to switch, you could just run everything off 
eth1, but anyway,

I would suggest looking in your bios and either disabling the onboard NIC, or changing 
the PCI probe order eg if its says first-last change it to last-first or what ever 
syntax your bios uses.

However Its most likely that the onboard can simply be disabled in the bios.

regards

Steven

-Original Message-
From: Andrei Badea [mailto:[EMAIL PROTECTED]
Sent: Friday, 8 October 2004 9:55 a.m.
To: Debian User List
Subject: Switching between two network cards


Hello all,

this is not quite a Debian related problem (except that I'm running sid), 
but anyway... I've got two network cards: one integrated on my motherboard 
(uses the sk98lin driver) and a PCI card (fealnx driver). Both drivers are 
compiled as modules and upon startup I'm loading only fealnx via 
/etc/modules (I'm not loading sk98lin at all). The network runs fine.

After my system starts, I want to switch to the other network card (the 
sk98lin one), but I only want its module loaded, so I do:

ifdown eth0
rmmod fealnx
modprobe sk98lin
ifup eth0

Messages in dmesg say the network is up and running. But it isn't, it 
seems I can't ping nor make net connections. However, when I (for example) 
run a ping and look at the LEDs on the card, I see them bliking in the 
ping way. I can also see the echo request and reply packets in tcpdump. 
But ping doesn't get them and reports 100% loss.

If I unload sk98lin and reload fealnx, the net works fine. Now comes the 
interesting part: if I put sk98lin in /etc/modules instead of fealnx and 
restart, the net comes up. Only this time I can't switch to fealnx. This 
shows both the cards are working.

I thought this was caused by iptables settings, so after loading the other 
module I rerun the script which setups my firewall rules. Didn't help.

I'm running Debian sid with self-compiled kernel 2.6.7.

Any ideas why this is happening? Not that is it important, as my net is 
running with any of the cards if I restart, I'm just curious. However, I'd 
like to point out that I don't want both modules to be loaded. I want to 
be able to unload the running one and load another without having to restart.

Thanks in advance!

Best regards,
Andrei

-- 
[EMAIL PROTECTED] # http://movzx.net # ICQ: 52641547

Re: Switching between two network cards

[Andrei Badea]

Steven Jones wrote:
I dont quite understand why you need to switch, you could just run everything off eth1, but anyway,
I don't need to switch. It's just that it's not doing what I think it 
should do and I want to know why.

I would suggest looking in your bios and either disabling the onboard NIC, or changing 
the PCI probe order eg if its says first-last change it to last-first or what ever 
syntax your bios uses.
However Its most likely that the onboard can simply be disabled in the bios.
I don't want to disable the onboard card. I have two different NICs in my 
computer using two different drivers and I want to load only _one_ of the 
drivers at a time and be able to switch among them:

load driver A (on startup)
... work
unload A, load B
... work
unload B, load A
... work
and so on. Again I have to mention it's rather an academic question - I 
don't really need it, I just want to know why it's not doing what I 
supposed it would do.

Best regards,
Andrei
--
[EMAIL PROTECTED] # http://movzx.net # ICQ: 52641547


signature.asc
Description: OpenPGP digital signature

Re: booting with same destop / app setup different video and network cards

[Åsmund Ødegård]

On Wed, 2004-04-14 at 12:23, Robert Fernando -ntlworld wrote:
  Hi all, Is it possible to configure linux to either auto detect a
  change in Ethernet and video card or allow manual selection of the
  correct drivers at boot time.  I.e. so that one hardisk can be shared
  between two pc with different hardware.
  
  Can the x Windows system be setup to use Intel Agp 470 video card in
  one config and a Diamond Stealth 2500 in a another pc/ configuration
  ?

 You might run a script from init which check the output from lspci, and
 adjust your config files accrodingly. Something like:

 if [ lspci | grep -q 'VGA.*Diamond' ] ; then
cp /etc/X11/XF86Config-4.diamond /etc/X11/XF86Config-4
 else
cp /etc/X11/XF86Config-4.intel /etc/X11/XF86Config-4
 fi

 and something similar with the ethernet. The ethernet I guess can be
 handled with proper use of modules, though.
 
-- 
[simula.research laboratory]
 smund degrd
 IT-Manager
 phone: +4767828291 / +4790069915
 http://www.simula.no

booting with same destop / app setup different video and network cards

[Robert Fernando -ntlworld]

Hi all,
Is it possible to configure linux to either auto detect a change in Ethernet
and video card or allow manual selection of the correct drivers at boot
time.
I.e. so that one hardisk can be shared between two pc with different
hardware.

Can the x Windows system be setup to use Intel Agp 470 video card in one
config and a Diamond Stealth 2500 in a another pc/ configuration ?

thanks
Robert Fernando
www.rowanclose.com

Robert Fernando
www.rowanclose.com
Fax +44(0)870-133-1992


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.657 / Virus Database: 422 - Release Date: 13/04/2004


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

ISA network cards

[jleclair]

I'm trying to set up an old 486 as router/nat/firewall server for home network. The 2 
nics are dlink 220 isa. 
When I run modconf, I choose the NE net module with this parameter: 
   io=0x300
This works and the module loads for eth0. How do I load the module now for the second 
nic?
I dont know the io address of the 2nd nic and the module will only load once. I guess 
I could do something like:  io=0x240,0x300 when loading the module through modconf.
BTW, I guessed at the io address that DID respond and have since unloaded the module 
and tried every other io address to make the second nic work. Are there tools to probe 
for hardware responding on io addresses not listed  
in /etc/proc?
I know this is all quite vague, but I am completely PCI plug-n-play spoiled.
Thanks for any assistance!
James  
   
   
   
   
   
   
   
  


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ISA network cards

[Derrick 'dman' Hudson]

On Thu, Aug 21, 2003 at 12:36:35PM -0300, jleclair wrote:
| 
| I'm trying to set up an old 486 as router/nat/firewall server for
| home network. The 2 nics are dlink 220 isa. 
| When I run modconf, I choose the NE net module with this parameter: 
|io=0x300
| This works and the module loads for eth0. How do I load the module
| now for the second nic?

I have a 486 with 2 Netgear EA211 cards in it.  They're also an 'ne'
clone.  I have the following in /etc/modutils/local.conf

alias eth0 ne
alias eth1 ne
options ne io=0x300,0x320

(after editing a file in /etc/modutils run 'update-modules')
This is all that I need.

| I dont know the io address of the 2nd nic

You need to find this out.  ISA isn't so friendly when it comes to
auto-probing.

| and the module will only
| load once. I guess I could do something like:  io=0x240,0x300 when
| loading the module through modconf.

That would probably work, if the addresses are correct, because that's
the same syntax I have in my config file.

| BTW, I guessed at the io address that DID respond and have since
| unloaded the module and tried every other io address to make the
| second nic work. Are there tools to probe for hardware responding on
| io addresses not listed in /etc/proc?

I think there are some, but I don't have any familiarity with them.
The main issue with such tools is that probing certain ISA devices
will cause the system to lock up.  That's just the way ISA works.
(and one good reason for PCI to have superseded it)

HTH,
-D

-- 
Folly delights a man who lacks judgement,
but a man of understanding keeps a straight course.
Proverbs 15:21
 
http://dman13.dyndns.org/~dman/


pgp0.pgp
Description: PGP signature

Re: ISA network cards

[mess-mate]

Hi,
On Thu, 21 Aug 2003 12:36:35 -0300
jleclair [EMAIL PROTECTED] wrote:

|
|I'm trying to set up an old 486 as router/nat/firewall server for home network. The 2 
nics are dlink 220 isa. 
|When I run modconf, I choose the NE net module with this parameter: 
|   io=0x300
|This works and the module loads for eth0. How do I load the module now for the second 
nic?
|I dont know the io address of the 2nd nic and the module will only load once. I guess 
I could do something like:  io=0x240,0x300 when loading the module through modconf.
|BTW, I guessed at the io address that DID respond and have since unloaded the module 
and tried every other io address to make the second nic work. Are there tools to probe 
for hardware responding on io addresses not listed  
|in /etc/proc?
|I know this is all quite vague, but I am completely PCI plug-n-play spoiled.
|Thanks for any assistance!
|James 
   
   
   
If they are isa then (informatical) you need 'isapnptools' and to 
do a isapnp dump.
Then a config of  /etc/isapnp.conf is needed. There you chose the irq and the io(s) 
of your cards. (uncomment these lines)
The isapnptools must be started at boot of course.
The rest is a config of your cards as eth0 and eth1.
   mess-mate   
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ISA network cards

[Erik Steffl]

jleclair wrote:
I'm trying to set up an old 486 as router/nat/firewall server for home network. The 2 nics are dlink 220 isa. 
When I run modconf, I choose the NE net module with this parameter: 
   io=0x300
This works and the module loads for eth0. How do I load the module now for the second nic?
I dont know the io address of the 2nd nic and the module will only load once. I guess I could do something like:  io=0x240,0x300 when loading the module through modconf.
BTW, I guessed at the io address that DID respond and have since unloaded the module and tried every other io address to make the second nic work. Are there tools to probe for hardware responding on io addresses not listed  
in /etc/proc?
...

  I think you need isapnptools

	erik

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

ISA network cards

[jleclair]

Can anyone assist me installing a d-link 220 isa nic? The OS is woody, and the 
platform is intel 486. The install routine doesnt see the card. Have also tried a few 
modules but no auto-probing was successful. Guess I have been spoiled with PCI plug n 
play! A nod to a good link with documentation or whatever would be great.
Thanks,
James


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ISA network cards

[Kenward Vaughan]

On Sat, Aug 16, 2003 at 01:32:27PM -0300, jleclair wrote:
 
 Can anyone assist me installing a d-link 220 isa nic? The OS is woody, and
 the platform is intel 486. The install routine doesnt see the card. Have
 also tried a few modules but no auto-probing was successful. Guess I have
 been spoiled with PCI plug n play! A nod to a good link with documentation
 or whatever would be great. 

Try the Ethernet HOWTO, section X.YY.Z.   

(Your line wrapping is non-existent, BTW. :-)


Kenward
-- 
In a completely rational society, the best of us would aspire to be 
_teachers_ and the rest of us would have to settle for something less, 
because passing civilization along from one generation to the next 
ought to be the highest honor and the highest responsibility anyone 
could have. - Lee Iacocca


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ISA network cards

[Andreas Janssen]

Hello

jleclair ([EMAIL PROTECTED]) wrote:

 Can anyone assist me installing a d-link 220 isa nic? The OS is woody,
 and the platform is intel 486. The install routine doesnt see the
 card. Have also tried a few modules but no auto-probing was
 successful. Guess I have been spoiled with PCI plug n play! A nod to a
 good link with documentation or whatever would be great. Thanks, James

The card seems to be supported by the ne module. If you want to use it
with plug and play, make sure the isa-pnp module is loaded first (I
think only kernel 2.4 has this). You can also specify the irq and i/o
values manually. And you can take a look at the isapnptools package.
And of course going to google.com or groups.google.com and searching
for something like d-link 220 isa kernel module will probably give
you some information.

best regards
Andreas Janssen

-- 
Andreas Janssen
[EMAIL PROTECTED]
PGP-Key-ID: 0xDC801674
Registered Linux User #267976


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: multiple network cards bound together

[Nathan E Norman]

On Wed, Aug 13, 2003 at 09:16:42AM -0400, D. Clarke wrote:
 Hi!
 
 Is it possible to bind multiple (non matching, or matching) network cards
 together to act as one device?
 
 I've got a fileserver here with 2 nics in it, currently both have seperate
 ip's but I'd like the box to have just one ip but use both cards... is what
 I'm asking for possible at all?

It should work if you install the ifenslave package and enable bonding
support in the kernel, and you have a switch that supports etherchannel
or multi-link trunks (depending on the vendor).

I've been meaning to try this but haven't got around to it ...

-- 
Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED]
  Exhilaration is that feeling you get just after a great idea hits you,
  and just before you realize what's wrong with it.


pgp0.pgp
Description: PGP signature

Re: multiple network cards bound together

[Derrick 'dman' Hudson]

On Wed, Aug 13, 2003 at 09:16:42AM -0400, D. Clarke wrote:
| Hi!
| 
| Is it possible to bind multiple (non matching, or matching) network cards
| together to act as one device?
| 
| I've got a fileserver here with 2 nics in it, currently both have seperate
| ip's but I'd like the box to have just one ip but use both cards... is what
| I'm asking for possible at all?

Search for docs on channel bonding.  The extent of my knowledge on
it is this :
.   linux supports it
.   linux calls it channel bonding (other OSes call it other things)
.   both network interfaces must connect to the same host on the
other end
.   the host on the other end must be configured to work with the
channel bonding (may need to be a linux host, but I'm
really not certain on that)

HTH,
-D

-- 
The remote desktop feature of Windows XP is really nice (and *novel*!).
As a Microsoft consultant can *remotely* disable the personal firewall
and control the system.  We'll ignore the fact that this tampering with
the firewall is not logged, and more importantly, that the firewall
isn't restored when the clowns from Redmond are done with their job.
-- bugtraq
 
http://dman13.dyndns.org/~dman/


pgp0.pgp
Description: PGP signature

multiple network cards bound together

[D. Clarke]

Hi!

Is it possible to bind multiple (non matching, or matching) network cards
together to act as one device?

I've got a fileserver here with 2 nics in it, currently both have seperate
ip's but I'd like the box to have just one ip but use both cards... is what
I'm asking for possible at all?

Thanks

~ Darryl



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Two network cards of same type, which eth0, which eth1?

[Jeff]

Mark Janssen, 2003-Mar-07 14:17 +0100:
 On Fri, 2003-03-07 at 13:26, Hugo van der Merwe wrote:
  I am going to be installing two new network cards soon, most likely
  I'll be getting that cheap junk that is the rtl8139. How do I choose
  which one must be eth0? Module parameters to the 8139too module? (In
  the past I simply loaded the correct module first.
 
 THey are detected in PCI order... so the lowest numbered PCI slot first,
 and then in order. So this depends on your motherboard. In my case they
 are numbered from low to high in the case. Check your mobo
 documentation.

My motherboard assigns them by the highest PCI number first.  01:06.0
gets to be eth0, and 01:05.0 gets to be eth1.  This is with 2.4.20
kernel and a Tyan S2060 Tomcat i815 motherboard.

Check /var/log/dmesg to see how they are assigned.  I don't know if it
depends on the motherboard or the kernel, but I suspect it's the
kernel.

jc

-- 
Jeff CoppockSystems Engineer
Diggin' Debian  Admin and User


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]