If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have
a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for
FreeBSD on an OpenBSD mailinglist :-)
http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html
Something
[EMAIL PROTECTED] wrote:
FWIW this doesn't happen with my card:
fxp0: Intel InBusiness 10/100 Ethernet port 0x1000-0x103f mem 0xf400-0xf40
f,0xf410-0xf4100fff irq 10 at device 15.0 on pci0
fxp0: Ethernet address 00:90:27:d1:83:6a
fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a
http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html
Something better than that is probably needed in the long run.
Let me confirm it.
Does this also fix your problem on your freebsd-current?
Yes. I have only tried ping6, but that works, and IPv4 works.
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have
a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for
FreeBSD on an OpenBSD mailinglist :-)
http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html
Something better than that is
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have
a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for
FreeBSD on an OpenBSD mailinglist :-)
http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html
Something better than
On Sat, 29 Jan 2000, Mattias Pantzare wrote:
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have
a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for
FreeBSD on an OpenBSD mailinglist :-)
FWIW this doesn't happen with my card:
fxp0: Intel InBusiness 10/100 Ethernet port 0x1000-0x103f mem 0xf400-0xf40
f,0xf410-0xf4100fff irq 10 at device 15.0 on pci0
fxp0: Ethernet address 00:90:27:d1:83:6a
fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a
fxp0: starting DAD for
Yes, I am trying to repeat it in my environment.
(But it doesn't necessarily happens on all card which use fxp
driver. Also, seems to happen with some delicate timing...)
I heard that changing driver not to use interrupt is complete
fix, though I am not so good at driver issue.
More
On Sun, 30 Jan 2000 [EMAIL PROTECTED] wrote:
FWIW this doesn't happen with my card:
fxp0: Intel InBusiness 10/100 Ethernet port 0x1000-0x103f mem 0xf400-0xf40
f,0xf410-0xf4100fff irq 10 at device 15.0 on pci0
fxp0: Ethernet address 00:90:27:d1:83:6a
fxp0: supplying EUI64:
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have
a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for
FreeBSD on an OpenBSD mailinglist :-)
http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html
Something better than
10 matches
Mail list logo
