On Sat, Jul 26, 2003 at 02:22:05AM +0200, Clement Laforet wrote:
for incoming traffic, you must use -redirect_address, but for outgoing
you have to set -alias_address.
If you want to use a specific public IP to map incoming AND outgoing
packets, you need to run 2 natd, using ipfw matching.
the problem exits in 4.8-stable too.
On Fri, Jul 25, 2003 at 12:46:49PM -0400, Brian Reichert wrote:
I _do_ want to open a PR on this, but I'm uncertain if if I should
just claim it's an mplayer issue, or should I do more research to
track what the point of failure it 'really' is, or
On Fri, Jul 25, 2003 at 01:49:38PM -0400, Jim Durham wrote:
The procedure we used was to alias a 2nd public address to the outside
interface and use a redirect_address statement in natd.conf to
redirect connections to the new public IP to the inside machine.
Just a remark: If this 2nd
On Sat, 26 Jul 2003, Yar Tikhiy wrote:
Could you check if TELNET, HTTP, or SSH from the outside world to the
inside machine works? The problem may have to do with VNC protocol
peculiarities preventing it from working through NAT. (However, the VNC
FAQ claims VNC will work through NAT.)
VNC
How does one set the serial speed of the console.
I changed the boot loader speed to 57600 in make.conf
but the kernel seems to chose random speeds each time
it's booted.
Sometimes it's 9600 sometimes it 115200 other times
it's 38400.
Note this is on 5.x current
Russell Cattelan
On Fri, Jul 25, 2003 at 01:06:28PM -0500, Russell Cattelan wrote:
How does one set the serial speed of the console.
Does specifying BOOT_COMCONSOLE_SPEED=57600 not work?
BMS
___
[EMAIL PROTECTED] mailing list
Hi,
Bruce M Simpson wrote on Sat, Jul 26, 2003 at 10:06:36AM +0100:
On Fri, Jul 25, 2003 at 01:06:28PM -0500, Russell Cattelan wrote:
How does one set the serial speed of the console.
Does specifying BOOT_COMCONSOLE_SPEED=57600 not work?
No, I've experienced the same problem years ago.
The
On Sat, 26 Jul 2003, Daniel Lang wrote:
No, I've experienced the same problem years ago.
The funny thing is, that it worked on some machines,
while it didn't on others.
I worked around the problem by putting
machdep.conspeed=38400
in /etc/sysctl.conf, so the speed is reset to the right
On 25 Jul 2003 13:06:28 -0500, Russell Cattelan [EMAIL PROTECTED]
said:
How does one set the serial speed of the console.
I changed the boot loader speed to 57600 in make.conf
but the kernel seems to chose random speeds each time
it's booted.
Sometimes it's 9600 sometimes it 115200 other
I complained some time ago that my wi0 in my laptop would commonly
loose sync. It appears to be the other way around. With other access
points, it works flawlessly. With my home accesspoint ... provided by
a FreeBSD-4.8-STABLE machine, the loss of sync is as follows:
transferring from the ap
Diomidis Spinellis wrote:
I think I can package the proposed sh changes as a separate command,
following Luigi's suggestion. The syntax will not include a pipe symbol
and layout, but the performance benefits will still be there. It will
also be a lot more portable and also usable within any
On Saturday 26 July 2003 03:13 am, you wrote:
On Sat, Jul 26, 2003 at 02:22:05AM +0200, Clement Laforet wrote:
for incoming traffic, you must use -redirect_address, but for
outgoing you have to set -alias_address.
If you want to use a specific public IP to map incoming AND
outgoing
On Saturday 26 July 2003 03:42 am, Yar Tikhiy wrote:
On Fri, Jul 25, 2003 at 01:49:38PM -0400, Jim Durham wrote:
The procedure we used was to alias a 2nd public address to the
outside interface and use a redirect_address statement in
natd.conf to redirect connections to the new public IP to
On Saturday 26 July 2003 04:07 am, Wouter Clarie wrote:
On Sat, 26 Jul 2003, Yar Tikhiy wrote:
Could you check if TELNET, HTTP, or SSH from the outside world to
the inside machine works? The problem may have to do with VNC
protocol peculiarities preventing it from working through NAT.
I have become the owner of a Specialix I/O8+ PCI multiport serial card.
I originally thought that FreeBSD had a driver for that card, but it
turns out that the si(4) driver only supports the older SI/XIO and SX
cards. Fortunately, Linux has an I/O8+ driver and I'm in contact with
the author,
15 matches
Mail list logo
