LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 07-04-2013, 06:54 AM   #1
sparkinson
LQ Newbie
 
Registered: Jul 2013
Posts: 5

Rep: Reputation: Disabled
Connected to router but cannot access internet/ssh/ping e.t.c


Some very weird behaviour going on with my network connection. I am connected to my router via ethernet (have also tried wireless with the same effect) but I cannot connect to the internet. I am going to call this computer computer A from now on.

I am currently typing on another computer (computer B) connected to the same router in exactly the same way, and this one is fine.

Other effect:
a) If I log into my router I can see that computer A is connected at 192.168.0.6
b) When I try to ssh into computer A from computer B I get:
ssh: connect to host 192.168.0.6 port 22: No route to host
c) When I try to ping computer A I get:
From 192.168.0.2 icmp_seq=1 Destination Host Unreachable
d) When I try to ssh into computer B from computer A it ssh's into itself??!??!?
e) When I try to ping www.google.com from computer A I get nothing
f) When I try to ping 173.194.66.147 (which is www.google.com) from computer A I occasionally get something but this is very glitchy.

At first I thought it was my resolv.conf, so I tried changing this to be the same as the working computer. This is included below:
Code:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1   # ip address of my router
nameserver 127.0.1.1
search Home

nameserver 208.67.222.222
nameserver 208.67.220.220
this is the output from some key commands:
Code:
#dmesg |grep eth           #check what is recognized
[    0.092335] reboot: BIOS series board detected. Selecting HP Compaq Laptop-method for reboots.
[    0.140073] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
[    1.552326] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
[    1.573818] b44 ssb0:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:15:60:cb:dd:3c
[   16.094067] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.763273] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
[   20.609954] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   20.610327] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   23.804222] b44 ssb0:0 eth0: Link is up at 100 Mbps, full duplex
[   23.804230] b44 ssb0:0 eth0: Flow control is off for TX and off for RX
Code:
#ifconfig -a               #get device info
eth0      Link encap:Ethernet  HWaddr 00:15:60:cb:dd:3c  
          inet addr:192.168.0.6  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::215:60ff:fecb:dd3c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1585 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1090 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:349984 (349.9 KB)  TX bytes:126257 (126.2 KB)
          Interrupt:16 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:3489 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3489 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:284300 (284.3 KB)  TX bytes:284300 (284.3 KB)

wlan0     Link encap:Ethernet  HWaddr 00:13:02:65:96:6a  
          BROADCAST MULTICAST  MTU:1500  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:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Code:
#iwconfig                  #unsure what you connect with
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11abg  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=off   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
Code:
#route -n                  #get route table
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U     1      0        0 eth0
Code:
#uname -a                  #kernel ?
Linux maeldeb 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:59 UTC 2013 i686 i686 i686 GNU/Linux
Code:
#lsmod                     #modules loaded
Module                  Size  Used by
snd_hda_codec_si3054    12864  1 
snd_hda_codec_analog    75266  1 
coretemp               13131  0 
kvm                   376505  0 
pcmcia                 39544  0 
hp_wmi                 17712  0 
snd_hda_intel          38307  2 
joydev                 17097  0 
snd_hda_codec         117580  3 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec_analog
ppdev                  12817  0 
snd_hwdep              13272  1 snd_hda_codec
sparse_keymap          13658  1 hp_wmi
snd_pcm                80890  3 snd_hda_codec_si3054,snd_hda_codec,snd_hda_intel
snd_page_alloc         14230  2 snd_pcm,snd_hda_intel
snd_seq_midi           13132  0 
snd_seq_midi_event     14475  1 snd_seq_midi
bnep                   17669  2 
snd_rawmidi            25114  1 snd_seq_midi
rfcomm                 37420  4 
bluetooth             202069  10 bnep,rfcomm
snd_seq                51280  2 snd_seq_midi_event,snd_seq_midi
parport_pc             27504  1 
i915                  535507  3 
arc4                   12543  2 
wmi                    18590  1 hp_wmi
yenta_socket           27095  0 
iwl3945                63619  0 
snd_seq_device         14137  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              24411  2 snd_pcm,snd_seq
pcmcia_rsrc            18191  1 yenta_socket
drm_kms_helper         47545  1 i915
iwlegacy               87575  1 iwl3945
video                  18894  1 i915
mac80211              526519  2 iwl3945,iwlegacy
pcmcia_core            21505  3 pcmcia,pcmcia_rsrc,yenta_socket
snd                    56485  14 snd_hda_codec_si3054,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_hda_codec_analog
mac_hid                13037  0 
drm                   228750  4 i915,drm_kms_helper
lpc_ich                16925  0 
i2c_algo_bit           13197  1 i915
cfg80211              436177  3 iwl3945,iwlegacy,mac80211
psmouse                81038  0 
soundcore              12600  1 snd
microcode              18286  0 
serio_raw              13031  0 
lp                     13299  0 
parport                40753  3 lp,ppdev,parport_pc
firewire_ohci          35292  0 
b44                    31137  0 
firewire_core          61718  1 firewire_ohci
ssb                    50834  1 b44
crc_itu_t              12627  1 firewire_core
Any ideas?? I am completely stuck?

Cheers,

sparkinson

Last edited by sparkinson; 07-04-2013 at 06:56 AM.
 
Old 07-04-2013, 07:07 AM   #2
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,373

Rep: Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962
Forget all that. Can you reliably ping your router?

Also, let's try some other bits and bobs... can you ping your DNS server IP? what about 8.8.8.8?

if you can't do this stuff, let's do it again, but also run "tcpdump -i eth0 -ven" and post the output from that whilst your pinging - including the other computer IF you can hit the router OK

Last edited by acid_kewpie; 07-04-2013 at 07:09 AM.
 
Old 07-04-2013, 07:36 AM   #3
sparkinson
LQ Newbie
 
Registered: Jul 2013
Posts: 5

Original Poster
Rep: Reputation: Disabled
Hi Chris,

Thanks for your help. I can ping 192.168.0.1 (my router) and 127.0.1.1 (not sure what this is, is it my router again?) but nothing external, and not 8.8.8.8.

The output from "tcpdump -i eth0 -ven" is below:
Code:
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
13:32:59.897532 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:00.565634 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 80: (tos 0x0, ttl 64, id 16534, offset 0, flags [DF], proto UDP (17), length 66)
    192.168.0.6.58759 > 208.67.222.222.53: 61562+ A? client57.dropbox.com. (38)
13:33:02.870006 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 96: (tos 0x0, ttl 64, id 17110, offset 0, flags [DF], proto UDP (17), length 82)
    192.168.0.6.33668 > 208.67.222.222.53: 33072+ A? safebrowsing.clients.google.com.Home. (54)
13:33:02.893507 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:03.893478 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:04.023631 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.4 (ff:ff:ff:ff:ff:ff) tell 192.168.0.1, length 46
13:33:04.893480 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:06.883609 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 79: (tos 0x0, ttl 64, id 18114, offset 0, flags [DF], proto UDP (17), length 65)
    192.168.0.6.36153 > 208.67.222.222.53: 53448+ A? notify3.dropbox.com. (37)
13:33:06.906474 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:06.948555 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 91: (tos 0x0, ttl 64, id 18130, offset 0, flags [DF], proto UDP (17), length 77)
    192.168.0.6.42683 > 208.67.222.222.53: 26401+ A? safebrowsing.clients.google.com. (49)
13:33:06.948575 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 91: (tos 0x0, ttl 64, id 18131, offset 0, flags [DF], proto UDP (17), length 77)
    192.168.0.6.42683 > 208.67.222.222.53: 42577+ AAAA? safebrowsing.clients.google.com. (49)
13:33:07.906448 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:08.806301 00:15:60:cb:dd:3c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 165: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 151)
    192.168.0.6.17500 > 255.255.255.255.17500: UDP, length 123
13:33:08.906440 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:09.065892 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.4 (ff:ff:ff:ff:ff:ff) tell 192.168.0.1, length 46
13:33:09.574913 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 85: (tos 0x0, ttl 64, id 18787, offset 0, flags [DF], proto UDP (17), length 71)
    192.168.0.6.46720 > 208.67.222.222.53: 19867+ A? client57.dropbox.com.Home. (43)
13:33:11.879350 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 96: (tos 0x0, ttl 64, id 19363, offset 0, flags [DF], proto UDP (17), length 82)
    192.168.0.6.55573 > 208.67.222.222.53: 33072+ A? safebrowsing.clients.google.com.Home. (54)
13:33:11.902472 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:12.902399 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:13.902409 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:14.102696 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.4 (ff:ff:ff:ff:ff:ff) tell 192.168.0.1, length 46
13:33:15.892970 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 84: (tos 0x0, ttl 64, id 20366, offset 0, flags [DF], proto UDP (17), length 70)
    192.168.0.6.46019 > 208.67.222.222.53: 14483+ A? notify3.dropbox.com.Home. (42)
13:33:15.915390 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:15.957848 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 96: (tos 0x0, ttl 64, id 20382, offset 0, flags [DF], proto UDP (17), length 82)
    192.168.0.6.43898 > 208.67.222.222.53: 10714+ A? safebrowsing.clients.google.com.Home. (54)
13:33:15.957869 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 96: (tos 0x0, ttl 64, id 20383, offset 0, flags [DF], proto UDP (17), length 82)
    192.168.0.6.43898 > 208.67.222.222.53: 4224+ AAAA? safebrowsing.clients.google.com.Home. (54)
13:33:16.915360 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:17.524480 a0:88:b4:12:f0:d8 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 86: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 72)
    192.168.0.2.57621 > 192.168.0.255.57621: UDP, length 44
13:33:17.915356 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:18.584248 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 85: (tos 0x0, ttl 64, id 21039, offset 0, flags [DF], proto UDP (17), length 71)
    192.168.0.6.59587 > 208.67.222.222.53: 19867+ A? client57.dropbox.com.Home. (43)
13:33:19.139863 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.4 (ff:ff:ff:ff:ff:ff) tell 192.168.0.1, length 46
13:33:20.886428 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 91: (tos 0x0, ttl 64, id 21614, offset 0, flags [DF], proto UDP (17), length 77)
    192.168.0.6.48804 > 208.67.222.222.53: 23397+ A? safebrowsing.clients.google.com. (49)
13:33:20.909349 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:21.909362 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:22.029469 a0:88:b4:12:f0:d8 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 165: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 151)
    192.168.0.2.17500 > 192.168.0.255.17500: UDP, length 123
13:33:22.909319 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:24.182041 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.4 (ff:ff:ff:ff:ff:ff) tell 192.168.0.1, length 46
13:33:24.902323 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 84: (tos 0x0, ttl 64, id 22618, offset 0, flags [DF], proto UDP (17), length 70)
    192.168.0.6.44717 > 208.67.222.222.53: 14483+ A? notify3.dropbox.com.Home. (42)
13:33:24.925313 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:24.966943 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 96: (tos 0x0, ttl 64, id 22635, offset 0, flags [DF], proto UDP (17), length 82)
    192.168.0.6.39849 > 208.67.222.222.53: 10714+ A? safebrowsing.clients.google.com.Home. (54)
13:33:24.966966 00:15:60:cb:dd:3c > 7c:4c:a5:0d:00:74, ethertype IPv4 (0x0800), length 96: (tos 0x0, ttl 64, id 22636, offset 0, flags [DF], proto UDP (17), length 82)
    192.168.0.6.39849 > 208.67.222.222.53: 4224+ AAAA? safebrowsing.clients.google.com.Home. (54)
13:33:25.925304 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:26.925291 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46

42 packets captured
42 packets received by filter
0 packets dropped by kernel
Thanks again
 
Old 07-04-2013, 07:44 AM   #4
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,373

Rep: Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962
Hmmm, odd. So we can see the router arping for you:

13:33:20.909349 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46
13:33:21.909362 7c:4c:a5:0d:00:74 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.6 tell 192.168.0.1, length 46

But from what I can see, you never reply. Maybe as you're on Sky broadband, your machine is anti Murdoch..?

So, why isn't your box replying to the ARP requests? is iptables blocking them somehow? Sounds a bit nutty to me, but let's see what "iptables -vnL" says, maybe there's something really odd there. Could there be a different device also on that IP? a smartphone or console? maybe try changing the IP to something different, like 192.168.0.123, leaving the other settings as they are.

to check for duplicated addresses, try a "arping -D 192.168.0.6" maybe something else will show up that way.

Last edited by acid_kewpie; 07-04-2013 at 07:47 AM.
 
Old 07-04-2013, 08:10 AM   #5
sparkinson
LQ Newbie
 
Registered: Jul 2013
Posts: 5

Original Poster
Rep: Reputation: Disabled
Yes, it's like every local ip is getting routed back to the computer itself. When I ssh out to another computer it logs me back into the computer I am ssh'ing from.

I also have apache2 installed. I have been stopping this as I thought it may be causing issues. But when I have it running and I try to go to my router's ip, 192.168.0.1, in the browser, it brings up the website hosted by the apache server.

Anyway, the output from "iptables -vnL" says
Code:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
and from "arping -D 192.168.0.6" return not a lot
Code:
ARPING 192.168.0.6 from 0.0.0.0 eth0
Sent 39 probes (39 broadcast(s))
Received 0 response(s)
 
Old 07-04-2013, 08:11 AM   #6
sparkinson
LQ Newbie
 
Registered: Jul 2013
Posts: 5

Original Poster
Rep: Reputation: Disabled
Oh, and I checked that nothing else is using the ip. I have 4 devices connected to the router and none of them are using that ip address.
 
Old 07-04-2013, 08:42 AM   #7
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,373

Rep: Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962
have you tried changing the IP? Maybe try a gratuitous arp as in the "workaround" here....

http://alpacapowered.wordpress.com/2...ith-subnet-ip/
 
Old 07-04-2013, 08:46 AM   #8
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,373

Rep: Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962Reputation: 1962
does this look at all familiar? https://bugs.launchpad.net/ubuntu/+s...wl/+bug/414724 Different driver, but the trick they discuss might shed some light on your situation.
 
Old 07-04-2013, 10:04 AM   #9
MikeDeltaBrown
Member
 
Registered: Apr 2013
Location: Arlington, WA
Distribution: Slackware
Posts: 44

Rep: Reputation: 5
There are some odd things happening, for sure.

Does the router have any Port Forwarding rules that point to 192.168.0.6? Maybe that's misconfigured.

It appears that your computer thinks it owns 192.168.0.1 ... let's try this:
ifconfig lo # the loopback interface; write down the number of packets RX'd and TX'd
ping -f 192.168.0.1 # flood ping the IP address for about 10 seconds....
# ... You may have to use `sudo ping -f 192.168.0.1`
<ctrl>-c # to stop the flood ping
ifconfig lo # compare the number of TX'd and RX'd packets

Any packets from the local machine to the local machine will go through the loopback interface (lo). If you see a large increase in packets as a result of this test then the local machine thinks it owns 192.168.0.1 and is routing the packets through the loopback interface. On my machine this test incremented the RX and TX counter by about 2 million in 10 seconds.

If this happens with yours, 192.168.0.1 _should_ show up in the output of `ifconfig -a`, but it doesn't... weird.

Try the ping test that Acid-Kewpie suggests but this time monitor the loopback interface:
"tcpdump -i lo -ven"

The output from "tcpdump -i eth0 -ven" above doesn't necessarily mean the router is asking for computer "A"s IP because of the ping. It may be looking for it for another reason, such as port-forwarding or nameserver replies. We should see the icmp echo request first, but we're not, so I don't think the "who-has X tell Y" lines are due to the ping. It does appear that the default route is working because we see nameserver queries going out:
" .... 192.168.0.6.48804 > 208.67.222.222.53: ...." that's probably what the arp-requests are from.

Your resolv.conf file should lose the "nameserver 127.0.1.1" line. This would only be valid if you have a nameserver configured and running on the local machine and you corrected the typo and made the entry "nameserver 127.0.0.1"

Does computer A get it's network config via DHCP or statically?
Are you mapping 00:15:60:cb:dd:3c to 192.168.0.6 in the router's DHCP?

Last edited by MikeDeltaBrown; 07-05-2013 at 09:49 AM. Reason: Removed double post.
 
Old 07-04-2013, 10:11 AM   #10
sparkinson
LQ Newbie
 
Registered: Jul 2013
Posts: 5

Original Poster
Rep: Reputation: Disabled
Hi Mike,

So there are no port forwarding rules for 192.168.0.6.

when I do the loopback test you described I do indeed see a large increase in TX'd and RX'd packets, about 20MB in 5 seconds.

Now some output from "tcpdump -i lo -ven"
Code:
16:22:12.871585 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 50746, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.58356 > 192.168.0.1.53: 32565+ A? daisy.ubuntu.com.Home. (39)
16:22:12.871620 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51424, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 50746, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.58356 > 192.168.0.1.53: 32565+ A? daisy.ubuntu.com.Home. (39)
16:22:12.871650 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 50747, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.58356 > 192.168.0.1.53: 10484+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:12.871664 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51425, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 50747, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.58356 > 192.168.0.1.53: 10484+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:12.871711 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 50746, offset 0, flags [DF], proto UDP (17), length 67)
    127.0.0.1.56130 > 127.0.1.1.53: 32565+ A? daisy.ubuntu.com.Home. (39)
16:22:12.871738 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 50747, offset 0, flags [DF], proto UDP (17), length 67)
    127.0.0.1.56130 > 127.0.1.1.53: 10484+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:12.871898 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.20713 > 192.168.0.1.53: 1935+ A? daisy.ubuntu.com.Home. (39)
16:22:12.871913 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51426, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.20713 > 192.168.0.1.53: 1935+ A? daisy.ubuntu.com.Home. (39)
16:22:12.871975 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.37216 > 192.168.0.1.53: 3263+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:12.871988 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51427, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.37216 > 192.168.0.1.53: 3263+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:13.632003 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 50936, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.57119 > 192.168.0.1.53: 37629+ A? client-lb.dropbox.com. (39)
16:22:13.632035 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51428, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 50936, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.57119 > 192.168.0.1.53: 37629+ A? client-lb.dropbox.com. (39)
16:22:13.632115 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 50936, offset 0, flags [DF], proto UDP (17), length 67)
    127.0.0.1.35718 > 127.0.1.1.53: 37629+ A? client-lb.dropbox.com. (39)
16:22:13.632262 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.51721 > 192.168.0.1.53: 60476+ A? client-lb.dropbox.com. (39)
16:22:13.632278 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51429, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.51721 > 192.168.0.1.53: 60476+ A? client-lb.dropbox.com. (39)
16:22:20.452110 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 52641, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.51097 > 192.168.0.1.53: 9585+ A? videosearch.ubuntu.com.Home. (45)
16:22:20.452144 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 115: (tos 0xc0, ttl 64, id 51430, offset 0, flags [none], proto ICMP (1), length 101)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 81
	(tos 0x0, ttl 64, id 52641, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.51097 > 192.168.0.1.53: 9585+ A? videosearch.ubuntu.com.Home. (45)
16:22:20.452175 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 52642, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.51097 > 192.168.0.1.53: 27907+ AAAA? videosearch.ubuntu.com.Home. (45)
16:22:20.452189 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 115: (tos 0xc0, ttl 64, id 51431, offset 0, flags [none], proto ICMP (1), length 101)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 81
	(tos 0x0, ttl 64, id 52642, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.51097 > 192.168.0.1.53: 27907+ AAAA? videosearch.ubuntu.com.Home. (45)
16:22:20.452237 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 52641, offset 0, flags [DF], proto UDP (17), length 73)
    127.0.0.1.40000 > 127.0.1.1.53: 9585+ A? videosearch.ubuntu.com.Home. (45)
16:22:20.452263 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 52642, offset 0, flags [DF], proto UDP (17), length 73)
    127.0.0.1.40000 > 127.0.1.1.53: 27907+ AAAA? videosearch.ubuntu.com.Home. (45)
16:22:20.452422 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.17624 > 192.168.0.1.53: 38904+ A? videosearch.ubuntu.com.Home. (45)
16:22:20.452438 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 115: (tos 0xc0, ttl 64, id 51432, offset 0, flags [none], proto ICMP (1), length 101)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 81
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.17624 > 192.168.0.1.53: 38904+ A? videosearch.ubuntu.com.Home. (45)
16:22:20.452504 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.1835 > 192.168.0.1.53: 8920+ AAAA? videosearch.ubuntu.com.Home. (45)
16:22:20.452518 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 115: (tos 0xc0, ttl 64, id 51433, offset 0, flags [none], proto ICMP (1), length 101)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 81
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 73)
    192.168.0.100.1835 > 192.168.0.1.53: 8920+ AAAA? videosearch.ubuntu.com.Home. (45)
16:22:21.880983 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 52998, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.57067 > 192.168.0.1.53: 32565+ A? daisy.ubuntu.com.Home. (39)
16:22:21.881016 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51434, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 52998, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.57067 > 192.168.0.1.53: 32565+ A? daisy.ubuntu.com.Home. (39)
16:22:21.881046 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 52999, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.57067 > 192.168.0.1.53: 10484+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:21.881059 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51435, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 52999, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.57067 > 192.168.0.1.53: 10484+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:21.881132 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 52998, offset 0, flags [DF], proto UDP (17), length 67)
    127.0.0.1.56859 > 127.0.1.1.53: 32565+ A? daisy.ubuntu.com.Home. (39)
16:22:21.881161 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 52999, offset 0, flags [DF], proto UDP (17), length 67)
    127.0.0.1.56859 > 127.0.1.1.53: 10484+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:21.881288 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.50105 > 192.168.0.1.53: 58638+ A? daisy.ubuntu.com.Home. (39)
16:22:21.881302 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51436, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.50105 > 192.168.0.1.53: 58638+ A? daisy.ubuntu.com.Home. (39)
16:22:21.881374 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.3571 > 192.168.0.1.53: 11445+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:21.881389 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 109: (tos 0xc0, ttl 64, id 51437, offset 0, flags [none], proto ICMP (1), length 95)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 75
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 67)
    192.168.0.100.3571 > 192.168.0.1.53: 11445+ AAAA? daisy.ubuntu.com.Home. (39)
16:22:22.241487 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 73: (tos 0x0, ttl 64, id 53088, offset 0, flags [DF], proto UDP (17), length 59)
    192.168.0.100.35473 > 192.168.0.1.53: 61393+ A? d.dropbox.com. (31)
16:22:22.241521 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 101: (tos 0xc0, ttl 64, id 51438, offset 0, flags [none], proto ICMP (1), length 87)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 67
	(tos 0x0, ttl 64, id 53088, offset 0, flags [DF], proto UDP (17), length 59)
    192.168.0.100.35473 > 192.168.0.1.53: 61393+ A? d.dropbox.com. (31)
16:22:22.241584 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 73: (tos 0x0, ttl 64, id 53088, offset 0, flags [DF], proto UDP (17), length 59)
    127.0.0.1.35841 > 127.0.1.1.53: 61393+ A? d.dropbox.com. (31)
16:22:22.241769 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 73: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 59)
    192.168.0.100.56538 > 192.168.0.1.53: 60697+ A? d.dropbox.com. (31)
16:22:22.241791 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 101: (tos 0xc0, ttl 64, id 51439, offset 0, flags [none], proto ICMP (1), length 87)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 67
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 59)
    192.168.0.100.56538 > 192.168.0.1.53: 60697+ A? d.dropbox.com. (31)
16:22:22.641382 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 86: (tos 0x0, ttl 64, id 53188, offset 0, flags [DF], proto UDP (17), length 72)
    192.168.0.100.55708 > 192.168.0.1.53: 16821+ A? client-lb.dropbox.com.Home. (44)
16:22:22.641408 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 114: (tos 0xc0, ttl 64, id 51440, offset 0, flags [none], proto ICMP (1), length 100)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 80
	(tos 0x0, ttl 64, id 53188, offset 0, flags [DF], proto UDP (17), length 72)
    192.168.0.100.55708 > 192.168.0.1.53: 16821+ A? client-lb.dropbox.com.Home. (44)
16:22:22.641455 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 86: (tos 0x0, ttl 64, id 53188, offset 0, flags [DF], proto UDP (17), length 72)
    127.0.0.1.46753 > 127.0.1.1.53: 16821+ A? client-lb.dropbox.com.Home. (44)
16:22:22.641579 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 86: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 72)
    192.168.0.100.23228 > 192.168.0.1.53: 21013+ A? client-lb.dropbox.com.Home. (44)
16:22:22.641595 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 114: (tos 0xc0, ttl 64, id 51441, offset 0, flags [none], proto ICMP (1), length 100)
    192.168.0.1 > 192.168.0.100: ICMP 192.168.0.1 udp port 53 unreachable, length 80
	(tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 72)
    192.168.0.100.23228 > 192.168.0.1.53: 21013+ A? client-lb.dropbox.com.Home. (44)
Finally, the computer is obtaining its address dynamically. It was originally static, on 192.168.0.100 which had firewall rules set on the router to allow ssh and http connections, but I changed this whilst trying to get it to work again.

Thanks for the help

Last edited by sparkinson; 07-04-2013 at 10:30 AM. Reason: added more info
 
Old 07-05-2013, 09:54 AM   #11
MikeDeltaBrown
Member
 
Registered: Apr 2013
Location: Arlington, WA
Distribution: Slackware
Posts: 44

Rep: Reputation: 5
OK, it looks like there is something running on your machine that is configured as 192.168.0.1.

Do you have any Virtual Machine software running like VMWare, VirtualBox, or Parallels? If so, one of the clients may have its virtual interface bridged with Computer A's and configured with the same IP address as your router.

Also, you still have "nameserver 127.0.1.1" in your /etc/resolv.conf. That needs to go away.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Connect to Network (can ping router) but can't access the Internet DGrieve Linux - Networking 9 04-02-2014 07:47 AM
Can ping server, can't SSH. No internet access. kaempfer0080 Linux - Networking 3 01-15-2013 07:50 AM
New 2.6.29.4-167.fc11.i586 Can access Internet and ping router -not Internal hosts? gdotoli Linux - Networking 5 11-05-2009 01:14 PM
NIC Not Working In 10.1 - Cannot Ping Router, Access Internet contillion Suse/Novell 6 09-08-2006 02:46 PM
Connected to router,but not able to access internet. JAKK Linux - Networking 5 06-14-2006 07:37 AM


All times are GMT -5. The time now is 05:55 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration