Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-09 Thread Jason Andresen
Terry Lambert wrote: > > Leo Bicknell wrote: > > * Users wish to replace a card but have it use the same MAC > > address due to filters, static arp entries, caches that take too > > long to expire, bootp entries that are based on MAC address, etc. > > For years cards had the MAC in a separa

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Mike Meyer
Leo Bicknell <[EMAIL PROTECTED]> types: > On Thu, Nov 08, 2001 at 03:02:15PM -0600, Mike Meyer wrote: > > Could you provide a pointer to where you found it? An explanation of > > why users need to reprogram their MAC's - which is rather unusual - > > would help quite a bit. > There are several pos

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Terry Lambert
Leo Bicknell wrote: > > On Thu, Nov 08, 2001 at 02:50:44PM -0800, Terry Lambert wrote: > > FreeBSD needs some basic changes for multiple MAC s to be > > useful, though. > > I have more than once wished to assign a separate MAC to each > virtual IP address on an interface. I have no idea how com

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Leo Bicknell
On Thu, Nov 08, 2001 at 02:50:44PM -0800, Terry Lambert wrote: > FreeBSD needs some basic changes for multiple MAC s to be > useful, though. I have more than once wished to assign a separate MAC to each virtual IP address on an interface. I have no idea how complex that would be, but it would be

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Terry Lambert
Leo Bicknell wrote: > * Users wish to replace a card but have it use the same MAC > address due to filters, static arp entries, caches that take too > long to expire, bootp entries that are based on MAC address, etc. > For years cards had the MAC in a separate ROM to make this possible > w

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Terry Lambert
Wilko Bulte wrote: > > An explanation of > > why users need to reprogram their MAC's - which is rather unusual - > > would help quite a bit. > > Things like DECnet used to do it. And I think some server clustering > solutions might still do it. DECNet reprogrammed the MACs with the DEC ethernet

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Warner Losh
In message <[EMAIL PROTECTED]> Wilko Bulte writes: : Things like DECnet used to do it. And I think some server clustering : solutions might still do it. Some clustering solutions do do it to this day. They provide for completely trasnparent IP failover, and experience has shown that the easiest

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Leo Bicknell
On Thu, Nov 08, 2001 at 03:02:15PM -0600, Mike Meyer wrote: > Could you provide a pointer to where you found it? An explanation of > why users need to reprogram their MAC's - which is rather unusual - > would help quite a bit. There are several possibilities: * Users wish to replace a card but h

Re: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Wilko Bulte
On Thu, Nov 08, 2001 at 03:02:15PM -0600, Mike Meyer wrote: > [Context recovered from top posting.] > > Nicpon, John <[EMAIL PROTECTED]> types: > > > From: Mike Meyer [mailto:[EMAIL PROTECTED]] > > > Nicpon, John <[EMAIL PROTECTED]> types: > > > > I've been having the same problem listed below an

RE: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Nicpon, John
Meyer [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 08, 2001 3:02 PM To: Nicpon, John Cc: Jonathan Lemon; Kent Stewart; [EMAIL PROTECTED] Subject: RE: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard. [Context recovered from top posting.] Nicpon, John <[EMAIL PROTECTED]> types: &g

RE: SIS 900 Onboard NIC /w SIS 735 Chipset Motherboard.

2001-11-08 Thread Mike Meyer
[Context recovered from top posting.] Nicpon, John <[EMAIL PROTECTED]> types: > > From: Mike Meyer [mailto:[EMAIL PROTECTED]] > > Nicpon, John <[EMAIL PROTECTED]> types: > > > I've been having the same problem listed below and was wondering if > > > anyone had a fix? > > There wasn't a fix when I