-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having a problem with slow transfers to my FreeBSD 4.7-RELEASE box
using a D-Link 528CT
(Realtek 8029 chipset). When I try to upload files to this machine from a
windowsXP box, I only
get about 30KB/s on the 10BaseT cat 5 network. This identical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was transferring a huge file (700 MB) to an nfs mounted disc and I
umount -f the nfs mounted directory. After this I lost control of that pc
(I was remotely administering it). The machine responds to pings and
forwards packets as well, but if I try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 10 Jan 2003, Rob wrote:
Sorry for this OT but I am trying for some hours to achieve a massive
rename of files using a simple script and I have not success yet. I want
to rename files like
RESULTS OF JAN 01 2002.txt
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What is the best way to resolve these?
ad0s1e: UDMA ICRC error reading fsbn 897759 of 144-159 (ad0s1 bn 897759;
cn 55 tn 225 sn 9) retrying
ad0s1a: UDMA ICRC error reading fsbn 45439 of 22688-22719 (ad0s1 bn
45439;
cn 2 tn 211 sn 16) retrying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a question about FFS filesystem.
According to a paper about the design of UFS filesystem[1], if you create
the FFS filesystem on a slow cpu and then move it to a fast cpu with a
fast controller, theh the FFS wont perform efficient.
This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SORT: Stetefull IPFW rules combined in a router that is
a ypclient may make the box loose connectivity and a
irreleavent error too many dynamic rules appear in the log
eventhough only 20 dynamic rules may exist.
LONG:
I am reporting a strange
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nelis wrote
...
inside machines cannot telnet...
#allow all outbound and only inbound TCP connections I've created
add 0301 divert natd all from any to any via rl0
add 00302 check-state
add 00303 allow tcp from any to any established
add 00304
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ipfw add 108 allow tcp from any to xx.250.227.0/22 20,21,25,80,110 via
bge0
snip
#Outbound from inside
ipfw add 109 check-state
ipfw add 110 allow tcp from xx.250.224.0/22 via bge0 keep-state
ipfw add 111 allow udp from xx.250.224.0/22 via bge0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(I sent this email to freebsd-security but it never appeared on the
list, nor it returned back-very strange for freebsd-security;does freebsd
security has any problem?)
I have a small question. When I was administering one freebsd box the
Dear,
Please help me with this strange situation, that is due to using boot0cfg
with wrong switches. I googled it but I did not find any similar case.
On a working 4.11 freebsd system I wanted to create a floppy bootable
disk.
This system had one slice and four labels.
I run this command:
Hi,
I managed to fix the error of all slices being destroyed. My system is up
and running. i did not reinstall any programs, just edited the partition
table and the labels. It took me 3 days to figure out the exact values, so
I post here my findings, in case somebody faces the same problem.
hi,
For the past weeks I have been receiving in my syslog the following
message
ikaros /kernel: unknown dynamic rule type 244
ikaros last message repeated XXX times
ipfw -d show | grep 244
does not show anything
I have rebooted the machine,
I have flushed reloaded the ruleset...the message
Summary: NATD translates source addresses even though it should not because
unregistered_only is set and the IPs do not belong to RFC 1918 (like
192.168)
Hi List,
I have a very strange problem in my
FreeBSD bigb3 6.1-STABLE FreeBSD 6.1-STABLE #0: Tue Jun 6
I am using the
On Fri, 7 Jul 2006, Chuck Swiger wrote:
BigBrother-{BigB3} wrote:
[ ... ]
I have trouble making a passive ftp connection to work, because every time
natd changed source port even though it should not. Sometimes it changes
within the IP_PORTRANGE_DEFAULT but sometimes it changes
14 matches
Mail list logo