Hello Folks,
I am working on extensions to Mobile IPv6 and faced with a strange situation. The current MIPv6 implementation
works fine but we would like to extend it to work with IPv4 endpoints.
This is the setup.
The CN (correspondent node) is a v4 only capable node. The AR's (Access Routers
On Fri, May 21, 2004 at 01:06:41PM -0500, Eric Anderson wrote:
> >
> > Disk design issues matter cause it is the ultimate
> >bottleneck. RAID is you friend.
> >
>
> Just curious - what RAID level/configuration do you use? I've typically
> used RAID5, but RAID0+1 might be acceptable.
>
Steve Shorter wrote:
Thanks - any help/hints is appreciated.
Disk design issues matter cause it is the ultimate
bottleneck. RAID is you friend.
Just curious - what RAID level/configuration do you use? I've typically
used RAID5, but RAID0+1 might be acceptable.
Eric
--
On Thu, May 20, 2004 at 10:44:14AM -0500, Eric Anderson wrote:
> >
>
> That's good to hear. Did you do any other tweaks? sysctl settings?
> mbufs?
net.inet.udp.recvspace=524288
kern.ipc.maxsockbuf=1048576
net.inet.icmp.drop_redirect=1
net.inet.icmp.log_redirect=1
Telus-nfs1:# w
12:41PM up
While on the subject of bge any idea why it performs so poorly in 100Mb mode
when compared to the humble fxp in the following results.
FreeBSD 5.1.2 (i386)
local: 22834.872368421 records per second
fxp 100Mb: 3854.06863517 records per second
bge 100Mb: 2501.66999862 records per second
bge 1Gb: 32
Our server has an twin-headed Intel Ether Express Gigabit ethernet
adaptor.
We've just upgraded the kernel to 5.2(RELEASE), and on reboot were
unable to connect to the machine. My colleague is currently battling to
repair the system over the phone to the tech up at telecity.
What has happen
On Fri, May 21, 2004 at 11:11:41PM +0900, George V.Neville-Neil wrote:
> >
> > While sweeping network interface drivers for incorrect usage of the
> > capabilities framework, I noticed some bugs in bge(4). Unfortunately,
> > I have no such card and I don't know its internals. Therefore I
> > mad
Hi folks,
While sweeping network interface drivers for incorrect usage of the
capabilities framework, I noticed some bugs in bge(4). Unfortunately,
I have no such card and I don't know its internals. Therefore I
made a patch fixing hw-independent bugs and marking some questionable
spots. It wou
On Thu, May 20, 2004 at 10:18:38AM -0700, Brooks Davis wrote:
>> This could be the first step towards teaching rc.conf about something like
>> network_interfaces_rename="hw-00:03:0d:08:dc:a7 sis0int"
> I don't really like the idea of adding magic values to the interface
> namespace that only work w
On Fri, 2004-05-21 at 13:16, Matthew Seaman wrote:
> However, remember that's written netbsd-centrically, and you'll have
> to adapt the instructions for use under FreeBSD -- use ports instead
> of pkgsrc, and you'll need to investigate what to do to make devfs(8)
> create the requited device node
> So I got set up with Vonage VoIP, which I am really excited to have, but
> I am having a heck of a time getting it set up behind my FreeBSD box.
>
> My network configuration is as follows:
> Cable modem --> FreeBSD 5.2.1-R (ipf/ipnat) --> 8-port D-Link Switch -->
> Internal network
>
> The Von
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] Behalf Of Muhammad Reza
> > I running named in sandbox as a secondary name server with
> > FreeBSD-5.1.p17,
> > Named log always complain:
> > named-xfer exited with signal 6 and slave zone expired for every
On Thu, May 20, 2004 at 10:18:38AM -0700, Brooks Davis wrote:
> On Thu, May 20, 2004 at 07:29:19PM +0300, Peter Pentchev wrote:
> > Hi,
> >
> > I found out recently that the Linux (or at least recent RedHat) startup
> > scripts could be configured to not bring up an Ethernet interface unless
> > i
13 matches
Mail list logo
