Robert,
When I enter that command I get a message back, Network unreachable. I had done this
once before.
Any other ideas??
Steven
*********** REPLY SEPARATOR ***********
On 6/14/2000 at 3:09 PM Robert Glover wrote:
>Okie Dokie! You have the DSL and your LAN hooked into the same hub?
>-- that's bad security, but I bet you just want to get things working
>for now. I'll throw in my 2 bits and say that you should not hook the
>internet directly to your LAN. You'll be broken into in no time that
>way. You should run the DSL into the Linux box and use ipchains and
>IP masquerading to firewall it away from the LAN. But since you're
>going to do it anyway, read on.
>
>First of all you need a default route, and to do that you will need
>the IP address of your ISP's router(gateway). Since your Windoze box
>sees the net okay, get the info from it. Here's an example of how to
>use the route command to add a default gateway. You could go into
>linuxconf and do it, but do it my way -- it'll grow hair on your chest
>:) Well, okay linuxconf will make the default route permanent, so
>once you have it working use linuxconf.
>
>route add default gw 216.233.X.1
> ^^^^^^^^^^^ This is the IP address of your ISP's
>router/gateway.
>
>You may have trouble if you only have one IP address from your ISP.
>If you set both the windoze box and the Linux box to the same IP
>address, you will have problems. The ISP's gateway may watch Mac
>addresses and only allow one (if you only paid for one).
>
>The IP address that isn't yours is the broadcast address formed by
>doing certain bitwise operations on your IP address. I won't go into
>that anymore. You don't need to worry about it at this point.
>
>
>> Good Morning again,
>>
>> I was asked some question about the way my network was set up. This is the
>information it gave me.
>> I know something is wrong, but not sure what. I did go though some of the network
>help on redhat.com, but
>> the 3howto was down.
>>
>> S
>> *********** REPLY SEPARATOR ***********
>>
>> On 6/14/2000 at 9:14 AM Robert Glover wrote:
>>
>> >> Good Evening Group,
>> >>
>> >[ snip ]
>> >>
>> >> I have a DSL line, and the windoze box that I have see's the net OK. I can not
>even see
>> >> the box from within my own network.
>> >>
>> >> So my question is (well the best I can do with my limited knowledge.) IS WHY?
>I ran
>> >> netcfg and put in the information for the network. If I run netstat -a it tells
>me that I have
>> >> an IP address and the name of the box. ifconfig has also been run. It tells me
>the best
>> >> that I can tell everything is OK.
>> >>
>> >> So HELP........... If you tell me something needs to be done, I can do most
>things
>> >> from memory. If not, please give me kind of a step by step of what you need done.
>> >> I have set up a named.conf file, also a hosts file. I think that I have set up
>all the files I need.
>> >>
>> >> One question first, is there an issue with the nic card on this box. I think it
>is an 82XX card.
>> >>
>> >> Steven
>> >
>> >Well, in your case I would suspect routing. Did you set up a
>> >(default) route? If you continue to have problems, include more
>> >information like:
>> >
>> >0. Did you read the NET-3-HOWTO?
>> Tried this... But the server states that is an 404 error....
>>
>> >1. When you say ping, what did you ping?
>> I did a ping box name.
>>
>> >2. Do you have a hub? Are both the windoze and Linux PC's on the LAN
>> >at the same time? Can they ping each other?
>> Yes, I have a hub, Yes both are on the same lan at the same time. No I can not
>ping each other.
>>
>> >3. What does the output of ifconfig look like.
>> Lots of information:
>> eth0 Link encap Ethernet HWaddres Mac address 00:A0:C9:XX:XX:XX
>> inet address (Currect IP_) Bcast: An IP address that is not mine
> Mask 255.255.255.248
>> RX Packets: 119 errors: 0 dropped: 0 overruns:0 Frame:0
>> TX Packets:0 " " " "
>> colisions:0 txqueuelen:0x2800
>>
>> lo Link encap Local Loopback
>> inet address 127.0.0.1 Mask 255.0.0.0
>> RX Packets: 104 errors: 0 dropped: 0 overruns:0 Frame:0
>> TX Packets:104 " " " "
>> colisions:0 txqueuelen:0
>>
>>
>> >4. What does the output of the route command look like?
>> 216.233.X.X * 255.255.255.255 UH 0 0 0 eth0
>> 216.233.X.X * 255.255.255.248 U " " " "
>> 127.0.0.0 * 255.0.0.0 U " " " lo
>>
>>
>> >5. What does the output of lsmod look like? This will help determine
>> >which module(driver) is being loaded for your NIC.
>>
>> eepro100 12272 1 (autoclean)
>> scsi card
>>
>>
>> >
>> >This will go a long way in helping diagnose the problem. And who
>> >knows: maybe before you get down to number 5, you'll have figured it
>> >out all by yourself.
>> >
>> >
>
>
>--
>To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
>as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
