Package: libmono-system2.0-cil
Version: 2.0.1-1

---------- Forwarded message ----------
From: Guy T. Rice <[EMAIL PROTECTED]>
Date: Fri, Nov 28, 2008 at 2:29 PM
Subject: Bad hardware address length
To: [EMAIL PROTECTED]


I tried switching to the Mono packages on "deb
http://debian.meebey.net/pkg-mono ./", but the libopenmetaverse
application I was trying to use would not connect after I switched, it
would just barf up "EXCEPTION: Bad hardware address length".
Switching back to the Mono packages in "testing" fixed the problem.
After a quick scanning of the source and a Google for similar issues,
I believe the problem is in ImplGetAllNetworkInterfaces in
System.Net.NetworkInformation/NetworkInterface.cs, and relates to how
the system handles interfaces for network "devices" that aren't
actually devices, e.g. teql0, although I don't know which interface on
my VPS is causing Mono to bomb, and being a VPS, I can't recompile the
kernel to disable any of these interfaces to see.  But in case it's
useful, here's the list (via "ifconfig -a"):

dummy0    Link encap:Ethernet  HWaddr 42:70:e6:ea:46:3a
         BROADCAST NOARP  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
         inet addr:xx.xx.xx.xxx  Bcast:xx.xx.xx.xxx  Mask:255.255.255.0
         inet6 addr: xxxx::xxxx:xxxx:xxxx:xxxx/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1187244 errors:0 dropped:0 overruns:0 frame:0
         TX packets:680473 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:236427175 (225.4 MiB)  TX bytes:81092749 (77.3 MiB)
         Interrupt:28

gre0      Link encap:UNSPEC  HWaddr
00-00-00-00-FF-00-65-74-00-00-00-00-00-00-00-00
         NOARP  MTU:1476  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ip6tnl0   Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
         NOARP  MTU:1460  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link 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:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sit0      Link encap:IPv6-in-IPv4
         NOARP  MTU:1480  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

teql0     Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
         NOARP  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

tunl0     Link encap:IPIP Tunnel  HWaddr
         NOARP  MTU:1480  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

========

Date: Sat, 29 Nov 2008 21:17:02 +0100
From: Mirco Bauer <[EMAIL PROTECTED]>

So sounds like that is a regression from 1.9.1 to 2.0.
Please file a bug report against debian and/or novell about this, so it
can be fixed.

-- 
Regards,

Mirco 'meebey' Bauer



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

Reply via email to