name servers have nothing to do with anything when pinging with IP numbers.


On 5/19/2015 2:45 PM, William Hermans wrote:
> As an aside, is this in fact the problem, it would probably be listed
> as "nameserver 192.168.1.1" Which seems to be the default value as
> "shipped"
>
> On Tue, May 19, 2015 at 2:44 PM, William Hermans <yyrk...@gmail.com
> <mailto:yyrk...@gmail.com>> wrote:
>
>     But the network interface seems to be working fine.
>
>     What nameserver is listed in /etc/resolv.conf under "nameserver" ?
>     If it is different from your network, then you should probably
>     change it to be accurate.
>
>     Then try to ping local IPs again . . .
>
>     On Tue, May 19, 2015 at 1:56 PM, Robert Nelson
>     <robertcnel...@gmail.com <mailto:robertcnel...@gmail.com>> wrote:
>
>         On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski
>         <bril...@gmail.com <mailto:bril...@gmail.com>> wrote:
>         > Hi, first thank you for the response, here is the output
>         where the network
>         > did not work:
>         >
>         > root@beaglebone:~# dmesg | grep mdio
>         > [    1.040419] davinci_mdio 4a101000.mdio: davinci mdio
>         revision 1.6
>         > [    1.040439] davinci_mdio 4a101000.mdio: detected phy mask
>         fffffffb
>         > [    1.047217] libphy: 4a101000.mdio: probed
>         > [    1.047246] davinci_mdio 4a101000.mdio: phy[2]: device
>         4a101000.mdio:02,
>         > driver SMSC LAN8710/LAN8720
>
>         Humm, that is odd, it corrected for [phy mask fffffffb] with
>         [4a101000.mdio:02]
>
>         But it should have been phy[4]... [4a101000.mdio:04]
>
>         The math conversion in the phy search patch is:
>
>         phy_mask = fffffffb
>
>         for (i = 0; i < PHY_MAX_ADDR; i++) {
>               if ((phy_mask & (1 << i)) == 0) {
>                       addr = (u32) i;
>                       break;
>                }
>         }
>
>         Regards,
>
>         --
>         Robert Nelson
>         https://rcn-ee.com/
>
>         --
>         For more options, visit http://beagleboard.org/discuss
>         ---
>         You received this message because you are subscribed to the
>         Google Groups "BeagleBoard" group.
>         To unsubscribe from this group and stop receiving emails from
>         it, send an email to beagleboard+unsubscr...@googlegroups.com
>         <mailto:beagleboard%2bunsubscr...@googlegroups.com>.
>         For more options, visit https://groups.google.com/d/optout.
>
>
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard+unsubscr...@googlegroups.com
> <mailto:beagleboard+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to