Announcement

Collapse
No announcement yet.

can't see local network, internet is fine

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    can't see local network, internet is fine

    My upgrade went well until I tried to access the other machines on my network. I can't ping anything inside my network. The internet is fine and I can ping both by address and name as long as it's not in the 192.168.1.x range. I can get out using my router at 192.168.1.1 but I can't ping it and my browser can't establish a connection to it. It almost sounds like a firewall problem but I've confirmed that ufw is unloaded.

    Any help would be appreciated.
    Thanks
    Mark

    xxx:~$ dmesg | grep eth0
    [ 2.064415] forcedeth 0000:00:08.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:1d:7d:9f:cc:5e
    [ 34.144014] eth0: no IPv6 routers present
    [11822.334790] eth0: link down.
    [12013.764330] eth0: link up.
    [12089.045023] eth0: no IPv6 routers present

    xxx:~$ cat /etc/hosts
    127.0.0.1 localhost
    127.0.1.1 server-jan2008

    # The following lines are desirable for IPv6 capable hosts
    ::1 ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    ff02::3 ip6-allhosts


    xxx:~$ ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:1d:7d:9f:cc:5e
    inet addr:192.168.1.92 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::21d:7dff:fe9f:cc5e/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:573391 errors:0 dropped:0 overruns:0 frame:0
    TX packets:370738 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:90649476 (90.6 MB) TX bytes:1139895802 (1.1 GB)
    Interrupt:254 Base address:0x4000

    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:16436 Metric:1
    RX packets:6756 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6756 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2018073 (2.0 MB) TX bytes:2018073 (2.0 MB)

    pan0 Link encap:Ethernet HWaddr 76:88:ed:5c:ae:3c
    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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    wlan0 Link encap:Ethernet HWaddr 00:d0:41:ad:47:04
    inet addr:192.168.1.91 Bcast:192.168.1.255 Mask:255.255.255.0
    UP 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)

    wmaster0 Link encap:UNSPEC HWaddr 00-D0-41-AD-47-04-00-00-00-00-00-00-00-00-00-00
    UP BROADCAST RUNNING 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)

    #2
    Re: can't see local network, internet is fine

    Hi mark,

    Your output shows that both your wired (eth0) and wireless (wlan0) interfaces are active with IP addresses in the same subnet (192.168.1.0/24)

    It has been my experience that *sometimes* the routing will become confused IF you have 2 interfaces on the SAME computer in the SAME subnet.

    I notice that you are primarily using your wired connection. Maybe try to disable your wireless, leave your wired on, and see how that goes. You *may* need to disable wireless and reboot (without the wireless getting an IP) because sometimes even just disabling the interface is not good enough as the routing/arp tables will still remember it.
    Confucius says: If you enjoy your work, then you never have to work another day in your life.

    Comment


      #3
      Re: can't see local network, internet is fine

      Yes, I disabled the wifi in the bios and it works. The wifi must not be supported, yet. I'll try again in a couple of weeks.

      Comment

      Working...
      X