subject:"network card"

David Christensen wrote: 
> On 2021-01-19 14:35, Dan Ritter wrote:
> > So I could drop down to a 2-port NIC, using 3 total and not
> > having any spares, but I already have this setup, and it's been
> > running nicely since 2014. I spent about $250 on it, including
> > some parts I had lying around, and with luck it will last until
> > something better than gigabit fiber comes to my neighborhood
> > with nothing worse than a power-supply replacement for $40 or
> > so. The best part is that it runs straight Debian, AMD64, so
> > unlike all the SOHO routers, it stays up to date.
> 
> 
> I have a SOHO network.  Our Wi-Fi devices need access to LAN hosts and
> vice-versa.  I set up WPA2 and MAC filtering on the Wi-Fi, and put the Wi-Fi
> devices on the LAN.
> 
> 
> Server-grade multi-port NIC's are expensive parts.  When I ran PC firewalls,
> I used desktop NIC's to supplement the motherboard port. Inexpensive Fast
> Ethernet (100 Mbps) cards and switches were, and still are, sufficient for
> the downstream side of my Internet connection.

Well, they were expensive when new. A used quad-gig-e PCIe card
is now $20-35 on Ebay, and I see someone with a supply of
Chelsio quad cards with 2 10g nics and 2 1g nics for $50 each.

The things that flow downstream can be recycled for the home
market...

-dsr-

Re: One network card many rj45 sockets

2021-01-19 Thread David Christensen


On 2021-01-19 14:35, Dan Ritter wrote:

David Christensen wrote:

On 2021-01-19 06:22, Dan Ritter wrote:


My firewall (yes, it runs Debian) has an Intel 4x 1gig ethernet
card in it, as well as the 1 gig port on the motherboard. Each
is completely independent, so I have:

- one connection to the public Internet
- one connection to my switched network of wifi access points
- one connection to my general wired network switch
- one connection to my remote power switch
- and a free connection for the future.

Each of these has one or more different IP addresses, including
IPv6 on three ports, and packets are routed between them and
blocked by the firewall.


On 2021-01-19 08:40, Dan Ritter wrote:

[The remote power switch] can turn on and off a set of wall outlets,
to which other computers are attached. In other words, if the firewall
is running, I can power-cycle several other machines.



I assume your Wi-Fi, LAN, and remote power switch interfaces are on
different network segments (?).


Do you have use-cases that require or benefit from this, or could you
replace the 4-port NIC with a 1-port NIC connected to a switch connected to
all of the inside devices (AP's, clients, servers, power gateway, etc.)?


The remote power switch doesn't have to be directly attached;
it could be attached to the switch that the general wired
network uses. However, it needs to be fully functional with just
the firewall being alive -- the idea is that if I can get into
my firewall, I can deal with a hung server.

The APs are deliberately separated from the wired network:
nothing on an AP is trusted more than the general Internet,
except that they get to see DHCP, DNS, NTP and a printer.

All the wired devices trust each other a bit more; there are
some NFS mounts that allow an entire subnet to read from them,
for example.

So I could drop down to a 2-port NIC, using 3 total and not
having any spares, but I already have this setup, and it's been
running nicely since 2014. I spent about $250 on it, including
some parts I had lying around, and with luck it will last until
something better than gigabit fiber comes to my neighborhood
with nothing worse than a power-supply replacement for $40 or
so. The best part is that it runs straight Debian, AMD64, so
unlike all the SOHO routers, it stays up to date.



I have a SOHO network.  Our Wi-Fi devices need access to LAN hosts and 
vice-versa.  I set up WPA2 and MAC filtering on the Wi-Fi, and put the 
Wi-Fi devices on the LAN.



Server-grade multi-port NIC's are expensive parts.  When I ran PC 
firewalls, I used desktop NIC's to supplement the motherboard port. 
Inexpensive Fast Ethernet (100 Mbps) cards and switches were, and still 
are, sufficient for the downstream side of my Internet connection.



David

Re: One network card many rj45 sockets

David Christensen wrote: 
> On 2021-01-19 06:22, Dan Ritter wrote:
> > 
> > My firewall (yes, it runs Debian) has an Intel 4x 1gig ethernet
> > card in it, as well as the 1 gig port on the motherboard. Each
> > is completely independent, so I have:
> > 
> > - one connection to the public Internet
> > - one connection to my switched network of wifi access points
> > - one connection to my general wired network switch
> > - one connection to my remote power switch
> > - and a free connection for the future.
> > 
> > Each of these has one or more different IP addresses, including
> > IPv6 on three ports, and packets are routed between them and
> > blocked by the firewall.
> 
> On 2021-01-19 08:40, Dan Ritter wrote:
> > [The remote power switch] can turn on and off a set of wall outlets,
> > to which other computers are attached. In other words, if the firewall
> > is running, I can power-cycle several other machines.
> 
> 
> I assume your Wi-Fi, LAN, and remote power switch interfaces are on
> different network segments (?).
> 
> 
> Do you have use-cases that require or benefit from this, or could you
> replace the 4-port NIC with a 1-port NIC connected to a switch connected to
> all of the inside devices (AP's, clients, servers, power gateway, etc.)?

The remote power switch doesn't have to be directly attached;
it could be attached to the switch that the general wired
network uses. However, it needs to be fully functional with just
the firewall being alive -- the idea is that if I can get into
my firewall, I can deal with a hung server.

The APs are deliberately separated from the wired network:
nothing on an AP is trusted more than the general Internet,
except that they get to see DHCP, DNS, NTP and a printer.

All the wired devices trust each other a bit more; there are
some NFS mounts that allow an entire subnet to read from them,
for example.

So I could drop down to a 2-port NIC, using 3 total and not
having any spares, but I already have this setup, and it's been
running nicely since 2014. I spent about $250 on it, including
some parts I had lying around, and with luck it will last until
something better than gigabit fiber comes to my neighborhood
with nothing worse than a power-supply replacement for $40 or
so. The best part is that it runs straight Debian, AMD64, so
unlike all the SOHO routers, it stays up to date.

-dsr-

Re: One network card many rj45 sockets

2021-01-19 Thread David Christensen

On 2021-01-19 06:22, Dan Ritter wrote:

mick crane wrote:

hello,
I see that you can get a single network card with 2, 3, 4 connections.
Can you happily make each one on a separate private address block ?
10.0.0.0, 172.16.0.0, 192.168.0.0

My firewall (yes, it runs Debian) has an Intel 4x 1gig ethernet
card in it, as well as the 1 gig port on the motherboard. Each
is completely independent, so I have:

- one connection to the public Internet
- one connection to my switched network of wifi access points
- one connection to my general wired network switch
- one connection to my remote power switch
- and a free connection for the future.

Each of these has one or more different IP addresses, including
IPv6 on three ports, and packets are routed between them and
blocked by the firewall.

On 2021-01-19 08:40, Dan Ritter wrote:
> [The remote power switch] can turn on and off a set of wall outlets,
> to which other computers are attached. In other words, if the firewall
> is running, I can power-cycle several other machines.

I assume your Wi-Fi, LAN, and remote power switch interfaces are on 
different network segments (?).

Do you have use-cases that require or benefit from this, or could you 
replace the 4-port NIC with a 1-port NIC connected to a switch connected 
to all of the inside devices (AP's, clients, servers, power gateway, etc.)?

David

Re: One network card many rj45 sockets

2021-01-19 Thread Sven Hartge

David Christensen  wrote:

> One feature of link aggregation is increased throughput -- two physical 
> connections can work together as one logical connection that is twice as 
> fast.

With the caveat that this does not increase the throughput of a single
flow. 

> But the killer feature is redundancy -- if every device is connected
> to two different switches, you can do maintenance on one switch and
> the network will remain up via the other switch.

Noteworthy here: If you want to do 802.3ad (aka LACP) the switches need
to be either stacked, use VSS/IRF or be compatible with MLAG/MC-LAG.

If you don't have such switches, you are limited to active-backup or
TLB/ALB-mode of the bonding code.

S°

-- 
Sigmentation fault. Core dumped.

Re: One network card many rj45 sockets

2021-01-19 Thread David Christensen


On 2021-01-19 04:47, mick crane wrote:

hello,
I see that you can get a single network card with 2, 3, 4 connections.
Can you happily make each one on a separate private address block ?
10.0.0.0, 172.16.0.0, 192.168.0.0


Yes, and more:

https://en.wikipedia.org/wiki/Link_aggregation


One feature of link aggregation is increased throughput -- two physical 
connections can work together as one logical connection that is twice as 
fast.



But the killer feature is redundancy -- if every device is connected to 
two different switches, you can do maintenance on one switch and the 
network will remain up via the other switch.



David

Re: One network card many rj45 sockets

mick crane wrote: 
> What is the purpose of remote power switch ?

It can turn on and off a set of wall outlets, to which other
computers are attached. In other words, if the firewall is
running, I can power-cycle several other machines.

-dsr-

Re: One network card many rj45 sockets

2021-01-19 Thread Stefan Monnier

> What is the purpose of remote power switch ?

Probably to turn on the popcorn machine when you're not at home.


Stefan

Re: One network card many rj45 sockets

2021-01-19 Thread mick crane


On 2021-01-19 15:06, Andy Smith wrote:

Hi Mick,

On Tue, Jan 19, 2021 at 12:47:34PM +, mick crane wrote:

I see that you can get a single network card with 2, 3, 4 connections.
Can you happily make each one on a separate private address block ?
10.0.0.0, 172.16.0.0, 192.168.0.0


There is no strong connection between the concept of a physical port
and the logical addresses you put on an interface associated with.
You can create a virtual network interface in a machine with no
network hardware at all, and put a billion different IPv6 networks
on it if you like!

Cheers,
Andy


But presumably at the end it would have to go to one addressable thing ?
Which would be the only point doing networking ?

mick
--
Key ID4BFEBB31

Re: One network card many rj45 sockets

2021-01-19 Thread Andy Smith

Hi Mick,

On Tue, Jan 19, 2021 at 12:47:34PM +, mick crane wrote:
> I see that you can get a single network card with 2, 3, 4 connections.
> Can you happily make each one on a separate private address block ?
> 10.0.0.0, 172.16.0.0, 192.168.0.0

There is no strong connection between the concept of a physical port
and the logical addresses you put on an interface associated with.
You can create a virtual network interface in a machine with no
network hardware at all, and put a billion different IPv6 networks
on it if you like!

Cheers,
Andy

Re: One network card many rj45 sockets

2021-01-19 Thread mick crane


On 2021-01-19 14:22, Dan Ritter wrote:

mick crane wrote:

hello,
I see that you can get a single network card with 2, 3, 4 connections.
Can you happily make each one on a separate private address block ?
10.0.0.0, 172.16.0.0, 192.168.0.0


My firewall (yes, it runs Debian) has an Intel 4x 1gig ethernet
card in it, as well as the 1 gig port on the motherboard. Each
is completely independent, so I have:

- one connection to the public Internet
- one connection to my switched network of wifi access points
- one connection to my general wired network switch
- one connection to my remote power switch
- and a free connection for the future.

Each of these has one or more different IP addresses, including
IPv6 on three ports, and packets are routed between them and
blocked by the firewall.

-dsr-


What is the purpose of remote power switch ?

mick

--
Key ID4BFEBB31

Re: One network card many rj45 sockets

2021-01-19 Thread Henning Follmann

On Tue, 2021-01-19 at 12:47 +, mick crane wrote:
> hello,
> I see that you can get a single network card with 2, 3, 4
> connections.
> Can you happily make each one on a separate private address block ?
> 10.0.0.0, 172.16.0.0, 192.168.0.0
> 
> mick
> 
Yes,
but depending on your network topology you might screw up things.
Make sure that each virtual nic links to a VLAN with the correct 
block.

-H

Re: One network card many rj45 sockets

mick crane wrote: 
> hello,
> I see that you can get a single network card with 2, 3, 4 connections.
> Can you happily make each one on a separate private address block ?
> 10.0.0.0, 172.16.0.0, 192.168.0.0

My firewall (yes, it runs Debian) has an Intel 4x 1gig ethernet
card in it, as well as the 1 gig port on the motherboard. Each
is completely independent, so I have:

- one connection to the public Internet 
- one connection to my switched network of wifi access points
- one connection to my general wired network switch
- one connection to my remote power switch
- and a free connection for the future.

Each of these has one or more different IP addresses, including
IPv6 on three ports, and packets are routed between them and 
blocked by the firewall.

-dsr-

Re: One network card many rj45 sockets

2021-01-19 Thread tomas

On Tue, Jan 19, 2021 at 12:47:34PM +, mick crane wrote:
> hello,
> I see that you can get a single network card with 2, 3, 4 connections.
> Can you happily make each one on a separate private address block ?
> 10.0.0.0, 172.16.0.0, 192.168.0.0

You can even put one connection (aka "port") on several networks.

Cheers
 - t


signature.asc
Description: Digital signature

Re: One network card many rj45 sockets

2021-01-19 Thread Reco

Hi.

On Tue, Jan 19, 2021 at 12:47:34PM +, mick crane wrote:
> I see that you can get a single network card with 2, 3, 4 connections.

They call them "ports" usually. Such things exist for a long time in a
server world, but are infrequent in consumer one.

> Can you happily make each one on a separate private address block ?
> 10.0.0.0, 172.16.0.0, 192.168.0.0

Yes, it's definitely possible - from IP stack point of view each port is
a different network interface.

It'll unlikely be efficient (compared to a managed switch, that is) if
your plan is to use such card as a router - after all you'll need to
copy all the packets to the kernel and back, and that takes time.
But it still going to beat more common DIY combo of two/three USB-Ethernets.

Reco

Re: One network card many rj45 sockets

2021-01-19 Thread Georgi Naplatanov

On 1/19/21 2:47 PM, mick crane wrote:
> hello,
> I see that you can get a single network card with 2, 3, 4 connections.
> Can you happily make each one on a separate private address block ?
> 10.0.0.0, 172.16.0.0, 192.168.0.0
> 

I don't know what the purpose is one network card to have multiple
connectors but yes it's possible one network card to have multiple IP
addresses - IPv4 and/or IPv6.

Kind regards
Georgi

One network card many rj45 sockets

2021-01-19 Thread mick crane


hello,
I see that you can get a single network card with 2, 3, 4 connections.
Can you happily make each one on a separate private address block ?
10.0.0.0, 172.16.0.0, 192.168.0.0

mick

--
Key ID4BFEBB31

Re: trouble with my network card

2019-05-21 Thread Greg Wooledge

On Tue, May 21, 2019 at 07:05:49AM -0400, BELAHCENE Abdelkader wrote:
> I have a trouble with my network card (extern card)
> lspci gives:
> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
> mii-tool  enp4s0
> SIOCGMIIPHY on 'enp4s0' failed: No such device

I would suggest you try installing the firmware-realtek package (it's
non-free) if you haven't already done so.  Then reboot.

https://packages.debian.org/stretch/firmware-realtek

Re: trouble with my network card

2019-05-21 Thread Pascal Hambourg


Le 21/05/2019 à 13:05, BELAHCENE Abdelkader a écrit :

Hi,
I have a trouble with my network card (extern card)


What do you mean by "extern card" ? It looks like an internal PCIe card.


lspci gives:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
mii-tool  enp4s0
SIOCGMIIPHY on 'enp4s0' failed: No such device


You may have better luck with ethtool instead of mii-tool.


ifconfig  enp4s0
enp4s0: flags=4098  mtu 1500


The interface is not UP.

trouble with my network card

2019-05-21 Thread BELAHCENE Abdelkader

Hi,
I have a trouble with my network card (extern card)
lspci gives:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
mii-tool  enp4s0
SIOCGMIIPHY on 'enp4s0' failed: No such device

ifconfig  enp4s0
enp4s0: flags=4098  mtu 1500
inet 192.168.10.20  netmask 255.255.255.0  broadcast 192.168.10.255
ether 00:e0:4c:68:0d:d7  txqueuelen 1000  (Ethernet)
RX packets 32  bytes 1920 (1.8 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
I can ping it in the local machine
but not from another machine,  the lightspot of the card is off !!!

What is happening ??  mii-tool doesn't find it but I can put an address??

thanks for help
regards

Re: RTL8812/8821 network card driver

2017-05-29 Thread Michael Milliman



On 05/29/2017 07:12 AM, to...@tuxteam.de wrote:
> On Mon, May 29, 2017 at 04:29:35AM -0700, 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
> 
> A couple of things:
> 
>  - this list is not "Debian". It's just the Debian User's mailing
>list. Debian users help each other (sometimes experts lurk here
>and help us all, which is very nice of them, but nobody is paid
>or forced to do that!)
> 
>  - if you want to get a hardware driver "in", the best path is,
>of course the kernel. This way, it'll find its way into all
>Linux distributions, not only Debian. That said, sometimes
>distributions carry a set of patches to the "official" or
>"vanilla" kernel, but most try to keep those patches to a
>minimum: it's a lot of work to maintain that, and this takes
>energy away to do other important things.
> 
>  - the mailing list for this kind of questions is most probably
>the Debian kernel mailing list:
> 
>https://lists.debian.org/debian-kernel/
> 
>There are really nice people there, but please be nice to
>them. They are doing an awesome work without us paying them
>to do so. Do your homework first:
>(a) do newer versions of the Linux kernel carry this driver
>   already?
>(b) search the mailing list archives. Perhaps there's already
>   a discussion about this on-going.
> 
It is also possible that another driver than the one OP mentions is
being considered for inclusion in the kernel to handle the hardware in
question.  Linux, being what it is, there are often more than one
solution to the same problem, and one of the things the developers, both
debian and upstream, consider is what is the best fit for Debian/Linux
overall.

> Cheers
> -- tomás
> 

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



signature.asc
Description: OpenPGP digital signature

Re: RTL8812/8821 network card driver

2017-05-29 Thread tomas

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, May 29, 2017 at 04:29:35AM -0700, 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

A couple of things:

 - this list is not "Debian". It's just the Debian User's mailing
   list. Debian users help each other (sometimes experts lurk here
   and help us all, which is very nice of them, but nobody is paid
   or forced to do that!)

 - if you want to get a hardware driver "in", the best path is,
   of course the kernel. This way, it'll find its way into all
   Linux distributions, not only Debian. That said, sometimes
   distributions carry a set of patches to the "official" or
   "vanilla" kernel, but most try to keep those patches to a
   minimum: it's a lot of work to maintain that, and this takes
   energy away to do other important things.

 - the mailing list for this kind of questions is most probably
   the Debian kernel mailing list:

   https://lists.debian.org/debian-kernel/

   There are really nice people there, but please be nice to
   them. They are doing an awesome work without us paying them
   to do so. Do your homework first:
   (a) do newer versions of the Linux kernel carry this driver
  already?
   (b) search the mailing list archives. Perhaps there's already
  a discussion about this on-going.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlksECcACgkQBcgs9XrR2kavYgCdHYhLO9P5CQTEEdkVbFA0PUtS
G+QAmgJR2kQdiZizdtEezaXKq6UDzsok
=c8sk
-END PGP SIGNATURE-

RTL8812/8821 network card driver

2017-05-29 Thread 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

Re: Intel I281-LM network card not working with Debian Stable

2017-04-21 Thread Ben Caradoc-Davies


On 21/04/17 22:27, Siebrand Klein wrote:

Dear Debian-users list,
I have a computer with one Intel I218-LM and two Intel I210 network
adapters.
The I210's are found correctly, but the I218 isn't.
Can anyone give me some advice on how to get the I218 up and running? I
found some (old) information that a newer version of the e1000e kernel
module might help, but I would like to stick to the standard distribution
files. If it is necessary to update, preferably to some testing packages
then...


A 4.9.18 kernel from jessie backports would likely be more compatible 
with stable than a kernel from testing. Note that stretch is almost 
released (it will soon be the new stable) and contains the same kernel. 
If you are not ready to upgrade, then jessie backports is in my view 
your best option for an upgraded kernel:

https://backports.debian.org/Instructions/

There are no guarantees that 4.9.18 will fix your issue. I218-LM should 
be supported in 3.16; support might be improved in 4.9.18:

http://cateee.net/lkddb/web-lkddb/E1000E.html

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Intel I281-LM network card not working with Debian Stable

2017-04-21 Thread Siebrand Klein

Dear Debian-users list,

I have a computer with one Intel I218-LM and two Intel I210 network 
adapters.
The I210's are found correctly, but the I218 isn't.

Can anyone give me some advice on how to get the I218 up and running? I 
found some (old) information that a newer version of the e1000e kernel 
module might help, but I would like to stick to the standard distribution 
files. If it is necessary to update, preferably to some testing packages 
then...

I'm using a fairly standard Debian Stable (jessie) installation. Please 
see the output of some commands below.


root@debian:~# uname -a
Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) 
x86_64 GNU/Linux


root@debian:~# lspci  | egrep -i --color 'network|ethernet'
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)


root@debian:~# ls /sys/class/net/
eth0  eth1  lo

 
root@debian:~# lspci -v | grep -i Ethernet -A 15
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
Subsystem: Intel Corporation Device 
Flags: fast devsel, IRQ 20
Memory at f7e0 (32-bit, non-prefetchable) [size=128K]
Memory at f7e38000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f060 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features

00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB EHCI #2 (rev 04) (prog-if 20 [EHCI])
Subsystem: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f7e37000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
--
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
Subsystem: Omron Corporation Device 003a
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f7d0 (32-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=32]
Memory at f7d2 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-00-0a-ff-ff-f8-fe-c5
Capabilities: [1a0] Transaction Processing Hints
Kernel driver in use: igb

05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
Subsystem: Omron Corporation Device 0039
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f7c0 (32-bit, non-prefetchable) [size=128K]
I/O ports at d000 [size=32]
Memory at f7c2 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-00-0a-ff-ff-f8-fe-c6
Capabilities: [1a0] Transaction Processing Hints
Kernel driver in use: igb


Thanks,
Siebrand

Re: Problem with TP-Link network card

2016-02-29 Thread Luis Eduardo Cortés

>
> Well, after some time, I have returned to this matter.
>
> I have done one more test that I think is is conclusive. As I said, this
> Debian GNU/Linux firewall PC has two network cards:
>
> * eth0: RealTek RTL8139 (to the ADSL router)
> * eth1: VIA Rhine II (to the local network)
>
> The problem was with the RTL8139 card connected to the router. This only
> worked when setting up it to 10 Mbps. The VIA card connected to the
> switch of the local network never gave problems.
>
> So I now exchanged the configuration of the cards. Now the eth0 Realtek
> card connects to the internal network. It runs smoothly at 100 Mbps,
> full duplex and auto negotiation. So I think it was not a problem with
> the Realtek card. In fact, now the VIA card (that previously worked
> properly connected to the internal network switch) only works against
> ADSL router when it is set to 10 Mbps.
>
> All this makes me think the problem is in the ethernet interface of the
> ADSL router.
>
> I have requested a new router to Telefonica. I hope they send me a good
> one. This Zyxel router worked smoothly for quite some time. I also hope
> it have a default password to access the router and make the necessary
> settings (such as SNMP monitoring).
>
>
> Thanks for your reply.
>
> Kind regards,
> Daniel
>


Try installing "firmware-realtek" package to solve the original problem.

Regards.

Re: Problem with TP-Link network card

2016-02-28 Thread Daniel Bareiro

Hi, Dan.

On 17/01/16 18:33, Dan Ritter wrote:

>> That is, it seems that the communication notebook <---> router works
>> well regardless of the type of negotiation on the notebook side.
>>
>> But when I reconnect the firewall to the router, I lose again the link,
>> regardless of whether on the firewall is enabled or not the
>> auto-negotiation.

> I'm afraid at this point my suggestions all involve hardware:
> 
> - replace the TP-Link nic with something else, preferably with a
>   different chipset. Intel has been very reliable.
> 
> - put a small ethernet switch (4 and 5 port switches are reasonably
>   cheap) between the router and firewall.
> 
> - replace the router with something else.

Well, after some time, I have returned to this matter.

I have done one more test that I think is is conclusive. As I said, this
Debian GNU/Linux firewall PC has two network cards:

* eth0: RealTek RTL8139 (to the ADSL router)
* eth1: VIA Rhine II (to the local network)

The problem was with the RTL8139 card connected to the router. This only
worked when setting up it to 10 Mbps. The VIA card connected to the
switch of the local network never gave problems.

So I now exchanged the configuration of the cards. Now the eth0 Realtek
card connects to the internal network. It runs smoothly at 100 Mbps,
full duplex and auto negotiation. So I think it was not a problem with
the Realtek card. In fact, now the VIA card (that previously worked
properly connected to the internal network switch) only works against
ADSL router when it is set to 10 Mbps.

All this makes me think the problem is in the ethernet interface of the
ADSL router.

I have requested a new router to Telefonica. I hope they send me a good
one. This Zyxel router worked smoothly for quite some time. I also hope
it have a default password to access the router and make the necessary
settings (such as SNMP monitoring).

Thanks for your reply.

Kind regards,
Daniel

signature.asc
Description: OpenPGP digital signature

Re: Problem with TP-Link network card

2016-01-17 Thread Dan Ritter

On Sun, Jan 17, 2016 at 05:07:20PM -0300, Daniel Bareiro wrote:
> Hi, Dan.
> 
> Thanks for your reply.

...

> That is, it seems that the communication notebook <---> router works
> well regardless of the type of negotiation on the notebook side.
> 
> But when I reconnect the firewall to the router, I lose again the link,
> regardless of whether on the firewall is enabled or not the
> auto-negotiation.

I'm afraid at this point my suggestions all involve hardware:

- replace the TP-Link nic with something else, preferably with a
  different chipset. Intel has been very reliable.

- put a small ethernet switch (4 and 5 port switches are reasonably
  cheap) between the router and firewall.

- replace the router with something else.

-dsr-

Re: Problem with TP-Link network card

2016-01-17 Thread Daniel Bareiro

Hi, Dan.

Thanks for your reply.

On 17/01/16 09:56, Dan Ritter wrote:

>> In fact, I tested it with a new TP-Link card with the same Realtek
>> chipset and I have observed the same behavior.
>>
>> Any idea what could be the problem?

> Disable autonegotiation on both sides; set it to full duplex
> 100.
> 
> If the behavior persists, replace the cable.

I was reviewing on the CLI as through the web access if the router
(Zyxel P-660R-T1v3) allows to disable the negotiation of the LAN
interface, but I found nothing. So I tried the other suggestion, that it
was changing the cable, but no change in behavior.

I did some other tests with my notebook:

a) notebook (orion) <---> firewall (alderamin)
b) notebook (orion) <---> router

Case a: notebook (orion) <---> firewall (alderamin)


root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg on
root@orion:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown (auto)
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: no

root@orion:~# ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 3c:97:0e:57:4a:89
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:8050 errors:162 dropped:0 overruns:0 frame:105
  TX packets:5137 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:4112009 (3.9 MiB)  TX bytes:674943 (659.1 KiB)
  Interrupt:20 Memory:f250-f252

root@orion:~# ip addr add 192.168.1.1 dev eth0
root@orion:~# ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 3c:97:0e:57:4a:89
  inet addr:192.168.1.1  Bcast:0.0.0.0  Mask:255.255.255.255
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:8050 errors:162 dropped:0 overruns:0 frame:105
  TX packets:5137 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:4112009 (3.9 MiB)  TX bytes:674943 (659.1 KiB)
  Interrupt:20 Memory:f250-f252


root@alderamin:~# ifconfig eth1
eth1  Link encap:Ethernet  HWaddr c4:e9:84:01:0e:4d
  inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
  inet6 addr: fe80::c6e9:84ff:fe01:e4d/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:359625 errors:151 dropped:0 overruns:48 frame:0
  TX packets:326791 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:297907826 (284.1 MiB)  TX bytes:45096052 (43.0 MiB)


root@alderamin:~# ethtool -s eth1 speed 100 duplex full autoneg on
root@alderamin:~# ethtool eth1

Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: no

root@alderamin:~# ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4010ms


It seems that here the connection notebook <---> firewall has not worked
with auto-negotiation on both sides. Now I try to disable the
negotiation on both ends:

root@orion:~# ethtool -s eth0 speed 100 duplex full autoneg off
root@orion:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation

Re: Problem with TP-Link network card

2016-01-17 Thread Dan Ritter

On Sat, Jan 16, 2016 at 04:24:15PM -0300, Daniel Bareiro wrote:
> 
> In fact, I tested it with a new TP-Link card with the same Realtek
> chipset and I have observed the same behavior.
> 
> Any idea what could be the problem?

Disable autonegotiation on both sides; set it to full duplex
100.

If the behavior persists, replace the cable.

-dsr-

Re: Problem with TP-Link network card

2016-01-16 Thread Daniel Bareiro

Hi, John.

Thanks for your reply.

On 16/01/16 17:13, John Hasler wrote:

>> Any idea what could be the problem?

> Hardware.

Do you mean to some problem with the motherboard?


Best regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: Problem with TP-Link network card

2016-01-16 Thread John Hasler

Daniel Bareiro writes: 
> Any idea what could be the problem?

Hardware.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Problem with TP-Link network card

2016-01-16 Thread Daniel Bareiro

Hi all!

Yesterday I had a power outage in my workplace and when the power was
restored, I noticed I did not have Internet access.

In reviewing the DSL router, I saw the "Ethernet" LED representing the
connection to the computer behind it, a PC firewall with Debian Jessie,
was turned off.

Apparently, the interface on Jessie side had no link. The network
interface is given by a PCI card with Realtek chipset RTL8139D that I'm
using since June 2008 without problems on this computer. It went through
several Debian versions and it was running smoothly with Jessie before
this incident. In fact, in the last update of the kernel that I have
applied (the one published by Salvatore Bonaccorso on December 17), I
restarted the operating system without downside.

I was looking at the syslog and it seems that the link comes and goes:


(...)
Jan 15 21:47:24 alderamin kernel: [  249.092973] 8139too :00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:47:24 alderamin kernel: [  249.114731] 8139too :00:09.0
eth1: link down
Jan 15 21:48:10 alderamin kernel: [  295.226378] 8139too :00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:10 alderamin kernel: [  295.245295] 8139too :00:09.0
eth1: link down
Jan 15 21:48:14 alderamin kernel: [  299.105773] 8139too :00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:14 alderamin kernel: [  299.117529] 8139too :00:09.0
eth1: link down
Jan 15 21:48:23 alderamin kernel: [  307.755787] 8139too :00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:23 alderamin kernel: [  307.759521] 8139too :00:09.0
eth1: link down
Jan 15 21:48:29 alderamin kernel: [  314.046708] 8139too :00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:48:29 alderamin kernel: [  314.055246] 8139too :00:09.0
eth1: link down
Jan 15 21:49:01 alderamin kernel: [  346.182821] 8139too :00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:49:01 alderamin kernel: [  346.184420] 8139too :00:09.0
eth1: link down
Jan 15 21:49:36 alderamin kernel: [  380.625602] 8139too :00:09.0
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Jan 15 21:49:36 alderamin kernel: [  380.628902] 8139too :00:09.0
eth1: link down
(...)


To rule out a problem in the DSL router or the network cable, I
unplugged the end connected to the Jessie firewall and plugged it into
my notebook (which also uses Debian Jessie). In this case it is an Intel
network interface:


$ lspci | grep -i ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)


Here everything runs smoothly. So this leads me to think it's something
on the side of the Jessie firewall.

The strange part is that if I set the card into 10Mbps, the link becomes up:

# mii-tool eth0 -F 10baseT-FD
# rmmod 8139too
# modprobe 8139too


# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

# ethtool -s eth1 speed 100

# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: no

# ethtool -s eth1 speed 10

# ethtool eth1

Re: network card bridging failing on wheezy

2014-11-10 Thread Gary Dale


On 10/11/14 12:50 AM, Christian Seiler wrote:

Am 10.11.2014 01:33, schrieb Gary Dale:

On 09/11/14 03:30 PM, Christian Seiler wrote:

Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following settings (which are default):

CONFIGURE_INTERFACES=yes
EXCLUDE_INTERFACES=  # (empty)

Just has comments. No active settings.


You're under Wheezy, so I'm assuming sysvinit + LSB, could you also
check whether the networking script is started at boot?

ls -l /etc/rc*.d/S??networking

(should turn up a single link in /etc/rcS.d)

Yes.


If both is the way it should be, could you perhaps set VERBOSE=yes in
/etc/default/networking and look for any relevant boot messages? Not
dmesg/syslog, but on the console.[1]

Also, might be relevant: did you install any software that might take
over network configuration? Such as NetworkManager or wicd or the such?

No.

When I look at the console messages, the networking doesn't show up even
with the zz-wait script inserted. Similarly, running
/etc/init.d/networking start doesn't work.

This is really strange... What does "doesn't work" mean in this context?
No output? A message that it's doing what it wants to do, but it doesn't
actually do it? Some error message?

I just looked at the /etc/init.d/networking source, and I don't see
anything in there that would make it not work other than
 if init_is_upstart; then
 exit 1
 fi
Are you by chance using upstart as init? (Although, while I haven't
tried that with wheezy, ifupdown does install an alternative mechanism
with upstart, so that shouldn't matter...)

If not, what does the following command tell you?

   ifup -a -v
Aha! ifup didn't run, so I reinstalled ifupdown. This removed iproute2 
and replaced it with iproute along with reinstalling ifupdown.  Now my 
network is coming up properly. I suspect this is a problem caused by the 
wheezy-backports Samba package not getting along with the regular Wheezy 
packages. Fortunately it gets along well enough to give me a working 
Samba environment even with the older packages.


Thanks Christian!


--
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/5460e8d7.6000...@torfree.net

Re: network card bridging failing on wheezy

Am 10.11.2014 01:33, schrieb Gary Dale:
> On 09/11/14 03:30 PM, Christian Seiler wrote:
>> Could you post the contents of your /etc/default/networking?
>> Specifically, it should have either no explicit settings (everything
>> commented out) or the following settings (which are default):
>>
>> CONFIGURE_INTERFACES=yes
>> EXCLUDE_INTERFACES=  # (empty)
> Just has comments. No active settings.
> 
>> You're under Wheezy, so I'm assuming sysvinit + LSB, could you also
>> check whether the networking script is started at boot?
>>
>> ls -l /etc/rc*.d/S??networking
>>
>> (should turn up a single link in /etc/rcS.d)
> Yes.
> 
>> If both is the way it should be, could you perhaps set VERBOSE=yes in
>> /etc/default/networking and look for any relevant boot messages? Not
>> dmesg/syslog, but on the console.[1]
>>
>> Also, might be relevant: did you install any software that might take
>> over network configuration? Such as NetworkManager or wicd or the such?
> No.
> 
> When I look at the console messages, the networking doesn't show up even 
> with the zz-wait script inserted. Similarly, running 
> /etc/init.d/networking start doesn't work.

This is really strange... What does "doesn't work" mean in this context?
No output? A message that it's doing what it wants to do, but it doesn't
actually do it? Some error message?

I just looked at the /etc/init.d/networking source, and I don't see
anything in there that would make it not work other than
if init_is_upstart; then
exit 1
fi
Are you by chance using upstart as init? (Although, while I haven't
tried that with wheezy, ifupdown does install an alternative mechanism
with upstart, so that shouldn't matter...)

If not, what does the following command tell you?

  ifup -a -v

After boot (before you try anything with ifconfig, ip, ifup, ...), does
/run/network/ifstate exist and if so, what's its contents? (Should be
two lines: lo=lo and br0=br0.)

Oh btw. is /etc/init.d/networking still the correct version?

dpkg -l ifupdown (current wheezy should give you 0.7.8)
debsums -a ifupdown (should give lots of OKs)

> But yes, udevd does start. I do get the eth0 link up messages, but they 
> seem to be from me logging in and bringing it up manually. After the 
> last reboot, I get the messages 67 seconds after the previous dmesg line.
> 
> [   31.724230] usb 3-3: new full-speed USB device number 9 using ohci_hcd
> [   32.132170] usb 3-3: device not accepting address 9, error -62
> [   32.132232] hub 3-0:1.0: unable to enumerate USB device on port 3
> [   99.533084] r8169 :02:00.0: eth0: link down
> [   99.533104] r8169 :02:00.0: eth0: link down
> [   99.536334] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [  101.996167] r8169 :02:00.0: eth0: link up
> [  101.999283] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Regardless of the wait time, this is weird: apparently something is
telling eth0 to go up at boot... Or was that you yourself after you
logged in to the system?

- Christian

-- 
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/54605209.9090...@iwakd.de

Re: network card bridging failing on wheezy


On 09/11/14 03:30 PM, Christian Seiler wrote:

Am 09.11.2014 21:13, schrieb Gary Dale:

You're right. Here's my default.xml (I only changed the addresses):

root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml

default



  

  



However when I removed the link to default.xml, I ended up with no
network starting. Nor could I bring up br0. lo and eth0 could still be
brought up manually and a gateway added.

Then it appears to be the case that Debian's networking scripts are not
started at boot. (Then it's also no wonder why you can't bring up br0,
because it doesn't exist yet, you'd have to create it with 'brctl addbr
br0' first, if you really wanted to use 'br0'.)

Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following settings (which are default):

CONFIGURE_INTERFACES=yes
EXCLUDE_INTERFACES=  # (empty)

Just has comments. No active settings.


You're under Wheezy, so I'm assuming sysvinit + LSB, could you also
check whether the networking script is started at boot?

ls -l /etc/rc*.d/S??networking

(should turn up a single link in /etc/rcS.d)

Yes.



If both is the way it should be, could you perhaps set VERBOSE=yes in
/etc/default/networking and look for any relevant boot messages? Not
dmesg/syslog, but on the console.[1]

Also, might be relevant: did you install any software that might take
over network configuration? Such as NetworkManager or wicd or the such?

No.

When I look at the console messages, the networking doesn't show up even 
with the zz-wait script inserted. Similarly, running 
/etc/init.d/networking start doesn't work.





But what is the underlying problem? It looks like the networking isn't
being brought up during boot, but I'm seeing dmesg output like:

[  199.542096] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[  199.542153] r8169 :02:00.0: setting latency timer to 64
[  199.542198] r8169 :02:00.0: irq 41 for MSI/MSI-X
[  199.542594] r8169 :02:00.0: eth0: RTL8168c/8111c at
0xc9c0e000, 00:24:1d:14:d8:42, XID 1c4000c0 IRQ 41
[  199.542596] r8169 :02:00.0: eth0: jumbo features [frames: 6128
bytes, tx checksumming: ko]

That just seems to load the corresponding driver, probably once udev is
loaded at boot,[*] but doesn't appear to actually bring it up (no 'link
is up' or similar message).

[*] Although 200s seems a bit late for that, udev should load
immediately after the root filesystem is mounted, could you check when
that happened? If it's just a couple of seconds before the 199.54s,
that's fine (then the kernel just takes a long time to initialize, maybe
because of RAID/SCSI/SAS/... controller?) but if there's quite a gap
between the mounting of the root filesystem and the loading of the
network driver (with no additional drivers that take a long time probing
in between), that would also be strange, and a potential source of problem.
That seems to be another problem. I'm getting a lot of USB messages (I 
have some USB printers plugged in). Not as urgent a problem since I have 
a network printer as well, so I don't need to get at the attached 
printers. And yes, I am running a RAID 1 array (mdadm).


However, the big problem is one that I have with some systems, where the 
boot process becomes stuck until a keypress. I suspect an issue with my 
kvm switch.


But yes, udevd does start. I do get the eth0 link up messages, but they 
seem to be from me logging in and bringing it up manually. After the 
last reboot, I get the messages 67 seconds after the previous dmesg line.


[   31.724230] usb 3-3: new full-speed USB device number 9 using ohci_hcd
[   32.132170] usb 3-3: device not accepting address 9, error -62
[   32.132232] hub 3-0:1.0: unable to enumerate USB device on port 3
[   99.533084] r8169 :02:00.0: eth0: link down
[   99.533104] r8169 :02:00.0: eth0: link down
[   99.536334] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  101.996167] r8169 :02:00.0: eth0: link up
[  101.999283] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready





and
[  226.160653] tun: Universal TUN/TAP device driver, 1.6
[  226.160660] tun: (C) 1999-2004 Max Krasnyansky 

That indicates that the tun driver is loaded, probably once libvirt is
started. That has no bearing on your host's network configuration.

- Christian

[1] If boot goes to fast for you, you could add the following script to
/etc/network/if-up.d/zz-wait (make it executable):

#!/bin/sh
[ x"$IFACE" = x"lo" ] && return
echo
echo $IFACE should be configured now...
echo  (sleeping for a while)
echo
sleep 20

(Replace the 20 with however many seconds you might need to see the
messages.)




--
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/546007d0.9010...@torfree.net

Re: network card bridging failing on wheezy

Am 09.11.2014 21:13, schrieb Gary Dale:
> You're right. Here's my default.xml (I only changed the addresses):
> 
> root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml
> 
>default
>
>
>
>  
>
>  
>
> 
> 
> However when I removed the link to default.xml, I ended up with no 
> network starting. Nor could I bring up br0. lo and eth0 could still be 
> brought up manually and a gateway added.

Then it appears to be the case that Debian's networking scripts are not
started at boot. (Then it's also no wonder why you can't bring up br0,
because it doesn't exist yet, you'd have to create it with 'brctl addbr
br0' first, if you really wanted to use 'br0'.)

Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following settings (which are default):

CONFIGURE_INTERFACES=yes
EXCLUDE_INTERFACES=  # (empty)

You're under Wheezy, so I'm assuming sysvinit + LSB, could you also
check whether the networking script is started at boot?

ls -l /etc/rc*.d/S??networking

(should turn up a single link in /etc/rcS.d)

If both is the way it should be, could you perhaps set VERBOSE=yes in
/etc/default/networking and look for any relevant boot messages? Not
dmesg/syslog, but on the console.[1]

Also, might be relevant: did you install any software that might take
over network configuration? Such as NetworkManager or wicd or the such?

> But what is the underlying problem? It looks like the networking isn't 
> being brought up during boot, but I'm seeing dmesg output like:
> 
> [  199.542096] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [  199.542153] r8169 :02:00.0: setting latency timer to 64
> [  199.542198] r8169 :02:00.0: irq 41 for MSI/MSI-X
> [  199.542594] r8169 :02:00.0: eth0: RTL8168c/8111c at 
> 0xc9c0e000, 00:24:1d:14:d8:42, XID 1c4000c0 IRQ 41
> [  199.542596] r8169 :02:00.0: eth0: jumbo features [frames: 6128 
> bytes, tx checksumming: ko]

That just seems to load the corresponding driver, probably once udev is
loaded at boot,[*] but doesn't appear to actually bring it up (no 'link
is up' or similar message).

[*] Although 200s seems a bit late for that, udev should load
immediately after the root filesystem is mounted, could you check when
that happened? If it's just a couple of seconds before the 199.54s,
that's fine (then the kernel just takes a long time to initialize, maybe
because of RAID/SCSI/SAS/... controller?) but if there's quite a gap
between the mounting of the root filesystem and the loading of the
network driver (with no additional drivers that take a long time probing
in between), that would also be strange, and a potential source of problem.

> and
> [  226.160653] tun: Universal TUN/TAP device driver, 1.6
> [  226.160660] tun: (C) 1999-2004 Max Krasnyansky 

That indicates that the tun driver is loaded, probably once libvirt is
started. That has no bearing on your host's network configuration.

- Christian

[1] If boot goes to fast for you, you could add the following script to
/etc/network/if-up.d/zz-wait (make it executable):

#!/bin/sh
[ x"$IFACE" = x"lo" ] && return
echo
echo $IFACE should be configured now...
echo  (sleeping for a while)
echo
sleep 20

(Replace the 20 with however many seconds you might need to see the
messages.)


-- 
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/545fced4.4060...@iwakd.de

Re: network card bridging failing on wheezy


On 09/11/14 02:34 PM, Christian Seiler wrote:

Am 09.11.2014 19:48, schrieb Gary Dale:

This IP seems oddly familiar... Did you recently install libvirt?
Because that's the default IP for libvirt's default internal bridged
network (virbr0). Normally, that shouldn't interfere with the standard
bridge (different interface name), but maybe in your case, perhaps
because you edited your configuration?

(XML configuration under /etc/libvirt/qemu/networks/, especially look
for symlinks in /etc/libvirt/qemu/networks/autostart/. Note that if you
manually edit your libvirt configuration without virt-manager or virsh,
you first have to stop it, edit the configuration and then start it
again, else it will not work and be overwritten.)

I've had libvirt install for quite a while, I believe. I've been using
kvm and virt-manager for years. There is a symlink (default.xml) that
points to default.xml in the parent directory (using the full path
name). That file does use the 192.168.122. address range.

It appears to me as though libvirt is trying to manage br0 (i.e.
resetting it and adding the vnet0 interface to it), instead of the
default virbr0, and thus overriding the network setup of yours.

What's the contents of default.xml? Is that in any way modified?

Specifically, is the following entry there?

   

(That is what is there by default.)

I suspect that there will be an entry like

   

instead, which might cause your problems.

See:
http://wiki.libvirt.org/page/VirtualNetworking
http://wiki.libvirt.org/page/Networking

In the latter page, you can see that for 'shared physical device', the
bridge setup is not done by libvirt itself (i.e. no network setup is
done in libvirt!), but rather by the distribution, and libvirt will
automatically detect that setup and provide the required options in the
host configuration for this.

So, for example, I have completely disabled the default.xml network
configuration in libvirt (no link in autostart/), and bridging still
works because libvirt detects the bridge set up by Debian's network
configuration; in the NIC settings of a virtual machine in virt-manager
I can just say 'Source device: Specify shared device name' and put in
'Bridge name: br0', and then that just works. The 'default' internal
network (corresponding to virbr0) is marked as inactive.

You're right. Here's my default.xml (I only changed the addresses):

root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml

  default
  
  
  

  

  


However when I removed the link to default.xml, I ended up with no 
network starting. Nor could I bring up br0. lo and eth0 could still be 
brought up manually and a gateway added.






brctl show returns

bridge name bridge id   STP enabled interfaces
br0 8000.fe54004068c8   yes vnet0

Yes, here we can see that only vnet0 is part of the br0 bridge, and
vnet0 is the tun/tap/whatever device that libvirt uses for a running guest.
It only shows up when I try to run a guest, but still not networking on 
the virtual machine.





Subsequent to this, I changed the default.xml package to use my local
subnet addresses. When I rebooted, the br0 IP was correct but nothing
else was up. Even after bringing up lo and eth0 and adding a default
gateway, my machine was still not reachable on the network.

Yes, of course, because eth0 is not part of your br0 device at that
point. If in that configuration you want the bridge to include eth0, you
could in principle do 'brctl addif br0 eth0' to add eth0 to the bridge,
but you don't want to do that at this stage, because libvirt still
thinks it's responsible for that device and bad things[tm] can happen if
you try to override that without fixing the underlying problem.

But what is the underlying problem? It looks like the networking isn't 
being brought up during boot, but I'm seeing dmesg output like:


[  199.542096] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[  199.542153] r8169 :02:00.0: setting latency timer to 64
[  199.542198] r8169 :02:00.0: irq 41 for MSI/MSI-X
[  199.542594] r8169 :02:00.0: eth0: RTL8168c/8111c at 
0xc9c0e000, 00:24:1d:14:d8:42, XID 1c4000c0 IRQ 41
[  199.542596] r8169 :02:00.0: eth0: jumbo features [frames: 6128 
bytes, tx checksumming: ko]


and
[  226.160653] tun: Universal TUN/TAP device driver, 1.6
[  226.160660] tun: (C) 1999-2004 Max Krasnyansky 


--
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/545fcad1.4060...@torfree.net

Re: network card bridging failing on wheezy

Am 09.11.2014 19:48, schrieb Gary Dale:
>> This IP seems oddly familiar... Did you recently install libvirt?
>> Because that's the default IP for libvirt's default internal bridged
>> network (virbr0). Normally, that shouldn't interfere with the standard
>> bridge (different interface name), but maybe in your case, perhaps
>> because you edited your configuration?
>>
>> (XML configuration under /etc/libvirt/qemu/networks/, especially look
>> for symlinks in /etc/libvirt/qemu/networks/autostart/. Note that if you
>> manually edit your libvirt configuration without virt-manager or virsh,
>> you first have to stop it, edit the configuration and then start it
>> again, else it will not work and be overwritten.)
> I've had libvirt install for quite a while, I believe. I've been using 
> kvm and virt-manager for years. There is a symlink (default.xml) that 
> points to default.xml in the parent directory (using the full path 
> name). That file does use the 192.168.122. address range.

It appears to me as though libvirt is trying to manage br0 (i.e.
resetting it and adding the vnet0 interface to it), instead of the
default virbr0, and thus overriding the network setup of yours.

What's the contents of default.xml? Is that in any way modified?

Specifically, is the following entry there?

  

(That is what is there by default.)

I suspect that there will be an entry like

  

instead, which might cause your problems.

See:
http://wiki.libvirt.org/page/VirtualNetworking
http://wiki.libvirt.org/page/Networking

In the latter page, you can see that for 'shared physical device', the
bridge setup is not done by libvirt itself (i.e. no network setup is
done in libvirt!), but rather by the distribution, and libvirt will
automatically detect that setup and provide the required options in the
host configuration for this.

So, for example, I have completely disabled the default.xml network
configuration in libvirt (no link in autostart/), and bridging still
works because libvirt detects the bridge set up by Debian's network
configuration; in the NIC settings of a virtual machine in virt-manager
I can just say 'Source device: Specify shared device name' and put in
'Bridge name: br0', and then that just works. The 'default' internal
network (corresponding to virbr0) is marked as inactive.

> brctl show returns
> 
> bridge name bridge id   STP enabled interfaces
> br0 8000.fe54004068c8   yes vnet0

Yes, here we can see that only vnet0 is part of the br0 bridge, and
vnet0 is the tun/tap/whatever device that libvirt uses for a running guest.

> Subsequent to this, I changed the default.xml package to use my local 
> subnet addresses. When I rebooted, the br0 IP was correct but nothing 
> else was up. Even after bringing up lo and eth0 and adding a default 
> gateway, my machine was still not reachable on the network.

Yes, of course, because eth0 is not part of your br0 device at that
point. If in that configuration you want the bridge to include eth0, you
could in principle do 'brctl addif br0 eth0' to add eth0 to the bridge,
but you don't want to do that at this stage, because libvirt still
thinks it's responsible for that device and bad things[tm] can happen if
you try to override that without fixing the underlying problem.

- Christian


-- 
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/545fc1e3.8020...@iwakd.de

Re: network card bridging failing on wheezy


On 09/11/14 05:09 AM, Karl E. Jorgensen wrote:

Hi

On Sat, Nov 08, 2014 at 05:57:41PM -0500, Gary Dale wrote:

For some reason my network card bridging has failed after working
properly for many years.

My /etc/network/interfaces is:

auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
 address 192.168.1.14
 netmask 255.255.255.0
 broadcast 192.168.1.255
 gateway 192.168.1.1
 bridge_ports eth0
 bridge_stp off
 bridge_fd 0
 bridge_maxwait 0

 From a fresh boot, I get nothing running. If I bring up br0
(ifconfig br0 up), it comes up with 192.168.122.1 whether I do it
with eth0 up or down. Bringing up eth0 seems to produce the correct
results - a network interface with no IP, same as it always did.

Bringing up br0 with the 192.168.1.14 address leaves me with a
machine that can't connect or be connected to. However, if I drop
br0 and bring up eth0 with the address, things work, apart from the
lack of a gateway.

I can manually add a default gateway to the route. While this works,
running the route command takes a long time to come back with the
results. However my computer now connects and can be connected to.

Hm.. I don't see "auto eth0" anywhere


auto eth0 would be incompatible with "manual".


--
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/545fbafa.1080...@torfree.net

Re: network card bridging failing on wheezy


On 09/11/14 05:27 AM, Christian Seiler wrote:

Am 08.11.2014 23:57, schrieb Gary Dale:

For some reason my network card bridging has failed after working
properly for many years.

My /etc/network/interfaces is:

auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
  address 192.168.1.14
  netmask 255.255.255.0
  broadcast 192.168.1.255
  gateway 192.168.1.1
  bridge_ports eth0
  bridge_stp off
  bridge_fd 0
  bridge_maxwait 0

  From a fresh boot, I get nothing running.

What does

  ip link show

and

  ip -4 addr show

say?

Note that in configurations where I use bridging, I don't have a 'iface
eth0 inet manual' line; since 'bridge_ports eth0' is set, this will
automatically activate 'eth0' as part of the bridge. But OTOH, I don't
see the harm that line can do...
That gets a little tricky if I do it after a fresh boot because I have 
no network running. However, in my current up and running state (eth0 
given the 192.168.1.14 IP) ifconfig returns


eth0  Link encap:Ethernet  HWaddr 00:24:1d:14:d8:42
  inet addr:192.168.1.14  Bcast:192.168.1.255 Mask:255.255.255.0
  inet6 addr: 2002:c654:a32b:0:224:1dff:fe14:d842/64 Scope:Global
  inet6 addr: fe80::224:1dff:fe14:d842/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:531054 errors:0 dropped:0 overruns:0 frame:0
  TX packets:535919 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:143598255 (136.9 MiB)  TX bytes:296648201 (282.9 MiB)
  Interrupt:41 Base address:0xe000

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:6945 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6945 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:6807129 (6.4 MiB)  TX bytes:6807129 (6.4 MiB)

vnet0 Link encap:Ethernet  HWaddr fe:54:00:40:68:c8
  inet6 addr: fe80::fc54:ff:fe40:68c8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4636 errors:0 dropped:0 overruns:0 frame:0
  TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:500
  RX bytes:575878 (562.3 KiB)  TX bytes:5876 (5.7 KiB)

ip link shows

1: lo:  mtu 16436 qdisc noqueue state UNKNOWN mode 
DEFAULT group default

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 1500 qdisc pfifo_fast 
state UP mode DEFAULT group default qlen 1000

link/ether 00:24:1d:14:d8:42 brd ff:ff:ff:ff:ff:ff
4: br0:  mtu 1500 qdisc noqueue state DOWN mode 
DEFAULT group default

link/ether fe:54:00:40:68:c8 brd ff:ff:ff:ff:ff:ff
5: vnet0:  mtu 1500 qdisc pfifo_fast 
master br0 state UNKNOWN mode DEFAULT group default qlen 500

link/ether fe:54:00:40:68:c8 brd ff:ff:ff:ff:ff:ff

ip -4 addr shows

1: lo:  mtu 16436 qdisc noqueue state UNKNOWN 
group default

inet 127.0.0.1/8 scope host lo
2: eth0:  mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000

inet 192.168.1.14/24 brd 192.168.1.255 scope global eth0
4: br0:  mtu 1500 qdisc noqueue state DOWN group 
default

inet 192.168.1.14/24 brd 192.168.1.255 scope global br0



If I bring up br0 (ifconfig
br0 up), it comes up with 192.168.122.1 whether I do it with eth0 up or
down.

This IP seems oddly familiar... Did you recently install libvirt?
Because that's the default IP for libvirt's default internal bridged
network (virbr0). Normally, that shouldn't interfere with the standard
bridge (different interface name), but maybe in your case, perhaps
because you edited your configuration?

(XML configuration under /etc/libvirt/qemu/networks/, especially look
for symlinks in /etc/libvirt/qemu/networks/autostart/. Note that if you
manually edit your libvirt configuration without virt-manager or virsh,
you first have to stop it, edit the configuration and then start it
again, else it will not work and be overwritten.)
I've had libvirt install for quite a while, I believe. I've been using 
kvm and virt-manager for years. There is a symlink (default.xml) that 
points to default.xml in the parent directory (using the full path 
name). That file does use the 192.168.122. address range.



Bringing up br0 with the 192.168.1.14 address leaves me with a machine
that can't connect or be connected to.

Is bridge-utils still installed? What does 'brctl show' say?

- Christian


brctl show returns

bridge name bridge id   STP enabled interfaces
br0 8000.fe54004068c8   yes vnet0


Subsequent to this, I changed the default.xml package to use my local 
subnet addresses. When I rebooted, the br0 IP was c

Re: network card bridging failing on wheezy

Am 08.11.2014 23:57, schrieb Gary Dale:
> For some reason my network card bridging has failed after working 
> properly for many years.
> 
> My /etc/network/interfaces is:
> 
> auto lo
> iface lo inet loopback
> iface eth0 inet manual
> auto br0
> iface br0 inet static
>  address 192.168.1.14
>  netmask 255.255.255.0
>  broadcast 192.168.1.255
>  gateway 192.168.1.1
>  bridge_ports eth0
>  bridge_stp off
>  bridge_fd 0
>  bridge_maxwait 0
> 
>  From a fresh boot, I get nothing running.

What does

 ip link show

and

 ip -4 addr show

say?

Note that in configurations where I use bridging, I don't have a 'iface
eth0 inet manual' line; since 'bridge_ports eth0' is set, this will
automatically activate 'eth0' as part of the bridge. But OTOH, I don't
see the harm that line can do...

> If I bring up br0 (ifconfig 
> br0 up), it comes up with 192.168.122.1 whether I do it with eth0 up or 
> down.

This IP seems oddly familiar... Did you recently install libvirt?
Because that's the default IP for libvirt's default internal bridged
network (virbr0). Normally, that shouldn't interfere with the standard
bridge (different interface name), but maybe in your case, perhaps
because you edited your configuration?

(XML configuration under /etc/libvirt/qemu/networks/, especially look
for symlinks in /etc/libvirt/qemu/networks/autostart/. Note that if you
manually edit your libvirt configuration without virt-manager or virsh,
you first have to stop it, edit the configuration and then start it
again, else it will not work and be overwritten.)

> Bringing up br0 with the 192.168.1.14 address leaves me with a machine 
> that can't connect or be connected to.

Is bridge-utils still installed? What does 'brctl show' say?

- Christian


-- 
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/545f41ae.3040...@iwakd.de

Re: network card bridging failing on wheezy

2014-11-09 Thread Karl E. Jorgensen

Hi

On Sat, Nov 08, 2014 at 05:57:41PM -0500, Gary Dale wrote:
> For some reason my network card bridging has failed after working
> properly for many years.
> 
> My /etc/network/interfaces is:
> 
> auto lo
> iface lo inet loopback
> iface eth0 inet manual
> auto br0
> iface br0 inet static
> address 192.168.1.14
> netmask 255.255.255.0
> broadcast 192.168.1.255
> gateway 192.168.1.1
> bridge_ports eth0
> bridge_stp off
> bridge_fd 0
> bridge_maxwait 0
> 
> From a fresh boot, I get nothing running. If I bring up br0
> (ifconfig br0 up), it comes up with 192.168.122.1 whether I do it
> with eth0 up or down. Bringing up eth0 seems to produce the correct
> results - a network interface with no IP, same as it always did.
> 
> Bringing up br0 with the 192.168.1.14 address leaves me with a
> machine that can't connect or be connected to. However, if I drop
> br0 and bring up eth0 with the address, things work, apart from the
> lack of a gateway.
> 
> I can manually add a default gateway to the route. While this works,
> running the route command takes a long time to come back with the
> results. However my computer now connects and can be connected to.

Hm.. I don't see "auto eth0" anywhere

-- 
Karl E. Jorgensen


-- 
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/20141109100954.GB20873@hawking

network card bridging failing on wheezy

2014-11-08 Thread Gary Dale

For some reason my network card bridging has failed after working 
properly for many years.


My /etc/network/interfaces is:

auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.1.14
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
bridge_maxwait 0

From a fresh boot, I get nothing running. If I bring up br0 (ifconfig 
br0 up), it comes up with 192.168.122.1 whether I do it with eth0 up or 
down. Bringing up eth0 seems to produce the correct results - a network 
interface with no IP, same as it always did.


Bringing up br0 with the 192.168.1.14 address leaves me with a machine 
that can't connect or be connected to. However, if I drop br0 and bring 
up eth0 with the address, things work, apart from the lack of a gateway.


I can manually add a default gateway to the route. While this works, 
running the route command takes a long time to come back with the 
results. However my computer now connects and can be connected to.


Unfortunately I can't run virtual machines without the bridging (why I 
was using it in the first place).


Any thoughts anyone?


--
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/545e9fe5.50...@torfree.net

Re: where to report bug: Wheezy installer failed on a RTL8169 network card

2012-08-29 Thread Martin Steigerwald

Am Mittwoch, 29. August 2012 schrieb Yuwen Dai:
> Dear all,
> 
> I downloaded the latest Wheezy AMD64 version DVD iso image, trying to
> install it on a HP notebook with a RTL8169 NIC.  When the installer
> detects network, it hangs.  I could switch to other ttys and open a
> busybox  shell, but it's useless, the installation could not resume
> any more.  I tried a Squeeze  DVD on the same notebook,  the DHCP
> process appeared some difficult, I tried several times,  but at last,
> it got IP address.  Where can I report this bug?

One thing that you may try unless the bug report mentioned by you does not 
yet have this information:

Go to tty4 (Alt-F4) and look for suspicious log messages. You can add to 
the bug report by sending an mail to bu...@bugs.debian.org

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


-- 
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/201208291911.54549.mar...@lichtvoll.de

Re: where to report bug: Wheezy installer failed on a RTL8169 network card

2012-08-28 Thread Yuwen Dai

>
> Thank you for testing the early installer and then reporting problems
> with it.  The place to report those bugs is the "installation-reports"
> package.
>
>   
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=installation-reports
>
> You would want to look over the bugs already filed there to see if one
> matches.  In particular there is a now known kernel bug which caused
> hangs at boot that was just this week closed.  If not then file your
> details there.
>
> I recommend that you try one of the very new daily built netinst
> images from http://cdimage.debian.org/cdimage/weekly-builds/ to see if
> the latest is still a problem.
>
> Bob

Hi Bob,

Thank you for the links.  It appears that this is  a known bug:


#679795
Installation freezes when detecting network card Ralink corp. RT5390
Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E

Best regards,
Yuwen


-- 
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/candez-yew+euhfiom6vb34vezfugx77dwfuushpeybjeydp...@mail.gmail.com

Re: where to report bug: Wheezy installer failed on a RTL8169 network card

2012-08-28 Thread Bob Proulx

Yuwen Dai wrote:
> I downloaded the latest Wheezy AMD64 version DVD iso image, trying to
> install it on a HP notebook with a RTL8169 NIC.  When the installer
> detects network, it hangs.  I could switch to other ttys and open a
> busybox  shell, but it's useless, the installation could not resume
> any more.  I tried a Squeeze  DVD on the same notebook,  the DHCP
> process appeared some difficult, I tried several times,  but at last,
> it got IP address.  Where can I report this bug?

Thank you for testing the early installer and then reporting problems
with it.  The place to report those bugs is the "installation-reports"
package.

http://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=installation-reports

You would want to look over the bugs already filed there to see if one
matches.  In particular there is a now known kernel bug which caused
hangs at boot that was just this week closed.  If not then file your
details there.

I recommend that you try one of the very new daily built netinst
images from http://cdimage.debian.org/cdimage/weekly-builds/ to see if
the latest is still a problem.

Bob

signature.asc
Description: Digital signature

where to report bug: Wheezy installer failed on a RTL8169 network card

2012-08-28 Thread Yuwen Dai

Dear all,

I downloaded the latest Wheezy AMD64 version DVD iso image, trying to
install it on a HP notebook with a RTL8169 NIC.  When the installer
detects network, it hangs.  I could switch to other ttys and open a
busybox  shell, but it's useless, the installation could not resume
any more.  I tried a Squeeze  DVD on the same notebook,  the DHCP
process appeared some difficult, I tried several times,  but at last,
it got IP address.  Where can I report this bug?

Best regards,
Yuwen


-- 
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/CANdEz-Y02n62qLiZyH-UMKjvt5ZH3yMhdc+j=+we3jr5rac...@mail.gmail.com

Re: Re: IRQ conflict IRQ0 network card.

2012-08-16 Thread Bhasker C V

Got this working.
The problem was local APIC was not enabled in the bios. Once enabled
everything started to fall in place.

thanks all for your inputs and help

On Thu, 16 Aug 2012 09:03:16 +0100, Bhasker C V wrote:

>  I have a old PC (AMD athelon 3000+) which has an onboard network card
> (gige-tg3) kernel 3.5.0 debian squeeze.

Have you tried with Debian stock kernel (2.6.32) or the backported one
(3.2)? :-?

> 03:16.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S
> [Rhine-III] (rev 86)
>
>
>  When I do an ifconfig eth1 up (eth0 is another external card) I get
> this error
>
>
> [  408.536851] genirq: Flags mismatch irq 0. 0080 (eth1) vs.
> 00015a20 (timer)

Is the network card working despite the error? I mean, kernel can be very
verbose but some messages are also harmless, just informative.
 
> I tried to google for this but could not get any good fix information
> for this issue. The card is not working as of now but was working fine
> with FreeBSD kernel.

Ah, then the problem is for real :-(

> Has anyone encountered this before

Google suggests the message comes from kernel 3.5.0, I would look for any
specific patch that solves this, if any.

> I have tried hpet=none (just to score off the hpet IRQ and this card IRQ
> clash)
> I have tried pci=biosirq
>
> When I load the driver these are the messages
>
> [  803.569255] tg3.c:v3.123 (March 21, 2012)
> [  803.631887] tg3 :02:00.0: eth1: Tigon3 [partno(BCM95789) rev
4101] (PCI Express) MAC address 00:30:1b:b9:d5:e3
> [  803.631895] tg3 :02:00.0: eth1: attached PHY is 5750
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
> [  803.631899] tg3 :02:00.0: eth1: RXcsums[1] LinkChgREG[0]
MIirq[0] ASF[0] TSOcap[1]
> [  803.631903] tg3 :02:00.0: eth1: dma_rwctrl[7618]
dma_mask[64-bit]

The card seems to be properly detected :-?

> When I do a ifconfig up I get this message
>
> [  823.525509] genirq: Flags mismatch irq 0. 0080 (eth1) vs.
00015a20 (timer)

What's the full output of "ifconfig eth1"?

Greetings,

-- 
Camaleón

-- 
Bhasker C V
To feel rich count all things you have in life that money can't buy.
Secure mails:
https://keyserver.pgp.com/vkd/DownloadKey.event?keyid=0x524E35A193ABFB8E


-- 
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/502d5b9b.70...@unixindia.com

Re: IRQ conflict IRQ0 network card.

2012-08-16 Thread Camaleón

On Thu, 16 Aug 2012 09:03:16 +0100, Bhasker C V wrote:

>  I have a old PC (AMD athelon 3000+) which has an onboard network card
> (gige-tg3) kernel 3.5.0 debian squeeze.

Have you tried with Debian stock kernel (2.6.32) or the backported one 
(3.2)? :-?

> 03:16.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S
> [Rhine-III] (rev 86)
> 
> 
>  When I do an ifconfig eth1 up (eth0 is another external card) I get
> this error
> 
> 
> [  408.536851] genirq: Flags mismatch irq 0. 0080 (eth1) vs.
> 00015a20 (timer)

Is the network card working despite the error? I mean, kernel can be very 
verbose but some messages are also harmless, just informative.
 
> I tried to google for this but could not get any good fix information
> for this issue. The card is not working as of now but was working fine
> with FreeBSD kernel.

Ah, then the problem is for real :-(

> Has anyone encountered this before

Google suggests the message comes from kernel 3.5.0, I would look for any 
specific patch that solves this, if any.

> I have tried hpet=none (just to score off the hpet IRQ and this card IRQ
> clash)
> I have tried pci=biosirq
> 
> When I load the driver these are the messages
> 
> [  803.569255] tg3.c:v3.123 (March 21, 2012) 
> [  803.631887] tg3 :02:00.0: eth1: Tigon3 [partno(BCM95789) rev 4101] 
> (PCI Express) MAC address 00:30:1b:b9:d5:e3 
> [  803.631895] tg3 :02:00.0: eth1: attached PHY is 5750 
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
> [  803.631899] tg3 :02:00.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] 
> ASF[0] TSOcap[1]
> [  803.631903] tg3 :02:00.0: eth1: dma_rwctrl[7618] dma_mask[64-bit]

The card seems to be properly detected :-?

> When I do a ifconfig up I get this message
> 
> [  823.525509] genirq: Flags mismatch irq 0. 0080 (eth1) vs. 00015a20 
> (timer)

What's the full output of "ifconfig eth1"?

Greetings,

-- 
Camaleón


-- 
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/k0j3ak$svs$8...@ger.gmane.org

Re: IRQ conflict IRQ0 network card.

2012-08-16 Thread Giancarlo Pegoraro


Olà,

Il 16/08/2012 10:03, Bhasker C V ha scritto:

Hi,


---cut---


Has anyone encountered this before


I have tried hpet=none (just to score off the hpet IRQ and this card IRQ
clash)
I have tried pci=biosirq


Another possibility,
if you use grub-pc, put irqpoll in the /etc/default/grub

#nano /etc/default/grub


GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet irqpoll"
GRUB_CMDLINE_LINUX=""


after
#update-grub


---cut--

IF anyone has got an experience dealing with this issue can you give me
inputs please ?

thanks




--
Ciao Genki ):o))


--
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/502cce43.7040...@gmail.com

IRQ conflict IRQ0 network card.

2012-08-16 Thread Bhasker C V

Hi,

 I have a old PC (AMD athelon 3000+) which has an onboard network card
(gige-tg3) kernel 3.5.0 debian squeeze.

03:16.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S
[Rhine-III] (rev 86)


 When I do an ifconfig eth1 up (eth0 is another external card) I get
this error


[  408.536851] genirq: Flags mismatch irq 0. 0080 (eth1) vs.
00015a20 (timer)

I tried to google for this but could not get any good fix information
for this issue. The card is not working as of now but was working fine
with FreeBSD kernel.

Has anyone encountered this before


I have tried hpet=none (just to score off the hpet IRQ and this card IRQ
clash)
I have tried pci=biosirq

When I load the driver these are the messages

[  803.569255] tg3.c:v3.123 (March 21, 2012)
[  803.631887] tg3 :02:00.0: eth1: Tigon3 [partno(BCM95789) rev
4101] (PCI Express) MAC address 00:30:1b:b9:d5:e3
[  803.631895] tg3 :02:00.0: eth1: attached PHY is 5750
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[  803.631899] tg3 :02:00.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0]
ASF[0] TSOcap[1]
[  803.631903] tg3 :02:00.0: eth1: dma_rwctrl[7618] dma_mask[64-bit]

When I do a ifconfig up I get this message

[  823.525509] genirq: Flags mismatch irq 0. 0080 (eth1) vs.
00015a20 (timer)


IF anyone has got an experience dealing with this issue can you give me
inputs please ?

thanks

-- 
Bhasker C V
Secure Mails:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D05FEEC54E47413


-- 
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/502ca944.4040...@unixindia.com

Re: 6.0.5 ia64 network card question

2012-05-17 Thread Stan Hoeppner

On 5/17/2012 8:59 AM, Bill Mclain wrote:
> Actually I meant ia64, but I got it working. Thanks for all the help!

Into which/whose Itanium server did you install this Best Buy NIC?
Seems strange to install such an el cheapo NIC into an $8-$10K (minimum)
server.

-- 
Stan


> Bill McLain
> Windows Environment Administrator
> Desk: 601-487-5241
> Cell: 601-213-6524
> 
> -Original Message-
> From: Stan Hoeppner [mailto:s...@hardwarefreak.com] 
> Sent: Wednesday, May 16, 2012 6:44 PM
> To: Bill McLain
> Cc: debian-user@lists.debian.org
> Subject: Re: 6.0.5 ia64 network card question
> 
> On 5/16/2012 4:03 PM, Bill Mclain wrote:
> 
>> Can anyone assist me with getting drivers and installing a Dynex DX-PCIGB 
>> network card? I also have a USB Netgear Wireless n300 adapter as an 
>> alternative but I cannot get it to install either. Thanks and any info I did 
>> not provide just let me know and I will get it to you.
> 
> First, I'd guess you really didn't mean "IA64" but "AMD64".  As for the Best 
> Buy house brand NIC, post lscpi output for the device.  The name on the card 
> is irrelevant.  What matters is what ethernet ASIC it has.
> Linux drives are written to the ASIC interface.
> 
> --
> Stan
> 


-- 
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/4fb54042.4090...@hardwarefreak.com

Re: 6.0.5 ia64 network card question

2012-05-16 Thread Stan Hoeppner

On 5/16/2012 6:44 PM, Stan Hoeppner wrote:
> On 5/16/2012 4:03 PM, Bill Mclain wrote:
> 
>> Can anyone assist me with getting drivers and installing a Dynex DX-PCIGB 
>> network card? I also have a USB Netgear Wireless n300 adapter as an 
>> alternative but I cannot get it to install either. Thanks and any info I did 
>> not provide just let me know and I will get it to you.
> 
> First, I'd guess you really didn't mean "IA64" but "AMD64".  As for the
> Best Buy house brand NIC, post lscpi output for the device.  The name on
> the card is irrelevant.  What matters is what ethernet ASIC it has.
> Linux drives are written to the ASIC interface.

"lspci" that is, for instance:

~$ lspci|grep -i ethernet
00:0d.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet\
Pro 100 (rev 08)

Which requires the driver "e100".

-- 
Stan


-- 
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/4fb4674c.3030...@hardwarefreak.com

Re: 6.0.5 ia64 network card question

2012-05-16 Thread Stan Hoeppner

On 5/16/2012 4:03 PM, Bill Mclain wrote:

> Can anyone assist me with getting drivers and installing a Dynex DX-PCIGB 
> network card? I also have a USB Netgear Wireless n300 adapter as an 
> alternative but I cannot get it to install either. Thanks and any info I did 
> not provide just let me know and I will get it to you.

First, I'd guess you really didn't mean "IA64" but "AMD64".  As for the
Best Buy house brand NIC, post lscpi output for the device.  The name on
the card is irrelevant.  What matters is what ethernet ASIC it has.
Linux drives are written to the ASIC interface.

-- 
Stan

-- 
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/4fb43bd5.70...@hardwarefreak.com

RE: 6.0.5 ia64 network card question

2012-05-16 Thread Bill Mclain


All,
Can anyone assist me with getting drivers and installing a Dynex DX-PCIGB 
network card? I also have a USB Netgear Wireless n300 adapter as an alternative 
but I cannot get it to install either. Thanks and any info I did not provide 
just let me know and I will get it to you.

Bill

Re: LSPCI shows network card, but the card refuses to come up

2012-03-26 Thread Camaleón

On Mon, 26 Mar 2012 16:27:50 +0300, Andrei POPESCU wrote:

> On Mi, 21 mar 12, 15:14:14, Camaleón wrote:
>> 
>> Nah, yours is too verbose for this matter ;-). Indeed, the extra
>> information (-v) can be omited as we just wanted to know what card it
>> was.
> 
> In which case -nn is very useful.

To know the card's name/model, "-v" or "-nn" flags are both fine.

Greetings,

-- 
Camaleón


-- 
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/jkpu5g$4vf$4...@dough.gmane.org

Re: LSPCI shows network card, but the card refuses to come up

2012-03-26 Thread Andrei POPESCU

On Mi, 21 mar 12, 15:14:14, Camaleón wrote:
> 
> Nah, yours is too verbose for this matter ;-). Indeed, the extra information 
> (-v) can be omited as we just wanted to know what card it was.

In which case -nn is very useful.

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: LSPCI shows network card, but the card refuses to come up

2012-03-21 Thread Camaleón

On Tue, 20 Mar 2012 18:37:09 -0600, Bob Proulx wrote:

> Camaleón wrote:
>> Bijoy Lobo wrote:
>> > I have 2 cards on my system. I had no errors while Expert Install of
>> > Debian netinstall. even lspci shows me 2 ethernet controllers,
>> > However I cannot bring the 2nd interface up.
>>
>> Show us the output of these two commands:
>> 
>> lspci -v | grep -i ether
> 
> Ahem...  'lspci | grep -i eth' is good but 'lspci -v' is paragraph
> formatted and so finding that with grep is more trouble.  You need a
> "paragraph grep" of which there are many different programs and
> techniques.  Perl is always available these days so perhaps using perl
> is easiest.
> 
>   lspci -v | perl -00 -ne 'm/eth/i && print'
> 
> The extra -v information isn't usually useful though.  YMMV.

(...)

Let's try out both:

sm01@stt008:~$ lspci -v | grep -i ether
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network 
Connection (rev 02)
11:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit 
Ethernet (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet

Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet



sm01@stt008:~$ lspci -v | perl -00 -ne 'm/eth/i && print'
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network 
Connection (rev 02)
Subsystem: Super Micro Computer Inc Device 10bd
Flags: bus master, fast devsel, latency 0, IRQ 1276
Memory at dc60 (32-bit, non-prefetchable) [size=128K]
Memory at dc625000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1820 [size=32]
Capabilities: 
Kernel driver in use: e1000e
Kernel modules: e1000e

11:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit 
Ethernet (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
I/O ports at 2000 [size=256]
Memory at dc30 (32-bit, non-prefetchable) [size=256]
[virtual] Expansion ROM at dc40 [disabled] [size=128K]
Capabilities: 
Kernel driver in use: r8169
Kernel modules: r8169

Nah, yours is too verbose for this matter ;-). Indeed, the extra information 
(-v) can be omited as we just wanted to know what card it was.

Greetings,

-- 
Camaleón


-- 
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/jkcr86$lch$4...@dough.gmane.org

Re: LSPCI shows network card, but the card refuses to come up

2012-03-21 Thread Alberto Fuentes


On 21/03/12 11:49, Bob Proulx wrote:

But why did you stop at five lines?  Aren't most network devices going
to print more lines than that?  And it misses the "kernel driver in
use" line which is useful information.


I see, in my case, 5 was enough to show everything :)



Can't leave off the '-A' --after-context part since otherwise -NUM is
the same as --context not --after-context.


I said even easier, because the info you are looking for shows up the 
same as with the qualifier, and you don’t have to remember witch is 
witch (and less typing!)


that said, i have a bind grep='grep --color' witch i think is a must as 
well ;)


greets!
aL


--
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/4f69b73a.9040...@qindel.com

Re: LSPCI shows network card, but the card refuses to come up

2012-03-21 Thread Bob Proulx

Alberto Fuentes wrote:
> for the shake of completesness

I commend your thoroughness.  But...

> lspci -v | grep -A5 -i eth

But why did you stop at five lines?  Aren't most network devices going
to print more lines than that?  And it misses the "kernel driver in
use" line which is useful information.

Example:

  root@fury:~# lspci -v | perl -00 -ne 'm/eth/i && print'
  3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755 Gigabit 
Ethernet PCI Express (rev 02)
  Subsystem: Hewlett-Packard Company Device 280c
  Flags: bus master, fast devsel, latency 0, IRQ 28
  Memory at e040 (64-bit, non-prefetchable) [size=64K]
  Expansion ROM at  [disabled]
  Capabilities: [48] Power Management version 3
  Capabilities: [50] Vital Product Data
  Capabilities: [58] Vendor Specific Information: Len=78 
  Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [d0] Express Endpoint, MSI 00
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [13c] Virtual Channel
  Capabilities: [160] Device Serial Number 00-1b-78-ff-fe-b0-a3-14
  Capabilities: [16c] Power Budgeting 
  Kernel driver in use: tg3

  root@fury:~# lspci -v | grep -A5 -i eth
  3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755 Gigabit 
Ethernet PCI Express (rev 02)
  Subsystem: Hewlett-Packard Company Device 280c
  Flags: bus master, fast devsel, latency 0, IRQ 28
  Memory at e040 (64-bit, non-prefetchable) [size=64K]
  Expansion ROM at  [disabled]
  Capabilities: [48] Power Management version 3

> or the even easier
> lspci -v | grep -5 -i eth

Can't leave off the '-A' --after-context part since otherwise -NUM is
the same as --context not --after-context.

  root@fury:~# lspci -v | grep -5 -i eth
  Capabilities: [78] Express Endpoint, MSI 00
  Capabilities: [100] Virtual Channel
  Capabilities: [128] Power Budgeting 
  Kernel driver in use: nouveau

  3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755 Gigabit 
Ethernet PCI Express (rev 02)
  Subsystem: Hewlett-Packard Company Device 280c
  Flags: bus master, fast devsel, latency 0, IRQ 28
  Memory at e040 (64-bit, non-prefetchable) [size=64K]
  Expansion ROM at  [disabled]
  Capabilities: [48] Power Management version 3

Bob


signature.asc
Description: Digital signature

Re: LSPCI shows network card, but the card refuses to come up

2012-03-21 Thread Alberto Fuentes


On 21/03/12 01:37, Bob Proulx wrote:

Ahem...  'lspci | grep -i eth' is good but 'lspci -v' is paragraph
formatted and so finding that with grep is more trouble.  You need a
"paragraph grep" of which there are many different programs and
techniques.  Perl is always available these days so perhaps using perl
is easiest.

for the shake of completesness

lspci -v | grep -A5 -i eth

or the even easier
lspci -v | grep -5 -i eth

greets!
aL


--
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/4f69916b.50...@qindel.com

Re: LSPCI shows network card, but the card refuses to come up

2012-03-20 Thread Bijoy Lobo

Hello guys,


Thanks alot. I sloved the problem. It was the older kernel which didnt have
support for my Atheros Card. I did a modprobe and it fixed the problem

On Wed, Mar 21, 2012 at 6:07 AM, Bob Proulx  wrote:

> Camaleón wrote:
> > Bijoy Lobo wrote:
> > > I have 2 cards on my system. I had no errors while Expert Install of
> > > Debian netinstall. even lspci shows me 2 ethernet controllers, However
> I
> > > cannot bring the 2nd interface up.
> >
> > Show us the output of these two commands:
> >
> > lspci -v | grep -i ether
>
> Ahem...  'lspci | grep -i eth' is good but 'lspci -v' is paragraph
> formatted and so finding that with grep is more trouble.  You need a
> "paragraph grep" of which there are many different programs and
> techniques.  Perl is always available these days so perhaps using perl
> is easiest.
>
>  lspci -v | perl -00 -ne 'm/eth/i && print'
>
> The extra -v information isn't usually useful though.  YMMV.
>
> > dmesg | grep -i eth
> >
> > > ifconfig eth1 tells me no such interface ifconfig -a show me only eth0
> > > and lo
> >
> > Also, show us the content of your "/etc/network/interfaces" file.
>
> Please also show us the output of
>
>  ip addr show
>
> and also
>
>  cat /etc/udev/rules.d/70-persistent-net.rules
>
> Bob
>



-- 
Thanks and Regards
Bijoy Lobo
Paladion Networks

Re: LSPCI shows network card, but the card refuses to come up

2012-03-20 Thread Bob Proulx

Camaleón wrote:
> Bijoy Lobo wrote:
> > I have 2 cards on my system. I had no errors while Expert Install of
> > Debian netinstall. even lspci shows me 2 ethernet controllers, However I
> > cannot bring the 2nd interface up.
>
> Show us the output of these two commands:
> 
> lspci -v | grep -i ether

Ahem...  'lspci | grep -i eth' is good but 'lspci -v' is paragraph
formatted and so finding that with grep is more trouble.  You need a
"paragraph grep" of which there are many different programs and
techniques.  Perl is always available these days so perhaps using perl
is easiest.

  lspci -v | perl -00 -ne 'm/eth/i && print'

The extra -v information isn't usually useful though.  YMMV.

> dmesg | grep -i eth
> 
> > ifconfig eth1 tells me no such interface ifconfig -a show me only eth0
> > and lo
> 
> Also, show us the content of your "/etc/network/interfaces" file.

Please also show us the output of

  ip addr show

and also

  cat /etc/udev/rules.d/70-persistent-net.rules

Bob

signature.asc
Description: Digital signature

Re: LSPCI shows network card, but the card refuses to come up

2012-03-20 Thread Camaleón

On Tue, 20 Mar 2012 19:11:39 +0530, Bijoy Lobo wrote:

> I have 2 cards on my system. I had no errors while Expert Install of
> Debian netinstall. even lspci shows me 2 ethernet controllers, However I
> cannot bring the 2nd interface up.

Show us the output of these two commands:

lspci -v | grep -i ether
dmesg | grep -i eth

> ifconfig eth1 tells me no such interface ifconfig -a show me only eth0
> and lo

Also, show us the content of your "/etc/network/interfaces" file.

Greetings,

-- 
Camaleón


-- 
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/jka4r3$v8o$3...@dough.gmane.org

Re: LSPCI shows network card, but the card refuses to come up

2012-03-20 Thread The_Ace

On Tue, Mar 20, 2012 at 7:11 PM, Bijoy Lobo  wrote:
>
> Hello all
>
> I have 2 cards on my system. I had no errors while Expert Install of
> Debian netinstall. even lspci shows me 2 ethernet controllers, However I
> cannot bring the 2nd interface up.
>
> ifconfig eth1 tells me no such interface
> ifconfig -a show me only eth0 and lo
>
> --
> Thanks and Regards
> Bijoy Lobo
> Paladion Networks


Does lspci -v (or -vv) show what driver and kernel modules are in use
for that card ?


--
The mysteries of the Universe are revealed when you break stuff.


-- 
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/CAM8yCh_rdQF+taAQRRXKnrqR13=81b3ma6marrqjotejdjq...@mail.gmail.com

LSPCI shows network card, but the card refuses to come up

2012-03-20 Thread Bijoy Lobo

Hello all

I have 2 cards on my system. I had no errors while Expert Install of Debian
netinstall. even lspci shows me 2 ethernet controllers, However I cannot
bring the 2nd interface up.

ifconfig eth1 tells me no such interface
ifconfig -a show me only eth0 and lo

-- 
Thanks and Regards
Bijoy Lobo
Paladion Networks

Re: Testing a network card

2011-01-30 Thread Camaleón

On Sun, 30 Jan 2011 12:04:14 +0700, logb wrote:

> Is there anyone know how to test PPS (packet per second) of a nic? I
> tried to googled it, only found how to test the bandwidth using iperf or
> netperf. None found for PPS.
> 
> Any hint are welcome.

I found an article on the matter:

Benchmark the packets-per-second performance of a network device
http://blog.famzah.net/2009/11/24/benchmark-the-packets-per-second-performance-of-a-network-device/

Greetings,

-- 
Camaleón


-- 
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/pan.2011.01.30.14.01...@gmail.com

Re: Testing a network card

2011-01-30 Thread elbbit

On 30/01/11 05:04, logb wrote:
> Hello,
> 
> Is there anyone know how to test PPS (packet per second) of a nic?
> I tried to googled it, only found how to test the bandwidth using
> iperf or netperf. None found for PPS.
> 
> Any hint are welcome.
> 
> TIA.
> 

Maybe you could use a "ping -f "

With the result you could take the delivered packets divided by 1000ms
to equal the amount of packets per second?

Or you could do something else to flood the interface and measure with
iptraf?

iptop and saidar do not seem to show packets/sec.

-- 

elbbit

-- 
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/4d456c62.6000...@gmail.com

Re: Testing a network card

2011-01-29 Thread Anand Sivaram

On Sun, Jan 30, 2011 at 10:34, logb  wrote:

> Hello,
>
> Is there anyone know how to test PPS (packet per second) of a nic?
> I tried to googled it, only found how to test the bandwidth using
> iperf or netperf. None found for PPS.
>
> Any hint are welcome.
>
> TIA.
>
> --
> -- logb - monkey.org fans - logb.dagdigdug.com -
>
>
> --
> 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/AANLkTi=pbnbo4ffc+ijbjequaprvna1j2pd1k2bhz...@mail.gmail.com
>
>
I could see packets per second in "bwm-ng" console.  After starting bwm-ng,
type 'u' a couple of times, it shown packet per second also.
Also try to change the Maximum Segment Size of TCP to try out different
sizes.

Testing a network card

2011-01-29 Thread logb

Hello,

Is there anyone know how to test PPS (packet per second) of a nic?
I tried to googled it, only found how to test the bandwidth using
iperf or netperf. None found for PPS.

Any hint are welcome.

TIA.

-- 
-- logb - monkey.org fans - logb.dagdigdug.com -


-- 
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/AANLkTi=pbnbo4ffc+ijbjequaprvna1j2pd1k2bhz...@mail.gmail.com

Re: network card

2010-09-02 Thread Jonathan Wiltshire

On Thu, Sep 02, 2010 at 07:51:00AM -0400, chris chalifoux wrote:
> hi i was wondering will 512AN_MMWW2 it is a min pci exprress card and i was
> wondering will it woork ?
> thank you chris

Please ask on the debian-user@lists.debian.org list, as copied.

-- 
Jonathan Wiltshire

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51


-- 
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/20100902122605.ga24...@lupin.powdarrmonkey.net

Re: Debian amd64 not detecting my network card (32 bit Debian does!)

2010-07-13 Thread H.S.

On 10-07-13 02:15 PM, H.S. wrote:

On 10-07-13 12:43 PM, H.S. wrote:

I decided to install amd64 on my computer which has Asus M3 socket
motherboard, M4A88TD-V EVO/USB3, chipset AMD 880G/SB850, and onboard
gigabit lan controller, Realtek® 8111E.

I installed 32 bit Debian using netinstall some days ago without too
many problems (see my post with subject Asus M4A88TD-V EVO/USB3 (was:Re:
AM3 socket Asus M4A87TD EVO ...).

But today when I booted my USB stick to install amd64 Debian, the
installer failed to detect my network card. Boot disk was created using
the two step procedure listed here (Squeeze section):
http://wiki.debian.org/DebianEeePC/HowTo/InstallUsingStandardInstaller

I also tried different boot.img.gz and net installer from the following
sites:

for boot image:
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/

(file date is 17:58 26-06-10)
http://ftp.nl.debian.org/debian/dists/lenny/main/installer-amd64/current/images/hd-media/

(file date is 22:43 10-07-10)

for net installer iso:
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/ (file
date is 17-Feb-2010 23:05)
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/

(file date is 13-Jul-2010 17:11)

So, the 32 bit installer worked on my motherboard but amd64 bit
installer fails to see the network card. Is there something I am missing
here?

Thanks.

Just a little update.

Getting the net install iso and the boot.img.gz from Lenny's download
page (stable release) works. The link is:
http://www.debian.org/releases/lenny/debian-installer/

Both the firewire and gigabit controller are detected. Also, there are
no warning for mismatch between the modules in the version being
installed and the kernel.

The problem, however, is that Lenny's installer does not give me an
option to format in ext4 filesystem, which I want. So I am still looking
for a solution to make testing or daily builds of installer to detect
the network card on my board.

Replying to myself again :)

Got it working by using the boot.img.gz from here:
http://d-i.debian.org/daily-images/amd64/daily/hd-media/

and net install iso from here:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/

In fact, I booted after install an older LAN NIC hoping that it would
surely work. But this time the installer detected both the lan cards,
the onboard and the PCI one. Installation is continuing now.

--
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/i1icce$oj...@dough.gmane.org

Re: Debian amd64 not detecting my network card (32 bit Debian does!)

2010-07-13 Thread H.S.

On 10-07-13 12:43 PM, H.S. wrote:

I decided to install amd64 on my computer which has Asus M3 socket
motherboard, M4A88TD-V EVO/USB3, chipset AMD 880G/SB850, and onboard
gigabit lan controller, Realtek® 8111E.

I installed 32 bit Debian using netinstall some days ago without too
many problems (see my post with subject Asus M4A88TD-V EVO/USB3 (was:Re:
AM3 socket Asus M4A87TD EVO ...).

I also tried different boot.img.gz and net installer from the following
sites:

for boot image:
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/
(file date is 17:58 26-06-10)
http://ftp.nl.debian.org/debian/dists/lenny/main/installer-amd64/current/images/hd-media/
(file date is 22:43 10-07-10)

So, the 32 bit installer worked on my motherboard but amd64 bit
installer fails to see the network card. Is there something I am missing
here?

Thanks.

Just a little update.

Getting the net install iso and the boot.img.gz from Lenny's download
page (stable release) works. The link is:

http://www.debian.org/releases/lenny/debian-installer/

Both the firewire and gigabit controller are detected. Also, there are
no warning for mismatch between the modules in the version being
installed and the kernel.

--
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/i1iagc$hs...@dough.gmane.org

Debian amd64 not detecting my network card (32 bit Debian does!)

2010-07-13 Thread H.S.



I decided to install amd64 on my computer which has Asus M3 socket 
motherboard, M4A88TD-V EVO/USB3, chipset AMD 880G/SB850, and onboard 
gigabit lan controller, Realtek® 8111E.


I installed 32 bit Debian using netinstall some days ago without too 
many problems (see my post with subject Asus M4A88TD-V EVO/USB3 (was:Re: 
AM3 socket Asus M4A87TD EVO ...).


But today when I booted my USB stick to install amd64 Debian, the 
installer failed to detect my network card. Boot disk was created using 
the two step procedure listed here (Squeeze section):

http://wiki.debian.org/DebianEeePC/HowTo/InstallUsingStandardInstaller

I also tried different boot.img.gz and net installer from the following 
sites:


for boot image:
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/ 
(file date is 17:58 26-06-10)
http://ftp.nl.debian.org/debian/dists/lenny/main/installer-amd64/current/images/hd-media/ 
(file date is 22:43 10-07-10)


for net installer iso:
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/ (file 
date is 17-Feb-2010 23:05)
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ 
(file date is  13-Jul-2010 17:11)



So, the 32 bit installer worked on my motherboard but amd64 bit 
installer fails to see the network card. Is there something I am missing 
here?


Thanks.








--
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/i1i52n$sp...@dough.gmane.org

Re: Belkin 54g Wireless Desktop Network Card

2009-02-17 Thread Celejar

On Tue, 17 Feb 2009 15:19:50 +
Martin Sewell  wrote:

> I'd be most grateful for any advice on how to get the following working 
> with Debian 2.6.18-6-486.
> 
> Belkin 54g Wireless Desktop Network Card
> model no. F5D7000
> version 1133uk

We need the chipset information (lspci).

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Belkin 54g Wireless Desktop Network Card

2009-02-17 Thread Martin Sewell

I'd be most grateful for any advice on how to get the following working 
with Debian 2.6.18-6-486.


Belkin 54g Wireless Desktop Network Card
model no. F5D7000
version 1133uk

Many thanks

Martin


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Nelson Castillo

On Wed, Nov 19, 2008 at 8:06 AM, 中和刘 <[EMAIL PROTECTED]> wrote:
> when a user visit my website, it's easy to get the ip address of the
> user, but i think IP address is not as stable as mac address, so I
> hope I can get the mac address of the user according to its IP
> address, is it possible? thanks

No. It is not possible unless you're on the same physical network.

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread owens

>
>
>
> Original Message 
>From: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: how to get the mac address(network card physical
>address) of a remote computer by its IP address?
>Date: Wed, 19 Nov 2008 15:16:34 +0200
>
>>On Wed, Nov 19, 2008 at 3:06 PM, ??? <[EMAIL PROTECTED]>
>wrote:
>>
>>> when a user visit my website, it's easy to get the ip address of
>the
>>> user, but i think IP address is not as stable as mac address, so I
>>> hope I can get the mac address of the user according to its IP
>>> address, is it possible? thanks
>>>
>>> --
>>> Welcome to visit my home page http://www.starliu.com
>>> [It's only accessable when my pc is turned on, on which it's
>hosted.]
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>>> with a subject of "unsubscribe". Trouble? Contact
>>> [EMAIL PROTECTED]
>>>
>>>
>>Well, if the visitor uses DHCP, then his IP will change at some
>point, so
>>one cannot
>>tell the MAC if one knows the IP...however, there are tools like
>wireshark
>>that can help you
>>with MAC's.
>>
AFAIK the MAC address is only available within a single network. 
Once the packet leaves the net as an IP packet all knowledge of the
MAC disappears.  Also wireshark (PKA Ethereal) is designed to do
packet analysis by sniffing on a single net (usually by putting the
computer on which wireshark is hosted in promiscuous mode).  This
doesn't work outside the originater's net
Larry




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

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Micha

On Wed, 19 Nov 2008 21:06:13 +0800
"中和刘" <[EMAIL PROTECTED]> wrote:

> when a user visit my website, it's easy to get the ip address of the
> user, but i think IP address is not as stable as mac address, so I
> hope I can get the mac address of the user according to its IP
> address, is it possible? thanks
> 



It's not possible. You can only get mac addresses using arp on the local lan.
You can't even be sure that you got a correct ip address if your users are
going through a proxy or nat.


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

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

On Wed, Nov 19, 2008 at 9:50 PM, Jochen Schulz <[EMAIL PROTECTED]> wrote:
> 中和刘:
>>
>> when a user visit my website, it's easy to get the ip address of the
>> user, but i think IP address is not as stable as mac address, so I
>> hope I can get the mac address of the user according to its IP
>> address, is it possible? thanks
>
> No, it's not possible. Ethernet frames aren't routed on the internet.
> You cannot even be sure that your users connect using Ethernet on their
> end.
thanks, i will give up

> Usually, HTTP-cookies are used as a solution for your problem.
>
> J.
> --
> Television advertisements are the apothesis of twentieth century culture.
> [Agree]   [Disagree]
> 
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkkkGbwACgkQ+AfZydWK2zmkRwCgr+B1A4G2tLb0n1lRbGJXhyIM
> suIAn03CUuV3MD8PRjfdEnURYh62jC6k
> =4cbC
> -END PGP SIGNATURE-
>
>



-- 
Welcome to visit my home page http://www.starliu.com
[It's only accessable when my pc is turned on, on which it's hosted.]

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Jochen Schulz

中和刘:
>
> when a user visit my website, it's easy to get the ip address of the
> user, but i think IP address is not as stable as mac address, so I
> hope I can get the mac address of the user according to its IP
> address, is it possible? thanks

No, it's not possible. Ethernet frames aren't routed on the internet.
You cannot even be sure that your users connect using Ethernet on their
end.

Usually, HTTP-cookies are used as a solution for your problem.

J.
-- 
Television advertisements are the apothesis of twentieth century culture.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Ron Johnson


On 11/19/08 07:16, Aioanei Rares wrote:
[snip]


Well, if the visitor uses DHCP, then his IP will change at some point, so
one cannot
tell the MAC if one knows the IP...however, there are tools like wireshark
that can help you with MAC's.


How, if IP packets don't contain the source MAC?

--
Ron Johnson, Jr.
Jefferson LA  USA

If you don't agree with me, you are worse than Hitler!!!


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

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Ron Johnson


On 11/19/08 07:27, 中和刘 wrote:

On Wed, Nov 19, 2008 at 9:20 PM, Ron Johnson <[EMAIL PROTECTED]> wrote:

On 11/19/08 07:06, 中和刘 wrote:

when a user visit my website, it's easy to get the ip address of the
user, but i think IP address is not as stable as mac address, so I
hope I can get the mac address of the user according to its IP
address, is it possible? thanks

IP packets don't contain the MAC address.  You'd have to run some
asynchronous arp ping against the IP address.

i heard that arp ping only get the mac address on the LAN, it cannot
get mac address outside the LAN.


Hmmm.  Looks like you're right.


(Why do I get the feeling that some Chinese Government rule is behind this
request?)

no, I'm not a member of chinese government, I just want to provide
better service in my website :)


I was thinking more of government regulation.

--
Ron Johnson, Jr.
Jefferson LA  USA

If you don't agree with me, you are worse than Hitler!!!


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

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Raj Kiran Grandhi


中和刘 wrote:

On Wed, Nov 19, 2008 at 9:20 PM, Ron Johnson <[EMAIL PROTECTED]> wrote:

On 11/19/08 07:06, 中和刘 wrote:

when a user visit my website, it's easy to get the ip address of the
user, but i think IP address is not as stable as mac address, so I
hope I can get the mac address of the user according to its IP
address, is it possible? thanks

IP packets don't contain the MAC address.  You'd have to run some
asynchronous arp ping against the IP address.

i heard that arp ping only get the mac address on the LAN, it cannot
get mac address outside the LAN.

(Why do I get the feeling that some Chinese Government rule is behind this
request?)

no, I'm not a member of chinese government, I just want to provide
better service in my website :)


I guess most sites just use cookies for this purpose.




--
Ron Johnson, Jr.
Jefferson LA  USA

If you don't agree with me, you are worse than Hitler!!!


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









--

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: how to get the mac address(network card physical address) of a remote computer by its IP address?

On Wed, Nov 19, 2008 at 9:20 PM, Ron Johnson <[EMAIL PROTECTED]> wrote:
> On 11/19/08 07:06, 中和刘 wrote:
>>
>> when a user visit my website, it's easy to get the ip address of the
>> user, but i think IP address is not as stable as mac address, so I
>> hope I can get the mac address of the user according to its IP
>> address, is it possible? thanks
>
> IP packets don't contain the MAC address.  You'd have to run some
> asynchronous arp ping against the IP address.
i heard that arp ping only get the mac address on the LAN, it cannot
get mac address outside the LAN.
> (Why do I get the feeling that some Chinese Government rule is behind this
> request?)
no, I'm not a member of chinese government, I just want to provide
better service in my website :)

> --
> Ron Johnson, Jr.
> Jefferson LA  USA
>
> If you don't agree with me, you are worse than Hitler!!!
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject
> of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>



-- 
Welcome to visit my home page http://www.starliu.com
[It's only accessable when my pc is turned on, on which it's hosted.]

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008/11/19 Aioanei Rares <[EMAIL PROTECTED]>:
>
>
> On Wed, Nov 19, 2008 at 3:06 PM, 中和刘 <[EMAIL PROTECTED]> wrote:
>>
>> when a user visit my website, it's easy to get the ip address of the
>> user, but i think IP address is not as stable as mac address, so I
>> hope I can get the mac address of the user according to its IP
>> address, is it possible? thanks
>>
>> --
>> Welcome to visit my home page http://www.starliu.com
>> [It's only accessable when my pc is turned on, on which it's hosted.]
>>
>>
>> --
>> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>> with a subject of "unsubscribe". Trouble? Contact
>> [EMAIL PROTECTED]
>>
>
> Well, if the visitor uses DHCP, then his IP will change at some point, so
> one cannot
> tell the MAC if one knows the IP...however, there are tools like wireshark
> that can help you
> with MAC's.
>
thanks, i will try the tool


-- 
Welcome to visit my home page http://www.starliu.com
[It's only accessable when my pc is turned on, on which it's hosted.]

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Ron Johnson


On 11/19/08 07:06, 中和刘 wrote:

when a user visit my website, it's easy to get the ip address of the
user, but i think IP address is not as stable as mac address, so I
hope I can get the mac address of the user according to its IP
address, is it possible? thanks


IP packets don't contain the MAC address.  You'd have to run some 
asynchronous arp ping against the IP address.


(Why do I get the feeling that some Chinese Government rule is 
behind this request?)


--
Ron Johnson, Jr.
Jefferson LA  USA

If you don't agree with me, you are worse than Hitler!!!


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

Re: how to get the mac address(network card physical address) of a remote computer by its IP address?

2008-11-19 Thread Aioanei Rares

On Wed, Nov 19, 2008 at 3:06 PM, 中和刘 <[EMAIL PROTECTED]> wrote:

> when a user visit my website, it's easy to get the ip address of the
> user, but i think IP address is not as stable as mac address, so I
> hope I can get the mac address of the user according to its IP
> address, is it possible? thanks
>
> --
> Welcome to visit my home page http://www.starliu.com
> [It's only accessable when my pc is turned on, on which it's hosted.]
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
>
>
Well, if the visitor uses DHCP, then his IP will change at some point, so
one cannot
tell the MAC if one knows the IP...however, there are tools like wireshark
that can help you
with MAC's.

how to get the mac address(network card physical address) of a remote computer by its IP address?