I Can't ping anything. What am I'm doing wrong?

sharris · 2010-06-26 08:43:29

For the past few days I been reading many networking examples to create a small LAN behind a gateway firewall. I read and search a lot and worked all day and night trying every example I studied and still I was never able to ping anything Could some tell me how to get thing thing going and also is there a good simple proven how-to... There are so many difference example with difference ways of doing things but even the most simple way did not work for me. It seems like I have connection but can't do anything. All I want to to is run my Windows, Linux and BSD machines behind a gateway firewall and nothing else special for now because I don't want to slow things down to much. At one point I was able to get all 4 pings from Windows to the gateway in the LAN, but lost it because of changing things around so much.

resolve.conf

domain gateway.2wire.net
nameserver 192.168.1.254

rc.conf:

HOSTNAME-"myhost"
eth0="dhcp"
INTERFACES=(eth0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

eth0      Link encap:Ethernet  HWaddr 00:14:D1:1B:16:1A  
          inet addr:192.168.1.65  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3287 (3.2 Kb)  TX bytes:594 (594.0 b)
          Interrupt:10 Base address:0x2000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@myhost ~]# ping 192.168.1.4
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
From 192.168.1.65 icmp_seq=1 Destination Host Unreachable
From 192.168.1.65 icmp_seq=2 Destination Host Unreachable
From 192.168.1.65 icmp_seq=3 Destination Host Unreachable
From 192.168.1.65 icmp_seq=4 Destination Host Unreachable
From 192.168.1.65 icmp_seq=5 Destination Host Unreachable
From 192.168.1.65 icmp_seq=6 Destination Host Unreachable
From 192.168.1.65 icmp_seq=7 Destination Host Unreachable
From 192.168.1.65 icmp_seq=8 Destination Host Unreachable
From 192.168.1.65 icmp_seq=9 Destination Host Unreachable

[1]+  Stopped                 ping 192.168.1.4

[root@myhost ~]# traceroute 192.168.1.4
traceroute to 192.168.1.4 (192.168.1.4), 30 hops max, 40 byte packets
 1  INNSF8GKSB61084 (192.168.1.65)  3002.161 ms !H  3002.591 ms !H  3003.181 ms !H


[root@myhost ~]#

Thanks in advance for all

Last edited by sharris (2010-06-26 08:45:39)

andresp · 2010-06-26 08:56:27

What does dhcpcd output, and route?

sharris · 2010-06-26 10:35:46

This all I could get. I search the web for the dhcpd code but there seem to be a lot of flags for it and it hard to get the hang of it, looks like perls. I'll be looking into dhcpcd until I shee what it does and get it right.

Script started on Sat 26 Jun 2010 06:04:37 AM CDT
[root@myhost ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     202    0        0 eth0


default         home            0.0.0.0         UG    202    0        0 eth0
[root@myhost ~]# 
[root@myhost ~]# 
[root@myhost ~]# killall dhcpcd
[root@myhost ~]# killall dhcpcd -I "" -d
Usage: killall [OPTION]... [--] NAME...
       killall -l, --list
       killall -V, --version

  -e,--exact          require exact match for very long names
  -I,--ignore-case    case insensitive process name match
  -g,--process-group  kill process group instead of process
  -i,--interactive    ask for confirmation before killing
  -l,--list           list all known signal names
  -q,--quiet          don't print complaints
  -r,--regexp         interpret NAME as an extended regular expression
  -s,--signal SIGNAL  send this signal instead of SIGTERM
  -u,--user USER      kill only process(es) running as USER
  -v,--verbose        report if the signal was successfully sent
  -V,--version        display version information
  -w,--wait           wait for processes to die

[root@myhost ~]# DHC[K[KHCPCD_ARGS="[]b][C-A[]/]b][C -t 30 -h $HOSTNAME"

[root@myhost ~]# DHCPCD_ARGS="[b]-A[/b] -t 30 -h $HOSTNAME"
dhcpcd: version 5.0.6 starting
dhcpcd: forking to background
[root@myhost ~]# exit
exit

Script done on Sat 26 Jun 2010 06:10:11 AM CDT

btw: what was I not suppose to post since it is about protecting a LAN, or does it matter what numbers you post..

abraham10 · 2010-06-26 19:23:37

What does:

dhcpcd eth0

print out?

sharris · 2010-06-26 20:08:04

I just blew my first major networking question Sorry about that Archers. Ping works fine. I had At&t DSL firewall running at full-blast, all setting checked, stealth to never and I paid for it, but I learn a lot about DHCP, NAT, routers and command-line options in these three days than I ever done, anything. Look-out CompTIA.

Thanks for the tips guys

Penguin Guy · 2010-06-26 21:13:02

sharris wrote:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     202    0        0 eth0
btw: what was I not suppose to post since it is about protecting a LAN, or does it matter what numbers you post..

None of those numbers identify you. 192.168.1.0 is a local address, it will only work from inside your network (mine is also 192.168.1.0).

sharris · 2010-06-26 21:18:17

What I said above is not going to help the next person who may not know or remember when one sometimes make changes to DSL settings than forget, than discover Networking years latter. You can CHECK to OPEN or BLOCK anything you want but you MUST leave *** All Other Protocols *** CHECKED or else ping don't work... You would think it was Stealth Mode, Block Ping and Strict UDP Session Control but they absolutely have nothing to do with it.

DSL - 2Wire Firewall

Stealth Mode
Block Ping
Strict UDP Session Control
Inbound and Outbound Control


Outbound
HTTP
HTTPS
FTP
Telnet
SMTP
DNS
NetBIOS
POP3
IMAP
NNTP
IRC
H323
All Other Protocols     - -   Keep a check mark here or NO-PING will work

sharris · 2010-06-26 21:28:24

Hi Penguin Guy, I could be wrong but I'm thinking it not good to post your NIC card last three digits, expecially when posting every single thing else about the machine. Your NIC is your true ID that make it all tick ... but we post them everyday so it must don't really matter unless the CIA or KGB was looking for you.

Last edited by sharris (2010-06-26 21:35:37)

Arch Linux

#1 2010-06-26 08:43:29

I Can't ping anything. What am I'm doing wrong?

#2 2010-06-26 08:56:27

Re: I Can't ping anything. What am I'm doing wrong?

#3 2010-06-26 10:35:46

Re: I Can't ping anything. What am I'm doing wrong?

#4 2010-06-26 19:23:37

Re: I Can't ping anything. What am I'm doing wrong?

#5 2010-06-26 20:08:04

Re: I Can't ping anything. What am I'm doing wrong?

#6 2010-06-26 21:13:02

Re: I Can't ping anything. What am I'm doing wrong?

#7 2010-06-26 21:18:17

Re: I Can't ping anything. What am I'm doing wrong?

#8 2010-06-26 21:28:24

Re: I Can't ping anything. What am I'm doing wrong?

Board footer