I'm having intermittent issues with my implementation of Dummynet.
I've got two FreeBSD 7.0 systems running an IPSec/Racoon VPN which runs stably. On one BSD box, I've set up a dummynet pipe to limit the amount of traffic going across my gif tunnel.
ipfw pipe 1 config bw 300Kbit/s queue 80Kbytes
ipfw add pipe 1 all from any to any via gif0
I have a client who is looking for a Sr Kernel engineer with 3+ years of coding exp with Freebsd,IP stack and MIPS...
Please let me know if you know anyone who would be interested.
Tony 408-345-9100 ext 103 firstname.lastname@example.org
I've got a FreeBSD setup running with three IPSec tunnels (these were created following the official FreeBSD documentation).
The three links have been running fine for many months now, however, I'm regularly getting entries in my /var/log/messages file stating "kernel: esp_input: packet replay check for SA(SPI= src= dst=)".
on my freebsd server, bind keep dieing.
i looked in the messages log and i see:
Limiting icmp unreach response from 224 to 200 packets per second
Limiting icmp unreach response from 246 to 200 packets per second
Limiting icmp unreach response from 226 to 200 packets per second
Limiting icmp unreach response from 253 to 200 packets per second
we have two gateways (GW-A(linux2.6.18)),GW-B(linux 2.6.18)) and one router(R(freeBSD mechine)) in between them.
IPSEC Policies at both the gateways:
GW-A(ESP)( Inbount :A<-B, Outbound:A->R(router) )
I am running UDP server at GW-B,UDP client at GW-A and sending UDP packets with Router Extension header from GW-A->R->GW-B.
I have installed FreeBSD 6.2 amd64 on my Athlon 643500+ pc. Everything is OK when working in GDE or KDE unless when I scroll with my USB mouse or even with my USB keyboard in filesystem window or for example when viewing a PDF file, which the kernel panics. Every thing(menu, clock, running applications)is freezed but mouse pointer is still active. Reboot is inevitable, though.
Hi, I posted on here a long time ago, for INSTALL7. Since then my team and I have been working on redesigning the project. We also renamed it to EasyBSD... The primary function of this project is to assist newer FreeBSD users in setting up freebsd, updating src,ports,doc tree, installing common apps, upgrading installed packages/ports, and to configure and tweak the system.
A bit of an odd situation. I recently purchased $99/mth dedicated hardware from Cedant. It is running FreeBSD 6.1. The system seems to have no root user, and no way to access it. All of the following fail:
"su" - FAILS (sorry)
"sudo" - FAILS (command not found)
"passwd root" - FAILS (passwd: permission denied)
I'm considering making changes to a private version of FreeBSD that builds a single kernel with support for both PAE capable processors as well as those that don't have PAE support. (If you don't know what PAE means, it's OK; it just means you can safely ignore this post :-)
I'm wondering if anybody has any thoughts on this subject. Yes, I've thought deeply about the implications of the many constants wose values are derived from Page Directory Indexes (i.e., see the definition of the VADDR() macro and the variables defined in terms of it).
The new Zettabyte File systems (ZFS), has been a part with Solaris 10 and OpenSolaris Operating Systems. As the name suggests, the filesystems offers immense scalability apart from a bunch of other features.
Pawel Jakub Dawidek announced the support for this filesystem in FreeBSD 7.0-RELEASE, as an experimental feature. Apart from some missing features like ACLs, and booting off ZFS, the filesystem is fully functional with this FreeBSD release.