<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I recently helped with a network issue with another AT&T U-Verse
router and this might be related. It seems that the routers made by
Pace for AT&T does not know how to auto-negotiate correctly. It
will connect with some network devices but fail to connect on
others. For the specific issue I fixed, it was one of the Western
Digital My Cloud drives that would not connect to the any of the
four switch ports. On the router you can set auto/10/100;full/half
but none of those combinations work. The "cloud" drive worked at
his previous place, and worked if you connected via the Ethernet
port to the computer. AT&T's "fix" for this is to put a network
device (router/switch/hub) between the cloud and AT&T's router.
A little odd google-fu turned out that many people are having
auto-negotiating issues. From the threads it depends on the
intelligence level of the support person from AT&T and which
router then send you, if it will know how to deal with
auto-negotiation. I did read later that you could SSH into the
"cloud" drive and manually set the network settings on the
interface, but that would be difficult for my friend to undo/modify
later. It does know how to auto-negotiate between my friend's other
devices (blue-ray player, AppleTV {although I find it odd that the
new AppleTV would have just a 100-full network interface instead of
a 1G}), just not this drive.<br>
<br>
More digging shows that it could be the drivers for the Broadcomm
chipset but there is no ETA on when there will be a fix. How often
will auto-negotiate retry?<br>
<br>
Hope this helps.<br>
<br>
-Mic<br>
<br>
<br>
<br>
On 04/04/2016 01:48 PM, Matthew Campbell wrote:<br>
<span style="white-space: pre;">> Good afternoon, sorry to hear about the problems you are facing.
> Network problems are sometimes easy to fix, but intermittent problems
> can be a real bear to diagnose.
>
> If you have more modern Linux machines the command to list your current IP is:
>
> ip addr
>
> The older method to list all your interfaces (whether they are
> configured or not) use:
>
> ifconfig -a
>
> If you have any Windows boxes you can get their configuration with
>
> ipconfig /all
>
> Getting all the machine's current states is a start but you really
> want to figure out whether they are configured with a static address
> or if they are getting a connection automatically though DHCP. A
> likely problem may be that the uVerse guys installed a conflicting
> DHCP server in your house. If you have two servers handing out
> conflicting addresses you would see intermittent failures.
>
> Good luck!
>
> Matt
>
>
>
> ---------
> Matthew Campbell
> Storage and Cloud Strategy
> Office of the CTO
>
> Kaiser Permanente
> 99 S. Oakland
> Pasadena, CA 91101
>
> 626-564-7228 (office)
> 8-338-7228 (tie-line)
> 818-314-9897 (mobile phone)
> Green Center 3-North, 031W29
> ---------
> kp.org/thrive
>
>
> On Mon, Apr 4, 2016 at 12:28 PM, John Kreznar <a class="moz-txt-link-rfc2396E" href="mailto:jek@ininx.com"><jek@ininx.com></a> wrote:</span><br>
<blockquote type="cite">Hart Larry <a class="moz-txt-link-rfc2396E" href="mailto:chime@hubert-humphrey.com"><chime@hubert-humphrey.com></a>
writes:<br>
<br>
>>> ... can I manually change an ip address of the local
Debian machine?<br>
>>> And exactly what will I type?<br>
<br>
Assuming the ethernet device is eth0, type<br>
<br>
ifconfig eth0 <new-address> up<br>
<br>
where <new-address> is the intended new ip address, e.g.
192.168.1.9.<br>
<br>
A way to check whether the ethernet device is eth0 is to type
simply<br>
<br>
ifconfig<br>
<br>
Before and after changing the ip address, you might also type
simply<br>
<br>
route<br>
<br>
to confirm that the Debian kernel routing table correctly tracks
the<br>
change.<br>
<br>
<br>
>>> This machine is still running at 157 days.<br>
<br>
Triple-digit up-time! You must be doing something right.<br>
Congratulations!<br>
<br>
</blockquote>
<span style="white-space: pre;">>>
>>
>
></span><br>
<br>
<br>
</body>
</html>