Francisco Castillo wrote:
> Then i do a apt-get install kernel-image-2.18.14-686, and this
> installations works fine. Then it puts me a entry on the lilo in
> order to load the new kernel (the old kernel is a 2.2 original woody,
> it has a 686 ) but the problem for me now is that when i reboot the
Francisco Castillo wrote:
> Then i do a apt-get install kernel-image-2.18.14-686, and this
> installations works fine. Then it puts me a entry on the lilo in
> order to load the new kernel (the old kernel is a 2.2 original woody,
> it has a 686 ) but the problem for me now is that when i reboot the
procedure to setup this configuration?
Thanks in advance.
Francisco.
- Original Message -
From: "Kris Deugau" <[EMAIL PROTECTED]>
To:
Sent: Friday, July 02, 2004 10:55 PM
Subject: Re: nat ipchains on debian woody
Francisco Castillo wrote:
> But my problem now i
procedure to setup this configuration?
Thanks in advance.
Francisco.
- Original Message -
From: "Kris Deugau" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 02, 2004 10:55 PM
Subject: Re: nat ipchains on debian woody
Francisco Castillo wrote:
&
Francisco Castillo wrote:
> But my problem now is another different. When I installed my woody i
> put a floppy disk bootting system in order to load my debian woody
> kernel (this is a large history because i have 2 hard disk on this
> machine and I cant start debian in a classic lilo)
Why not?
Francisco Castillo wrote:
> But my problem now is another different. When I installed my woody i
> put a floppy disk bootting system in order to load my debian woody
> kernel (this is a large history because i have 2 hard disk on this
> machine and I cant start debian in a classic lilo)
Why not?
ernel) to load a new kernel which have been installed on /boot/"kernel 2.4
" ?
Thanks for your previous numerous interested response.
Francisco.
- Original Message -
From: "Kris Deugau" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, June 29, 2004 5:30 PM
Subject
ernel) to load a new kernel which have been installed on /boot/"kernel 2.4
" ?
Thanks for your previous numerous interested response.
Francisco.
- Original Message -
From: "Kris Deugau" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June
Francisco Castillo wrote:
> I'm novice on debian, i have decided recently to change from redhat
> or mandrake (fatal experiencie in two years), so excuse my ignorance.
Having recently gone through a similar change, I may be able to help a
little more.
> First i dont know how to do this step "The
Francisco Castillo wrote:
> I'm novice on debian, i have decided recently to change from redhat
> or mandrake (fatal experiencie in two years), so excuse my ignorance.
Having recently gone through a similar change, I may be able to help a
little more.
> First i dont know how to do this step "The
Hola Francisco
Francisco Castillo wrote:
Enrique,
IÂm novice on debian, i have decided recently to change from redhat or
mandrake (fatal experiencie in two years), so excuse my ignorance.
First i dont know how to do this step "The first thinng you must do is to
install a kernel with IPTABLES suppor
Hola Francisco
Francisco Castillo wrote:
Enrique,
IÂm novice on debian, i have decided recently to change from redhat or
mandrake (fatal experiencie in two years), so excuse my ignorance.
First i dont know how to do this step "The first thinng you must do is to
install a kernel with IPTABLES suppor
Christoph,
You are right. Looks like he should also modprobe or insmod iptables
and many other modules. I insmod a whole list of routing modules:
ipt_REDIRECT
ipt_MASQUERADE
iptable_mangle
iptable_nat
ipt_REJECT
iptable_filter
ay, June 28, 2004 10:09 PM
Subject: Re: nat ipchains on debian woody
On Mon, 28 Jun 2004 21:35:40 +0200
Christoph LÃffler <[EMAIL PROTECTED]> wrote:
Hello Fraancisco:
The first thinng you must do is to install a kernel with IPTABLES support,
the ipchains is not recomendable for kernels up to 2
On Mon, 28 Jun 2004 21:35:40 +0200
Christoph Löffler <[EMAIL PROTECTED]> wrote:
Hello Fraancisco:
The first thinng you must do is to install a kernel with IPTABLES support, the
ipchains is not recomendable for kernels up to 2.4. The kernel packages of
woody distro have this support
Next you MUST
To: "Francisco Castillo" <[EMAIL PROTECTED]>;
Sent: Monday, June 28, 2004 9:16 PM
Subject: Re: nat ipchains on debian woody
Have you tried iptables instead? If your kernel supports iptables,
then:
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4
Hello Francisco,
Francisco Castillo wrote:
I have read doc to do it but when i apply this doc i have a "your
kernel seems to not support ipchains" messages when i try to do
this.
For what reason do you want to use ipchains? If you just set up
debian successfully i think you have also an actual ker
Hello Francisco,
Francisco Castillo wrote:
I have read doc to do it but when i apply this doc i have a "your
kernel seems to not support ipchains" messages when i try to do
this.
For what reason do you want to use ipchains? If you just set up
debian successfully i think you have also an actual ke
Have you tried iptables instead? If your kernel supports iptables,
then:
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/$both_eth_devs/rp_filter
iptables -t nat -I POSTROUTING -s 192.168.0.0/24 -i eth1 -o eth0 -j
MASQUERADE
iptables also does the firewalling in other ch
Christoph,
You are right. Looks like he should also modprobe or insmod iptables
and many other modules. I insmod a whole list of routing modules:
ipt_REDIRECT
ipt_MASQUERADE
iptable_mangle
iptable_nat
ipt_REJECT
iptable_filter
ROTECTED]>
Sent: Monday, June 28, 2004 10:09 PM
Subject: Re: nat ipchains on debian woody
On Mon, 28 Jun 2004 21:35:40 +0200
Christoph LÃffler <[EMAIL PROTECTED]> wrote:
Hello Fraancisco:
The first thinng you must do is to install a kernel with IPTABLES support,
the ipchains is not recomend
On Mon, 28 Jun 2004 21:35:40 +0200
Christoph Löffler <[EMAIL PROTECTED]> wrote:
Hello Fraancisco:
The first thinng you must do is to install a kernel with IPTABLES support, the
ipchains is not recomendable for kernels up to 2.4. The kernel packages of woody
distro have this support
Next you MUST
To: "Francisco Castillo" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, June 28, 2004 9:16 PM
Subject: Re: nat ipchains on debian woody
Have you tried iptables instead? If your kernel supports iptables,
then:
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 &g
Hello Francisco,
Francisco Castillo wrote:
I have read doc to do it but when i apply this doc i have a "your
kernel seems to not support ipchains" messages when i try to do
this.
For what reason do you want to use ipchains? If you just set up
debian successfully i think you have also an actual ker
Hello Francisco,
Francisco Castillo wrote:
I have read doc to do it but when i apply this doc i have a "your
kernel seems to not support ipchains" messages when i try to do
this.
For what reason do you want to use ipchains? If you just set up
debian successfully i think you have also an actual ke
Have you tried iptables instead? If your kernel supports iptables,
then:
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/$both_eth_devs/rp_filter
iptables -t nat -I POSTROUTING -s 192.168.0.0/24 -i eth1 -o eth0 -j
MASQUERADE
iptables also does the firewalling in other ch
On Mon, Feb 12, 2001 at 08:31:42AM +0100, Tobias Geijersson wrote:
> My firewall have these NICs:
>
> eth0 192.168.2.254/24 is connected to my IP-provider using private ip
> eth1 a.x.y.z1/27 is connected to my server segment using "real" ip
> eth2 a.x.y.z2/27 is connected to my workstation segment
Tobias Geijersson <[EMAIL PROTECTED]> writes:
> The problem is that when I add the rule for masqurading it translates
> all 192.168.10.1/24 to eth0's 192.168.2.254 before routed to my ip
> provider, and that adress is a private one and will not work!
>
> How do I solve this in kernel 2.2?
I'm no
On Mon, Feb 12, 2001 at 08:31:42AM +0100, Tobias Geijersson wrote:
> My firewall have these NICs:
>
> eth0 192.168.2.254/24 is connected to my IP-provider using private ip
> eth1 a.x.y.z1/27 is connected to my server segment using "real" ip
> eth2 a.x.y.z2/27 is connected to my workstation segmen
Tobias Geijersson <[EMAIL PROTECTED]> writes:
> The problem is that when I add the rule for masqurading it translates
> all 192.168.10.1/24 to eth0's 192.168.2.254 before routed to my ip
> provider, and that adress is a private one and will not work!
>
> How do I solve this in kernel 2.2?
I'm n
secure.
Matthew Sherborne
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Florian Kunkel
> Sent: Wednesday, 11 October 2000 10:20 p.m.
> To: [EMAIL PROTECTED]
> Subject: Re: nat
>
>
> Matthew Sherborne wrote:
> > issued m
Matthew Sherborne wrote:
> issued mail clients that support CRAM-MD5 authentication to everyone and
... wich mail client do you use than ?
do you know of any others supporting CRAM-MD5 auth ?
where can I read more on CRAM-MD5 auth ?
tia
Florian!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
On Sat, 07 Oct 2000, Nathan wrote:
>It's a pain in the ass to maintain an ability to track users sending spam
>from your dialups and through your server if you don't have each user
>authenticate and the connections all apear to hit the mail server from the
>firewall.
>
>That's what vetoed ours for
On Fri, 6 Oct 2000, Kevin wrote:
>
> I was wondering if anyone can tell me sort of problems I would have
> if I assigned internal ips to our customers and used ipmasq.
> Basically I don't want to do this, but I need some sort of firepower
> to persuade my boss that he doesn't want it eithe
> Even for the "standard" protocols it fails if you need to connect to a
> port not handled by the module. Example: the ip_masq_irc watches only
fails? since when? it works perfectly.
> something, not everything (here: DCC) will work.
dah??
DCC works like a charm, where did you get an idea it d
> if I assigned internal ips to our customers and used ipmasq.
tcp/ip was designed based on idea that one ip means one network
interface, various problems arises with introduction of NAT
- things like gnutella and napster don't work very well from behind NAT,
there are problems with x-clie
On Fri, 6 Oct 2000, Kevin wrote:
>
> I was wondering if anyone can tell me sort of problems I would have
> if I assigned internal ips to our customers and used ipmasq.
> Basically I don't want to do this, but I need some sort of firepower
> to persuade my boss that he doesn't want it eit
On Fri, Oct 06, 2000 at 04:59:39PM -0700, Kevin wrote:
> I was wondering if anyone can tell me sort of problems I would have
> if I assigned internal ips to our customers and used ipmasq.
Merely thinking about it says 'no' ..
Since there might be protocols using IPs within themselves that ar
It's a pain in the ass to maintain an ability to track users sending spam
from your dialups and through your server if you don't have each user
authenticate and the connections all apear to hit the mail server from the
firewall.
That's what vetoed ours for a long time.
Then we just got a few mor
On Fri, 6 Oct 2000, Kevin wrote:
> I was wondering if anyone can tell me sort of problems I would have
> if I assigned internal ips to our customers and used ipmasq.
> Basically I don't want to do this, but I need some sort of firepower
> to persuade my boss that he doesn't want it either.
40 matches
Mail list logo
