On Tue, 04 Jan 2005 09:27:34 -0700 (MST) "M. Warner Losh" <[EMAIL PROTECTED]>
wrote about Re: Strange networking problems after update 5.2.1->5.3:
MWL> : Please tell me which information you need.
MWL> You've likely already sent this before... But can y
In message: <[EMAIL PROTECTED]>
Gerrit Kühn <[EMAIL PROTECTED]> writes:
: On Tue, 04 Jan 2005 03:36:53 -0700 (MST) "M. Warner Losh" <[EMAIL PROTECTED]>
: wrote about Re: Strange networking problems after update 5.2.1->5.3:
:
:
: MWL> : I will do so
On Tue, 2005-Jan-04 10:17:01 +0100, Gerrit Kühn wrote:
>PJ> >ed0: flags=108843 mtu 1500
>PJ> > inet 130.75.117.37 netmask 0x broadcast 130.75.255.255
>PJ> > ether 01:d4:ff:03:00:20
>
>PJ> That's a multicast MAC address (the LSB of the first byte is 1). More
>
>Ok, I didn't know about thi
On Tue, 04 Jan 2005 03:36:53 -0700 (MST) "M. Warner Losh" <[EMAIL PROTECTED]>
wrote about Re: Strange networking problems after update 5.2.1->5.3:
MWL> : I will do so if it's the support for the cards that is broken.
MWL> However, I : have tried 4 different cards
In message: <[EMAIL PROTECTED]>
Gerrit Kühn <[EMAIL PROTECTED]> writes:
: I will do so if it's the support for the cards that is broken. However, I
: have tried 4 different cards now, and only one of them worked. So I'm
: tending to put the blame on the pcmcia bridge and it's driver.
B
In message: <[EMAIL PROTECTED]>
Gerrit Kühn <[EMAIL PROTECTED]> writes:
: Meanwhile I tried two further pcmcia cards which are 32bit (cardbus). Both
: (Xircom CBE2-100 and D-Link DFE-690-TXD) result in
:
: cbb0: CardBus card activation failed
:
: It seems it's rather the pcmcia bridg
In message: <[EMAIL PROTECTED]>
Robert Watson <[EMAIL PROTECTED]> writes:
: I've CC'd Warner Losh on the general principle that if it's a problem with
: a PCCARD ethernet adapter, he might be able to help (perhaps especially if
: it's possible to ship him one of the cards).
I think tha
On Tue, 4 Jan 2005 06:30:26 +1100 Peter Jeremy
<[EMAIL PROTECTED]> wrote about Re: Strange networking problems
after update 5.2.1->5.3:
PJ> >ed0: flags=108843 mtu 1500
PJ> > inet 130.75.117.37 netmask 0x broadcast 130.75.255.255
PJ> > ether 01:d4:ff:03:00
On Mon, 2005-Jan-03 15:58:26 +0100, Gerrit Kühn wrote:
>ed0: flags=108843 mtu 1500
> inet 130.75.117.37 netmask 0x broadcast 130.75.255.255
> ether 01:d4:ff:03:00:20
That's a multicast MAC address (the LSB of the first byte is 1). More
intelligent NICs will have an internal li
On Mon, 3 Jan 2005 13:19:13 + (GMT) Robert Watson <[EMAIL PROTECTED]>
wrote about Re: Strange networking problems after update 5.2.1->5.3:
RW> > arp things look ok, but I cannot ping the router, though I can ping
RW> > any other host (the same thing I already noticed
On Mon, 3 Jan 2005, Gerrit Kühn wrote:
> arp things look ok, but I cannot ping the router, though I can ping any
> other host (the same thing I already noticed here at work). But my
> router at home complains about this:
>
> arp: ether address is multicast for IP address 192.168.1.4!
Ah, now
>> I recently updated my old Compaq Armada 1500c from 5.2.1 to 5-stable. 5.2
>> worked fine, the update went without any noticable problem according to the
>> docs. 5.3 behaves well apart from a strange networking problem.
>> The notebook lives in a /16 subnet with a /16 netmask and has a 16bit
>>
On Thu, 30 Dec 2004, Gerrit Kühn wrote:
> I recently updated my old Compaq Armada 1500c from 5.2.1 to 5-stable. 5.2.1
> worked fine, the update went without any noticable problem according to the
> docs. 5.3 behaves well apart from a strange networking problem.
> The notebook lives in a /16 subnet
13 matches
Mail list logo
