Re: Intel WiFi 5100/5300

2009-10-30 Thread Bernhard Schmidt 
On Sunday 25 October 2009 10:24:06 Bernhard Schmidt wrote:
> On Saturday 24 October 2009 21:41:39 Sam Fourman Jr. wrote:
> > Just wanted to make everyone aware that OpenBSD just 1 hour ago commited
> > a bunch of changes to their iwn driver. maybe some of it is useful for
> > FreeBSD as well?
> 
> Definitely, I'll look into that.

Another update:

* ICT interrupts for 5000/6000 series
* New firmware
* Initial support for 1000 series and initial bits for upcoming 6000  series 
(untested as hardware is not available to the general public)
* Many bug fixes, including workarounds for hardware bugs
* Addresses kern/140036

Most of this stuff has been obtained from OpeBSD. Testes/Feedback welcome!

http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn_merge_20081028.diff.bz2

-- 
Bernhard
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: bce(4) BCM5907 CTX write errors on 7.2 driver

2009-10-30 Thread Tom Judge 

Tom Judge wrote:

David Christensen wrote:
The next test is to diable the LOM's management firmware 

but boot to
an active network. 


After disabling the management firmware and doing 1 cold reboot and 3 
warms all worked correctly.


After re enabling the firmware and doing 1 cold reboot and 3 warms, the 
cold works correctly and the warms all failed.


Tom
Finally, the routine bce_print_adapter_info() in HEAD 

prints out both
the bootcode and management firmware versions.  If you can 

get those
same changes into your release I'd like to see the versions 

reported

on your system.


Here is the info from a boot of 8.0 RC2.

ASIC: 0x57092003
B/C: 5.0.6
Rev: C0
Bus: PCIe x4, 2.5Gb/s
Flags: MSI|MFW
MFW: NCS 2.0.3

And looking at this it seems dells update CD was not up to date 
enough and I only got 5.0.6 firmware not 5.0.9.


The package version and the bootcode version are similar but
they are not the same.  The bootcode you have (v5.0.6) is
sufficient to fix the problem.



Ok just checked in the life cycle manager and it has 5.0.9 installed my 
bad.


Running the other test now.


___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Hi. /31 on ethernet links

2009-10-30 Thread Sebastian Hyrwall 

Hi.


Is there any way to use /31's on ordinary ethernet links in 7.2? 
"ifconfig addr dest-addr" does not work either. It keeps setting the 
last ip as broadcast.



Sincerley,
Sebastian H
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Sebastian Hyrwall 

Chuck Swiger skrev:

On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote:
Is there any way to use /31's on ordinary ethernet links in 7.2? 
"ifconfig addr dest-addr" does not work either. It keeps setting the 
last ip as broadcast.


A /31 subnet is only defined for point-to-point network links, per:

  http://www.rfc-editor.org/rfc/rfc3021.txt

Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT.

Regards,
Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag on 
ethernet links? Or are you implying that it does not belong on ethernet 
links :)

Cause Cisco and Linux support /31 (ptp's) on ordinary ethernet links.

Sincerely,
Sebastian H
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Sebastian Hyrwall 

Freddie Cash skrev:
Reading the man page for ifconfig will show the "ptp" option for 
ifconfig, that configures the interface as a point-to-point 
interface..  :)




It will also show that it seems to be only for bridgeing,

# ifconfig  fxp0 ptp fxp0
ifconfig: unable to get bridge flags: Invalid argument




On Fri, Oct 30, 2009 at 5:22 PM, Sebastian Hyrwall > wrote:


Chuck Swiger skrev:

On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote:

Is there any way to use /31's on ordinary ethernet links
in 7.2? "ifconfig addr dest-addr" does not work either. It
keeps setting the last ip as broadcast.


A /31 subnet is only defined for point-to-point network links,
per:

 http://www.rfc-editor.org/rfc/rfc3021.txt

Ordinary ethernet links have BROADCAST flag set instead of
POINTOPOINT.

Regards,

Well how do I set the POINTOPOINT flag and remove the
BROADCAST-flag on ethernet links? Or are you implying that it does
not belong on ethernet links :)
Cause Cisco and Linux support /31 (ptp's) on ordinary ethernet links.

Sincerely,

Sebastian H
___
freebsd-net@freebsd.org  mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"




--
Freddie Cash
fjwc...@gmail.com 


___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Chuck Swiger 

On Oct 30, 2009, at 5:22 PM, Sebastian Hyrwall wrote:

A /31 subnet is only defined for point-to-point network links, per:

 http://www.rfc-editor.org/rfc/rfc3021.txt

Ordinary ethernet links have BROADCAST flag set instead of  
POINTOPOINT.




Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag  
on ethernet links? Or are you implying that it does not belong on  
ethernet links :)  Cause Cisco and Linux support /31 (ptp's) on  
ordinary ethernet links.


Ethernet point-to-point links are normally handled by ppp / pppd in  
PPPoE mode, but possibly something like:


  ifconfig en0 inet 192.1.1.10 inet 192.1.1.2

...would give you a POINTOPOINT link instead.  If not, you can  
probably fake things out by either using a /30 and wrapping the /31  
inside, or using  a /32 and an explicit default route via your  
ethernet interface.


Regards,
--
-Chuck

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Chuck Swiger 

On Oct 30, 2009, at 3:37 PM, Chuck Swiger wrote:

 ifconfig en0 inet 192.1.1.10 inet 192.1.1.2


Whoops-- copy-paste-typo; instead should be:

  ifconfig en0 inet 192.1.1.10 192.1.1.11

--
-Chuck

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Freddie Cash 
Reading the man page for ifconfig will show the "ptp" option for ifconfig,
that configures the interface as a point-to-point interface..  :)



On Fri, Oct 30, 2009 at 5:22 PM, Sebastian Hyrwall  wrote:

> Chuck Swiger skrev:
>
>> On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote:
>>
>>> Is there any way to use /31's on ordinary ethernet links in 7.2?
>>> "ifconfig addr dest-addr" does not work either. It keeps setting the last ip
>>> as broadcast.
>>>
>>
>> A /31 subnet is only defined for point-to-point network links, per:
>>
>>  http://www.rfc-editor.org/rfc/rfc3021.txt
>>
>> Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT.
>>
>> Regards,
>>
> Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag on
> ethernet links? Or are you implying that it does not belong on ethernet
> links :)
> Cause Cisco and Linux support /31 (ptp's) on ordinary ethernet links.
>
> Sincerely,
>
> Sebastian H
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>



-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Chuck Swiger 

On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote:
Is there any way to use /31's on ordinary ethernet links in 7.2?  
"ifconfig addr dest-addr" does not work either. It keeps setting the  
last ip as broadcast.


A /31 subnet is only defined for point-to-point network links, per:

  http://www.rfc-editor.org/rfc/rfc3021.txt

Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT.

Regards,
--
-Chuck

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Sebastian Hyrwall 

Chuck Swiger skrev:

On Oct 30, 2009, at 5:22 PM, Sebastian Hyrwall wrote:

A /31 subnet is only defined for point-to-point network links, per:

 http://www.rfc-editor.org/rfc/rfc3021.txt

Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT.



Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag 
on ethernet links? Or are you implying that it does not belong on 
ethernet links :)  Cause Cisco and Linux support /31 (ptp's) on 
ordinary ethernet links.


Ethernet point-to-point links are normally handled by ppp / pppd in 
PPPoE mode, but possibly something like:


  ifconfig en0 inet 192.1.1.10 inet 192.1.1.2

...would give you a POINTOPOINT link instead.  If not, you can 
probably fake things out by either using a /30 and wrapping the /31 
inside, or using  a /32 and an explicit default route via your 
ethernet interface.



Unfortunetly that doesn't work. It just sets 192.1.1.2 as broadcast.

Well wrapping a /31 inside of a /30 kinda defeats the purpose :)


If Cisco,Linux and NetBSD support it so should FreeBSD imho.


Regards,


___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

WPI panic (was: Can we turn off WPI_DEBUG)

2009-10-30 Thread Lawrence Stewart 

Doug Barton wrote:

I cc'ed those who seem to have put the most/recent effort into
sys/dev/wpi.

Is there any objection to turning off WPI_DEBUG by default? it creates
a lot of spam that the average user doesn't need. I use my 3945abg
every day and haven't had any problems with it for ages so I think
it's safe to say we're out of the period were debug by default is needed?


Doug, have you ever experienced the issue with your 3945 card that I 
reported here:


http://lists.freebsd.org/pipermail/freebsd-net/2009-October/023348.html

I'm guessing you haven't by your comment about lack of problems. Do you 
run with INVARIANTS in your kernel?


Cheers,
Lawrence
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: WPI panic

2009-10-30 Thread Doug Barton 
Lawrence Stewart wrote:
> Doug Barton wrote:
>> I cc'ed those who seem to have put the most/recent effort into
>> sys/dev/wpi.
>>
>> Is there any objection to turning off WPI_DEBUG by default? it creates
>> a lot of spam that the average user doesn't need. I use my 3945abg
>> every day and haven't had any problems with it for ages so I think
>> it's safe to say we're out of the period were debug by default is needed?
> 
> Doug, have you ever experienced the issue with your 3945 card that I
> reported here:
> 
> http://lists.freebsd.org/pipermail/freebsd-net/2009-October/023348.html
> 
> I'm guessing you haven't by your comment about lack of problems.

No, I have not had those problems at all. I routinely associate with
both WPA and WPA2 routers, as well as open routers at coffee shops and
such.

> Do you run with INVARIANTS in your kernel?

Yes, and up till recently I've been running with witness as well.


Wish I could be more help,

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Hi. /31 on ethernet links

2009-10-30 Thread Randy Bush 
/31 on point to point ether is exceedingly common in inter-router
topologies.

you may be amused to also read draft-kohno-ipv6-prefixlen-p2p-00.txt

randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"