Can someone Please help me...please

[bruce1271]

I cant ping my pc from my linux box. Everything was working great til I powered off my linux box. My pc is 192.168.1.3 and is on 255.255.255.0 subnet and gateway is 192.168.1.1 I think I have tried evrything, but I am lost. I have ipchains running but opened them all to accept everything all ways.


Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
target prot opt source destination ports
MASQ all ------ anywhere anywhere n/a
Chain output (policy ACCEPT):
Chain acct (0 references):


route -n
---------

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
4.33.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 4.33.104.1 0.0.0.0 UG 0 0 0 ppp0


ifconfig
-----------
eth0 Link encap:Ethernet HWaddr 00:20:78:E1:45 http://www.linuxnewbie.org/ubb/biggrin.gif4
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13767 errors:0 dropped:0 overruns:0 frame:0
TX packets:10722 errors:0 dropped:0 overruns:0 carrier:0
collisions:5 txqueuelen:100
Interrupt:10 Base address:0x6100

eth1 Link encap:Ethernet HWaddr 00:20:78:E1:46:09
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:72 dropped:0 overruns:0 carrier:72
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x6200

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:99 errors:0 dropped:0 overruns:0 frame:0
TX packets:99 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

ppp0 Link encap:Point-to-Point Protocol
inet addr:4.33.104.3 P-t-P:4.33.104.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:13765 errors:0 dropped:0 overruns:0 frame:0
TX packets:10715 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10

[Mountainman]

So, you powered down your linux box and now you cant ping between another computer and the linux box? Is this basically what your saying? <looks at your post>It looks like all of your interfaces are up. Kind of strange. Did you move any cables or anything? What OS is on your other computer?
Upon closer inspection, did you see that you had 72 errors on TX for eth0? Might want to start tracing from there.
Sorry, eth1.

[ 02 February 2001: Message edited by: Mountainman ]
undefinedundefinedundefined

[ 02 February 2001: Message edited by: Mountainman ]

[bruce1271]

Hi, Thanks for your help..

The errors are because I cant ping ...eth1 is connected to my win 98 machine. However, when I try to ping it says "--- 192.168.1.3 ping statistics ---
16 packets transmitted, 0 packets received, 100% packet loss"

I think I have transmitted many packets
But in my error when I do ifconfig It says "TX packets:0 errors:117 dropped:0 overruns:0 carrier:117" I see the light blinking on my hub as if the signal is out there, but not reaching the PC. Also I trie pinging from my pc...I see the light blinking on the hub, but no return signal from linux. :confused:

[bruce1271]

Hi, Thanks for your help..

The errors are because I cant ping ...eth1 is connected to my win 98 machine. However, when I try to ping it says "--- 192.168.1.3 ping statistics ---
16 packets transmitted, 0 packets received, 100% packet loss"

I think I have transmitted many packets
But in my error when I do ifconfig It says "TX packets:0 errors:117 dropped:0 overruns:0 carrier:117" I see the light blinking on my hub as if the signal is out there, but not reaching the PC. Also I trie pinging from my pc...I see the light blinking on the hub, but no return signal from linux. :confused:

[mindwarp.out]

Uninstall and reinstall TCP/IP on the windows box. Dont enter a gateway on it. Make sure that Eth1 on the linux box goes to the same hub that the windows box goes into. Make sure both have a IP in the 192.168.1.1- range and the subnet for both is 255.255.255.0. Make sure you see the 2 lights on the hub. Try testing them without being connected to the internet. What is the exact ping error message?

Mindwarp

[bruce1271]

Ok, I deleted and re-installed tcp on windows 98 machine-192.168.1.2. All your other requests were already in place. Still no ping. However, I re-started linux as well. and before I started the adsl-start execution, I tried pinging and got these errors:
[root@localhost /root]# ping 192.168.1.0 PING 192.168.1.0 (19256 data bytes ping: sendto: Operation not permitted ping: wrot64 chars, ret=-1 ping: sendto: Operation not permitted ping: w--- 192.168.1.0 ping statistics --- 2 packets transmitted, 0 p
[root@localhost /root]# ping 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.4 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.2 ms
--- 127.0.0.1 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss

As you can see, I cant ping any internal eth0 or eth1 on my linux box before I execute adsl-start. I think it because I have ipchians and the adsl-start prog runs my firewall script which allows my pinging. Is that correct??

Anyway, after I run my ipchains rulesI can ping internal, but when I go external there is this:

[root@localhost /root]# ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2): 56 data bytes

--- 192.168.1.2 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

[root@localhost /root]#


Whats next? my route table is this: Is this correct?
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
192.168.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
4.33.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 4.33.104.1 0.0.0.0 UG 0 0 0 ppp0
[root@localhost /root]#

Thanks for your help!

[bruce1271]

Is the gateway supposed to be 0.0.0.0??

[mindwarp.out]

I am still reading your huge posts :) The gateway 0.0.0.0 should be bound to your outgoing interface.. it is your default gateway, so that any traffic not meant for your network goes there..

Mindwarp

[mindwarp.out]

Also dont bind a IP address to the interface that you are using ADSL with.. (are you using roaring penguin? if so dont give it a ip address) What dist are you using? So your adsl ethernet card (the one that goes to your dsl modem) should have no IP, but you can do a ifconfig eth0 UP so that it is up..

[mindwarp.out]

Also.. if the interface that we are trying to take the ip off of already has a ip and you dont know how to remove it type:

# <-- command prompt symbol - dont type it
#lsmod
#modprobe -r yourniccardsmodule
#modprobe yourniccardsmodule
#ifconfig eth1(or whatever the dsl interface is) UP

and see if it helps

Mindwarp

[bruce1271]

Thanks,
but none of what you suggested worked. I think it has something to do with my route or ipchains.

[Delta_z]

there is something messed up in your route table.

"4.33.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0"

see that 4.33.104.1 it should be like 4.33.104.xx. the 4.33.104.1 is the gateway of your ISP.


"192.168.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0"

also you have a NIC card ip set to 192.168.0.1 which is a no-no but 192.168.2.1 for ith0 would be ok

And don't reinstall TCP/IP windows anything that is not the problem! your linux box is simply miss configured

[bruce1271]

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
192.168.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
4.33.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 4.33.104.1 0.0.0.0 UG 0 0 0 ppp0

Thanks for the reply,
I agree with you I think I am mis-configured. I think the 4.33.104.1 is my P-t-P on my ppp0 device. I am using linux now to type thi s message, so my internet connection is not a problem. It has something to do with eth1(which is connected to my windows machine). I see the light blinking on my hub, but no return acknowledgement and vice versa FROM windows. Once again. Thanks and any more advice is helpful.

[bruce1271]

Well, I went out and bought a new hub and new cables and still no ping reply...next step = burning the linux box...aaaaahhhhhhhhhhhh!!! :eek:

[mindwarp.out]

Hey wait! Dont burn that box. Here is what my table looks like (eth0 is the lan)

64.108.241.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 64.108.241.1 0.0.0.0 UG 0 0 0 ppp0

So basically delete the entries for your 192.168.1.1 255.255.255.255 etc.. they are unneeded

Mindwarp

[bruce1271]

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
4.33.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.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 4.33.104.1 0.0.0.0 UG 0 0 0 ppp0

Well, no more 255.255.255.255 and I still cant ping..oh well such is life.

[Delta_z]

your missing one more line in your route. you need something like this.

"192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1"

do you have eth1 assigend as 192.168.1.0? If you do then you can't do that it has to be like 192.168.1.1 and then the NIC on your windows machine is 192.168.1.2. Your almost there!

[bruce1271]

Hi,

I had 192.168.1.1 with 255.255.255.255 and it did not work. that was my original config.
Also, eth1 is assigned 192.168.1.1 in the ifconfig data.

Nothing yet.

[Guitarlynn]

Have you enabled forwarding on the Linux "router" box?

You'll have to locate the exact location of this file on your box, but the line will be:

echo "1" > /proc/<your_path>/ip_forward

You can also check this with:

cat /proc/<your_path>/ip_forward

If it gives you "1", the forwarding is enabled. If it gives you "0", then forwarding is not enabled.

Also a mask of 255.255.255.255 will not work on the class C you are running, change the mask on all your 192.168.x.x boxes to 255.255.255.0 with a broadcast of 192.168.x.255 . The gateway on all the boxes (except the Linux router) should be the interface on the router they are connected (ie... 192.168.1.1 for this subnet, 192.168.0.1 for the other subnet). I would either build a "hosts" file for all computers on the network or set Samba as a WINS server (which would require all client boxes to use the respected ethx inface for the WINS server in the TCP/IP settings).

The only other thing I can think of is you only need to run ipmasq on the external IFACE. You may be masq'ing the internal networks from themselves (this looks like the case). Through NAT all addresses forwarded to the WAN will carry the ip of your EXTERNAL_IFACE on the ppp0 device.

This is a guess,
but it does look like a masq problem
without seeing your ruleset.
~Guitarlynn

[bruce1271]

Ok, So I am looking at my /var/log/boot.log and i am seeing this:
Feb 4 18:25:19 localhost ifup: eth1: Host name lookup failure

But,
Feb 4 18:25:18 localhost network: Bringing up interface eth0 succeeded

eth1 is where I am having the problem, but when I do if-up on eth1 everything seems fine and in ifconfig it actsa as if it is up. I dont know if this is part of my problem or not??? I dont think so

[bruce1271]

Guitarlynn,

ip_forward returns a 1.

I do have my windows98 gateway set to 192.168.1.1 (eth1 on linux).

I am not sure I understand your last paragraph about the masq problem?? Can you explain a little more or give me a few commands to check this? I have all MASQed in my ipchains rules.

Thanks for your help

[X_console]

I haven't read the entire thread yet, but from what I've read so far, it looks like you don't have your gateway right. You say your gateway is 192.168.1.1 But when you type "route -n" it's not there. So try typing this as root:

route add default gw 192.168.1.1

See if that works. If it does, then add it to your /etc/rc.d/rc.local (or to the one that controls networking if you know which since it varies between distributions).

[mindwarp.out]

bruce,

post us your

ifconfig eth0
and
ifconfig eth1


Mindwarp

[bruce1271]

Hi, I meant to say my gateway on windows I used was 192.168.1.1(my ip of eth1 in linux).
Just for kicks,I tried adding to the route my default of 192.168.1.1 and it locked up all my routes, so I removed it again.

Here is my ifconfig data:
eth0 Link encap:Ethernet HWaddr 00:20:78:E1:45 :D4
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5565 errors:0 dropped:0 overruns:0 frame:0
TX packets:5038 errors:0 dropped:0 overruns:0 carrier:0
collisions:2 txqueuelen:100
Interrupt:10 Base address:0x6100

eth1 Link encap:Ethernet HWaddr 00:20:78:E1:46:09
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:75 dropped:0 overruns:0 carrier:75
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x6200

[bruce1271]

Well, I guess no-one here knows whats going on either...atleast that is comforting to know I am not the only one who doesnt know how to fix this problem

[aph3x]

im kinda confused as to which interface is on which box, so forgive me if im wrong. :)

in the following im assuming eth1 is on the windoze box, and the eth0 is your internal NIC on your linux box, not the NIC running to your DSL router...

according to your ifconfig, your eth0 and eth1 are located on different subnets:

eth0 Link encap:Ethernet HWaddr 00:20:78:E1:45 :D4
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0

eth1 Link encap:Ethernet HWaddr 00:20:78:E1:46:09
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0

it looks like the broadcast should both be set to 192.168.255.255 and the netmask both set to 255.255.0.0

hope that helps :D

[ 07 February 2001: Message edited by: aph3x ]

[bruce1271]

Thanks for the reply.

Eth0 and eth1 are in my linux box. I have an etherent card in my windows 98 that has a gateway of 192.168.1.1 and ip of 192.168.1.x (i have played with x, but it doesnt matter if its 2 or 5 or whatever). I get my dsl into linux on eth0 of linux. then form eth1 of linux I go to a hub which then is connected to the windows machine. My dsl works inot linux with no problem. I just cant ping eth1 of linux to the windows98 machine.
The different subnets of eth0 or eth1 is not of consequence for eth1 pinging windows98 is it? I tried doing what you requested, but it did not help. Thank you though.

[bruce1271]

OK SOME NEW NEWS!!!!!!!!!!!!!!

I removed my connection from DSL-ETH0 and put ETH0-hub instead. I reset my windows 98 to 192.168.0.5. I can now ping my windows machine form LINUX...YEAHHH!! I tried to connect with my old eth1 to DSl and it doesnt work. BOOOO. So tomorrow, I will try to swap etherent cards places in my mother board. They are both linksys and same model, so it should be transparent to start-up, but this way I will tell If I have a bad card.
Other than this, What are the suggestions for seeing why eth1 doesnt do a damn thing?? I can see my hub blinking so I have a feeling the card will be good, just the config of eth1 is bad.

So any ideas as to why eth1 config is bad is helpful. Thanks

Bruce

[bruce1271]

FOUND THE PROBLEM

Etherent card was bad. I didnt know these cards went bad?? I have had it for a year now with no problem. When I swapped the cards, eth1 slot now works and eth0 slot is now bad. So, I have to go buy a new card. Atleast I dont have to mess with re-config.


THANKS TO ALL THOSE WHO HAVE HELPED..

[mindwarp.out]

Man.. after all that :) hehe.. well thats excellent, atleast now you dont think linux sucks, which is always a good thing.

Mindwarp

[AWebDesign]

Lol, i'm reading this whole thread, and thinking, "i bet it's a bad NIC card". Then my curiosity gets the best of me, i scroll all the way down and behold, a bad nic. FYI, nics do go bad, just like everything else in a computer.

Aaron
LPSB PC Tech

[Delta_z]

I don't think there is anything wrong with your NIC card look at the ifconfig's. Your eth0 is set to 192.168.0.1 which is the same as 255.255.0.0 and your eth1 set to 192.168.1.1 for 255.255.255.255.0 which is fine. What I think is happening is eth0 is consuming eth1's IP's that's why when you take it out it works. I'm no expert on this stuff so I could be very wrong. I think the 0 and 255 are reserved numbers for broadcasting in the IP number.

[ToadMan8]

Originally posted by bruce1271:
Ok, So I am looking at my /var/log/boot.log and i am seeing this:
Feb 4 18:25:19 localhost ifup: eth1: Host name lookup failure

You're using red hat 7 aren't you?? Try using the hostname command, (#>hostname [your hostname]) and you should be able to use the int. Problem is, redhat 7 forgets its own hostname when you reboot the first time. dunno why. doesn't do it any other time