: [EMAIL PROTECTED]
Sent: Saturday, November 24, 2001 7:02 AM
Subject: Re: Networking: The Saga, The Sequel
At 01:49 AM 11/24/01 -0500, you wrote:
It's much easier to help someone who's actively trying to be helped,
rather than someone who simply asks for a magic answer.
Jason, you haven't been
Well said, I have been following your saga and it does seem like you are
doing everything you can to solve the problem. Don't give up, there are
nice people on this list. I think some have forgot what it is like to
have issues that they can't solve.
At 11/23/2001 04:59 PM -0800, you wrote:
Ben Ocean [EMAIL PROTECTED] writes:
Hoping not to add to the noise but it occured to me that I had told
Ben to Flush ipchains. Since I quite using ipchain or iptables months
ago, I had forgotten that depending on the rules you have, flushing
can leave
At 11/23/2001 01:15 PM -0800, you wrote:
At 04:56 PM 11/23/01 +, you wrote:
I still say this is wrong somehow; you can't have eth1 on the 216.9.0
network (note the 216), and have your gateway be 206.9.0.1. HOW IS THAT
POSSIBLE? (AFAIK, it isn't.)
Let's settle this issue once and for all.
At 11/23/2001 04:06 PM -0800, you wrote:
It says there's a folder called /etc/dhcpcd with a number of files in it.
I thought it was /etc/dhcpc (no d at the end...). See below, OK?
What does ifconfig show now?
eth1 Link endcap:Ethernet HWaddr 00:40:D0:0C:B2:22
inet addr:216.9.0.125
Rodolfo J. Paiz [EMAIL PROTECTED] writes:
Harry has made the mistake of assuming eth0 is your outside network, and
you have followed him into that mistake. It *should* work if you use
eth1 instead.
And that one mistake has added considerable confusion to this.
However my short in brief
At 11/23/2001 02:11 PM -0800, you wrote:
Rodolfo J. Paiz [EMAIL PROTECTED] writes:
Harry has made the mistake of assuming eth0 is your outside network, and
you have followed him into that mistake. It *should* work if you use
eth1 instead.
And that one mistake has added considerable
At 10:07 PM 11/23/01 +, you wrote:
At 11/23/2001 01:15 PM -0800, you wrote:
At 04:56 PM 11/23/01 +, you wrote:
I still say this is wrong somehow; you can't have eth1 on the 216.9.0
network (note the 216), and have your gateway be 206.9.0.1. HOW IS THAT
POSSIBLE? (AFAIK, it isn't.)
At 04:56 PM 11/23/01 +, you wrote:
I still say this is wrong somehow; you can't have eth1 on the 216.9.0
network (note the 216), and have your gateway be 206.9.0.1. HOW IS THAT
POSSIBLE? (AFAIK, it isn't.) Are you using pump or dhcpcd to get your IP
address for eth1? (Running ps auxw |
On Sat, Nov 24, 2001 at 09:29:41AM -0500, Dale Kosan wrote:
: Well said, I have been following your saga and it does seem like you are
: doing everything you can to solve the problem. Don't give up, there are
: nice people on this list. I think some have forgot what it is like to
: have issues
At 04:55 PM 11/24/01 +, you wrote:
At 11/24/2001 10:54 AM -0500, you wrote:
As many will attest, I've helped a lot of people out on this list.
I'll attest. Jason is a good guy.
I wrote him off-list and told him as much.
What's my problem with Ben's (many) requests for help? He never seems
Jason Costomiris [EMAIL PROTECTED] writes:
As many will attest, I've helped a lot of people out on this list. What's
my problem with Ben's (many) requests for help? He never seems to make
any progress, he doesn't seem to respond to requests for information
(like the 3 times I asked him to
Jason Costomiris [EMAIL PROTECTED] writes:
On Fri, Nov 23, 2001 at 03:14:47PM -0800, Harry Putnam wrote:
: Doesn't that street intersect I can't draw a picture Lane? Or is that
: one near Howtos? Bah. Road?
:
: `Networking is confusing regardless of man or howto Blvd'
:
: Which is
At 11/22/2001 11:20 AM -0800, you wrote:
I had somehow missed this response from Rodolfo Paiz.
Shame on you.
BTW, you need to remember that people answering don't always get everything
right. The most normal thing to do (don't know why) is to set eth0 to your
external network and eth1 to your
Happy Thanksgiving, everyone!
I had somehow missed this response from Rodolfo Paiz. I've also included
Harry Putman's comments and response at the bottom:
At 10:57 PM 11/20/01 +, you wrote:
I've probably spent a good 60 hours trying to figure this problem out to
date. I'm beginning to
On Tue 20 November 2001 22:21, you (James Francis) wrote:
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -s 192.168.1.2/24 -j MASQ
## I do have other IPchains installed...
Forgot to mention...make sure you have a rule like the following:
/sbin/ipchains -A forward -i eth1 -j
Ocean [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 20, 2001 1:24 PM
Subject: Networking: The Saga, The Sequel
Hello yet again;
First up, I_have_done_my_homework. I've probably spent a good 60 hours
trying to figure this problem out to date. I'm beginning to understand
At 11/21/2001 11:14 AM +0100, you wrote:
On Tue 20 November 2001 22:21, you (James Francis) wrote:
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -s 192.168.1.2/24 -j MASQ
## I do have other IPchains installed...
Forgot to mention...make sure you have a rule like the
At 11/21/2001 02:32 AM -0800, you wrote:
Answering the three respondents who haven't given up on me as a hopeless
case...
Hey, you haven't answered *my* questions yet.
Hmmm... Before I attempt this, it seems to me that if your gateway is
192.168.0.2, then I need to either change my NETWORK in
Ben Ocean [EMAIL PROTECTED] writes:
Harry Putnam writes, in essence:
Let's see your netstat -nr:
Destination Gateway Genmask Flags MSS Window irttIface
192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
216.9.0.0 0.0.0.0 255.255.255.0 U 40 0
Hello yet again;
First up, I_have_done_my_homework. I've probably spent a good 60 hours
trying to figure this problem out to date. I'm beginning to understand the
lingo now. Hopefully, with your help, I can get it right this time.
Secondly, I have gone through all of the old posts to try and
-Original Message-
From: Ben Ocean [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 3:25 PM
To: [EMAIL PROTECTED]
Subject: Networking: The Saga, The Sequel
Hello yet again;
Hello...
OUTLINING THE PROBLEM
I am currently able to ping from the Doze box to the RH
Ben,
CONFIGURING MASQUERADING
vi /etc/rc.d/rc.masq
/sbin/depmod -a
/sbin/modprobe ip_masq_ftp
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -s 192.168.1.2/24 -j MASQ
## I do have other IPchains installed...
Forgot to mention...make sure you have a rule like the following:
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 20, 2001 1:24 PM
Subject: Networking: The Saga, The Sequel
Hello yet again;
First up, I_have_done_my_homework. I've probably spent a good 60 hours
trying to figure this problem out to date. I'm beginning to understand the
lingo now. Hopefully
James Francis [EMAIL PROTECTED] writes:
Ben,
CONFIGURING MASQUERADING
vi /etc/rc.d/rc.masq
/sbin/depmod -a
/sbin/modprobe ip_masq_ftp
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -s 192.168.1.2/24 -j MASQ
## I do have other IPchains installed...
Forgot to
On Tue, Nov 20, 2001 at 04:05:13PM -0500, James Francis wrote:
From: Ben Ocean [mailto:[EMAIL PROTECTED]]
vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
BROADCAST=192.168.1.255
IPADDR=192.168.1.1
NETMASK=255.255.225.0
NETWORK=192.168.1.0
At 11/20/2001 12:24 PM -0800, you wrote:
First up, I_have_done_my_homework.
Clearly... grin
I've probably spent a good 60 hours trying to figure this problem out to
date. I'm beginning to understand the lingo now. Hopefully, with your
help, I can get it right this time.
Fear not, solutions
27 matches
Mail list logo
