At 11/23/2001 01:15 PM -0800, you wrote:
>At 04:56 PM 11/23/01 +0000, 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.
>>Are you using pump or dhcpcd to get your IP address for eth1? (Running
>>"ps auxw | grep dhcpcd" should tell you whether dhcpcd is running;
>>similar thing for pump.)
>
>Both are running, but pump specifically references eth1.
Only one should be running. I believe (someone may correct me) that dhcpcd
is the preferred choice. We should only have dhcpcd running, and need to
find a way to turn off pump. Or, if you prefer pump, need to turn off dhcpcd.
The man page for each should tell you where it keeps the DHCP info it got
from the DHCP server.
>>Given that your forwarding nameservers are both on 206, I'm going to
>>assume that is the correct number. Please correct me.
>
>Yes, that is correct.
If so, how do you explain this?
>>2. the output of:
>>
>>route -n
>
>Destination Gateway Genmask Flags Metric Ref
>Use Iface
>192.168.1.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
>216.9.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth1
>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
>0.0.0.0 216.9.0.1 0.0.0.0 UG 0 0
> 0 eth1
>
>Note: It *is* 216: not a typo
I have a strong hunch a misconfigured gateway could be a good part of your
troubles. (There may be others, but surely this is one.)
I suggest shutting down one DHCP client, and then reading the man page for
the other to find out where it stores the info it got from the server, so
we can settle the 206/216 issue once and for all.
What does "ifconfig" show now?
>>3. your DHCP config information from your ISP (obtained from some file
>> from pump or dhcpcd)
>
>Will /etc/resolv.conf do?
>
>search cnw.com
>nameserver 206.40.133.20
>nameserver 206.129.112.21
Nope; you want the file where dhcpcd (for example) stores the config info
it got. The following is an excerpt from the dhcpcd man page:
FILES
/etc/dhcpc
directory used for storing files created by dhcpcd
/etc/dhcpc/dhcpcd-<interface>.info
file in which dhcpcd saves the host information.
The word interface is actually replaced with the
network interface name like eth0 to which dhcpcd is
attached.
>>5. The actual network config of the Winbox
>
>IP Address 192.168.1.2
>Subnet Mask: 255.255.255.0
>DNS Configuration
> Enable DNS is checked
> DNS Server Search Order
> 206.40.133.20
> 206.129.112.21
> 192.168.1.1
>Gateway 192.168.1.1
>(Note: Just barely added the 192.168.1.1 to both entries above to test...)
This configuration is fine (assuming your nameservers are OK, but we're
doing networking first.)
>I've rebooted so I imagine they've been reactivated, yes.
"service ipchains status" will return to you the list of currently active
ipchains rules. Yes, they should have reactivated.
Man, I have *no* idea why this is so difficult. I didn't know how to do
this, and my 7.2 box I just set up (a Cyrix P166+) took me 30 minutes to do.
You sure you don't want to install 7.2 on here, then I can guide you to my
config? :) Probably take less time than to figure the current config out...
<grin>
--
Rodolfo J. Paiz
[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
