Another bsnmpd module, in case anyone's interested: bsnmp-ping is an
SNMP module which allows you to measure latency and reachability to
hosts of your choice.
More info:
http://memberwebs.com/nielsen/software/bsnmp-ping/
Cheers,
Nate
___
freebsd-net@fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harti Brandt wrote:
> On Fri, 7 Apr 2006, Nate Nielsen wrote:
> NN> * bsnmp-host module (RFC 2790 ie: uptime, cpu load, memory, disks)
>
> Is that different from the hostres module we have in the tree?
The very same... Oh we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bjoern A. Zeeb wrote:
> On Thu, 6 Apr 2006, Nate Nielsen wrote:
>
>> A thousand apologies if announcing this here is inappropriate, but since
>> it's related to FreeBSD's very own bsnmpd...
>>
>> bsnmp-re
A thousand apologies if announcing this here is inappropriate, but since
it's related to FreeBSD's very own bsnmpd...
bsnmp-regex is an SNMP module that allows one to create arbitrary
counters from logs, program output or other text.
If you're interested:
http://memberwebs.com/nielsen/software/bs
Bjoern A. Zeeb wrote:
> On Mon, 3 Apr 2006, Nate Nielsen wrote:
>
> Hi,
>
>> I've been experiencing a panic in ipsec_process_done. Below is a
>> backtrace and a patch which supresses the issue. I don't profess to
>> understand the IPSec code completely...
I've been experiencing a panic in ipsec_process_done. Below is a
backtrace and a patch which supresses the issue. I don't profess to
understand the IPSec code completely...
The panic occurs when performing IKE negotiations (racoon) with multiple
systems at the same time. The panicing boxes are rou
Eric W. Bates wrote:
> I'm running pfsense (an embedded FreeBSD 6.1) on a wrap2C. I recently
> added a Soekris vpn1411 and am now getting infrequent errors:
>
> hifn0: rndtest: ones interval 4 failed (382, 251-373)
> hifn0: rndtest: ones interval 1 failed (2663, 2343-2657)
> hifn0: rndtest: zeros
Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Nate Nielsen writes:
>
>>Thanks, that helps. It works nicely with a uhci USB controller.
>>
>>However when the ohci driver is in use, we crash somewhere in
>>usb_transfer_complete. I'll look into this fu
Sam Leffler wrote:
> I see no statistics; are you sure you are not being pounded by phy
> errors.
I've put together a small patch to the ath driver which exposes some
interupt statistic sysctls, and a small shell script to read these and
list them once per second. Both are attached.
Here are the
Sam Leffler wrote:
> Nate Nielsen wrote:
>> Adding polling to this driver does increase performance on embedded
>> systems. With my current patch (on a 233Mhz system), the throughput (in
>> this case a simple TCP stream) goes up by ~6Mbits, from 18Mbits to
>> 24Mbits.
&g
Sam Leffler wrote:
> You might try explaining why you think polling helps your performance.
> Unless you've significantly restructured the interrupt handling in the
> driver most work is deferred to a non-interrupt context.
Yes, I saw that. However the interrupts themselves when they are fired
a
I've been working on polling for the FreeBSD ath wireless driver.
On slow CPU's polling helps prevent (by supressing certain interrupts)
livelock and increases throughput. This is true of Atheros cards on
Soekris and other embedded hardware.
Just thought I'd post something here in case anyone is
Tiago Cruz wrote:
> On Mon, 2006-01-23 at 20:49 +0000, Nate Nielsen wrote:
>
>
>>I'd use tcpdump on the various interfaces (tap devices, ethernet) on the
>>machines in question to see exactly at which host is not forwarding the
>>packets properly and where
Tiago Cruz wrote:
> If I install the VPN in my gateway (192.168.0.1), the laptop client host
> (Windows XP) is able to ping my virtual server (10.8.0.1), my gateway
> (192.168.0.1) and all my LAN (192.168.0.0/22).
>
> If I install the VPN in my gateway backup (192.168.0.253, with CARP),
> the lapt
I encountered a strange problem with PMTU discovery not working properly
on various machines when the packets were tunneled over a GIF / IPSEC
Transport type tunnel (both ends running FreeBSD 6.0). Configuration
files attached.
Various older FreeBSD systems (it seemed systems that had jails runnin
Brian Candler wrote:
> The IPSEC documentation at
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html is
> pretty weird. It suggests that you encapsulate your packets in IP-IP (gif)
> encapsulation and THEN encapsulate that again using IPSEC tunnel mode.
> This is a really str
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sam Leffler wrote:
> Seems to work fine here with CURRENT; I just typed the exact commands
> from above. "hardware errors" are typically dma errors. If you're
> operating in adhoc mode the h/w is periodically sending beacons and if
> that tx descript
Certain multicast packets are not making it through an Atheros based
802.11 wireless link. Other drivers/cards (ie: wi) work fine.
Two boxes sitting next to each other running FreeBSD 6.0. The cards are
set up simply:
ifconfig ath0 inet 172.28.2.18/30 ssid tel2 channel 52 \
mediaopt adhoc
I have Atheros 5213 based 802.11a cards. When switching 'media' (ie:
rates or speed) I often get the following error multiple times on my
console:
> ath0: hardware error; resetting
> ath0: hardware error; resetting
It's all fine and good when it's just a few times, but in many cases it
enters an
Sam Leffler wrote:
> adhoc mode is not intended for bridging; I'm a bit surprised it works at
> all (I've never tried it).
Perhaps not in the atheros driver, or net80211 subsystem.
But general it does make sense. I'm setting up several point to point
links with relays. The plan is that these re
Has anyone else seen a problem where bridging an Atheros wireless with
an ethernet interface has painfully slow throughput?
I have two boxes sitting next to each other both running FreeBSD 6.0.
BOX 1 BOX 2
A +++ B/C -
Two Atheros (5213) 802.11a cards (A and B above)
Has anyone else seen a problem where bridging an Atheros wireless with
an ethernet interface has painfully slow throughput?
I have two boxes sitting next to each other both running FreeBSD 6.0.
BOX 1 BOX 2
A +++ B/C -
Two Atheros (5213) 802.11a cards (A and B above)
Sam Leffler wrote:
> I believe the attached change plugs the leak.
I gave it a shot, and the problem is still there. I've checked to make
sure this is in fact the right kernel:
> # strings /boot/kernel/kernel | grep ieee80211_init_neighbor
> ieee80211_init_neighbor
Is there further information
Sam Leffler wrote:
> Nate Nielsen wrote:
>> I've put debugging code in node_alloc() and node_free() (in
>> net80211/ieee80211_node.c) and can confirm that thousands of
>> ieee80211_node structures are being allocated, at a cost of 1K a piece.
>>
>> I'll
Nate Nielsen wrote:
> I'm experiencing a memory leak in the net80211 code. I have two atheros
> 5213-A cards on two embedded systems running FreeBSD 6.0. They are setup
> as IBSS (adhoc) stations. After roughly 15 seconds of ~14Mbps TCP
> traffic (single stream) I promptly
I'm experiencing a memory leak in the net80211 code. I have two atheros
5213-A cards on two embedded systems running FreeBSD 6.0. They are setup
as IBSS (adhoc) stations. After roughly 15 seconds of ~14Mbps TCP
traffic (single stream) I promptly run out of memory:
> login: panic: kmem_malloc(4096)
No. I think each instance of natd (at least last time I looked at it)
could only use one IP address as it's public address.
Cheers,
Nate
Daniel Dias Gonçalves wrote:
> Exists the possibility to make NAT POOL with IPFW + NATD ?
>
___
freebsd-net@freebs
27 matches
Mail list logo
