> >
> > kernel: IN=eth0 OUT= MAC=00:50:da:05:c5:f4:00:04:dd:0b:e0:92:08:00
> > SRC=210.11.68.47 DST=204.144.132.162 LEN=56 TOS=0x00 PREC=0x00 TTL=238
ID=14090
> > PROTO=ICMP TYPE=3 CODE=3 [SRC=204.144.132.162 DST=210.11.68.47 LEN=121
TOS=0x00
> > PREC=0x00 TTL=248 ID=37692 DF PROTO=UDP SPT=53 DPT=
I was looking at the cpu use of my linux machine and noticed a strange
effect when running more than one process. I am having it encode wave files
ripped on another machine to mp3s for my music library.
This sample was taken while copying wave files from the other machine:
01:36:54 PM PID
I added a DWORD value named MTU to my Windows 2000 machine here, in the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interf
aces\{486B0CE0-AFB8-453C-AF22-1C2101E65970}
I set it to 1400, a number I just guessed. Looking at the cipe link I have
now shows an MTU of 1418,
This is likely to be a MTU problem on the Windows machine. There's a problem
in Windows in that it doesn't respond to requests to reduce MTU if the
target host is on the local subnet. Since you are using fake ips on the
local subnet, the Windows machine will be seeing a local connection and
always
At least you got a response to your report. "My" bug,
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=60930 still has no
response after almost three months. But I suppose they have other
priorities.
Andreas
- Original Message -
From: "Patrick Paul" <[EMAIL PROTECTED]>
To: <[EMAIL PR
Where should you configure iptables connection tracking modules to load? I
edit the iptables script now to insmod ip_conntrack_ftp and ip_nat_ftp but I
have to redo it when i upgrade iptables so it'd be better if I knew a config
file to use.
Andreas Hansson
- Original Message -
Fro
ld've been very annoying if I had bought a new
drive and then found it did the same thing as the old one because of the
cables.
Andreas
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 25, 2002 6:30 PM
Subject: Re: ide0 errors logged
I've started getting these errors logged in /var/log/messages:
Mar 22 22:08:33 linux kernel: hda: irq timeout: status=0xd0 { Busy }
Mar 22 22:08:33 linux kernel: ide0: reset: success
Is this a sign of my harddrive dying so i better replace it, or is it a
normal message from the kernel (redhat li
> A much better solution is that which is implemented by default in VMS -
lock
> the account for a random period of time - usually around 5 minutes - but
> don't lock it permanently. When the account is locked, accept all
passwords,
> even the correct one, and return a standard user authorization
I have a redhat 7.1 system. I'm trying to limit the number of login failures
to prevent brute-forcing passwords. To do this I changed
/etc/pam.d/system-auth to contain this:
authrequired /lib/security/pam_env.so
authrequired /lib/security/pam_tally.so no_magic_root
auth
Wouldn't it be possible to have this download from one of the mirrors
instead of directly from redhat? There's a mirror close to me that is
"never" too busy and that always gives a good speed download. I just haven't
seen any setting in up2date to download from mirrors instead of directly
from red
For each dnat line, add an accept line in forward:
$IPTABLES -A FORWARD -p tcp --dport 25 -m state --state NEW -d
192.168.0.1 -j ACCEPT
$IPTABLES -A FORWARD -p tcp --dport 80 -m state --state NEW -d
192.168.0.1 -j ACCEPT
$IPTABLES -A FORWARD -p tcp --dport 22 -m state --state NEW -d
192.168.0.1 -
The iptables firewall is not running on the same machine as the laptop,
correct? Then what you need to do on the firewall is just to allow udp's to
pass between laptop<->remote peer on the ports you specify in your cipe
options. What have you done to troubleshoot your problems? Try running
tcpdump
I'm running cipe with iptables. For my home setup it worked fine from the
rpm. At work, I had to download and compile the latest cipe. There was an
issue with packets not getting reprocessed by iptables after they were
encapsulated. Apparently some configurations work fine and some don't. More
inf
> > I'm running 7.1 on a P120. I currently have glibc-2.2.4-19. Any
suggestions
> > on how to fix this? How can I see what architecture the new package is
for?
>
> rpm -qp --qf "%{NAME}-%{VERSION}-%{RELEASE} %{ARCH}\n" *.rpm
OK, I used this and found that I currently have "glibc-2.2.4-19 i386"
i
unning 7.1 on a P120. I currently have glibc-2.2.4-19. Any suggestions
on how to fix this? How can I see what architecture the new package is for?
Andreas Hansson
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
> Anyway, all that corrected and it still gives me exactly the same error,
or
> warning as you will. Either way, it doesn't work.
>
> If you can think of anything else that I might have missed, I'd appreciate
> it.
Try checking the permissions of the files and directories. ssh doesn't like
if ~/.
> I'd recommend upgrading the rpm for iptables as this is one of the
> fixes. Current version is iptables-1.2.4-0 I believe.
Ah, up2date didn't update that automatically because of my manual fix. Now
I've forced it to apply the update. However, immediately after updating, i
tried "service iptable
> > i use in seawolf
> > # iptables-save > /etc/sysconfig/iptables
> > # chmod go-r /etc/sysconfig/iptables
> >
> > but this only save iptables command
>
> Ok, I take it this means that if I were to issue a series of iptables
commands at the prompt, then I could flush those rules that were loaded
19 matches
Mail list logo
