New subject: att-uverse new, can't access internet

5 Oct 2012


      Terry Polzin responded:
...
Does the time stamp on the /etc/resolv.conf correspond to the times of
your reboots?
...
Could you kindly detail your new equipment with some photographs so we
all might see what these devices look like.  Be sure to include
close-ups of any labels on the devices.
---
time stamp of /etc/resolv.conf on f16 is oct4... consistent with
last boot of f16
I am not proficient with cameras of any type.
Also leery of too much pushing around that jumble of
equipment.  Will get down there again and see if can get
better description.
Might be able to get att on phone to
tell me what was put in, but our experience on the phone is not good.
----------------------------------------------------------------------------
Robert Locke  responded:
...
You have hit the nail on the head. Your iMac is configured for DHCP and
was working, but your F16 box is configured for static addressing that
does not match what the "new router" is willing to accept.
...
So, since you have the ifcfg-eth0 file available, edit the file and
change the following line:
...
BOOTPROTO=static
...
to
...
BOOTPROTO=dhcp
...
You can also safely remove the lines:
...
IPADDR=192.168.2.8
NETMASK=255.255.255.0
NETWORK=192.168.2.0
GATEWAY=192.168.2.1
DNS1=206.13.31.12
DNS2=68.94.156.1
DOMAIN=pacbell.net
...
which contain the incorrect static settings.
...
-Rob
I hope this is it!
Still confused on this point:
the mixed system with 192.168.2.8 static on f16
and 192.168.1.0 network, dhcp, currently 192.168.1.71 on imac
was working fine on the old adsl pacbell modem.
So why can't  this new uverse also deal with that mix?
And I much prefer static IP for f16.
the network 192.168.2.0 is also
used in configs of [previously used]
   :linksys router
   :netgear wless access point,
both of which I would need to be working
if we have to give up uverse and go back to old adsl pacbell modem,
hopefully without reconfiguration of  the linksys, netgear.
(I forget completely just how to do that, web-based I think)
Instead of changing my f16 to dhcp,
would it be sufficient on f16
to keep my static config
but convert to 192.168.1.0 network?
[or even change the imac to 192.168.2.0?
probably don't want to mess with the imac
 since it has working internet with uverse]
Also we know those DNS1, DNS2 are valid
so I would prefer to keep those lines if possible.
not sure about
DOMAIN=pacbell.net
Am I not free to pick almost any name for DOMAIN?
FWIW, here is result of  'ifconfig -a'  from the imac:
bash-3.2$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:26:bb:58:4c:e2
        inet6 fe80::226:bbff:fe58:4ce2%en0 prefixlen 64 scopeid 0x4
        inet 192.168.1.71 netmask 0xffffff00 broadcast 192.168.1.255
        media: autoselect (100baseTX <full-duplex>)
        status: active
fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 4078
        lladdr 00:26:bb:ff:fe:58:4c:e2
        media: autoselect <full-duplex>
        status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether d4:9a:20:56:8a:2d
        media: autoselect (<unknown type>)
        status: inactive
bash-3.2$ ~~
thanks much for your response,  just maybe it can get the uverse going?
Jack

Re: att-uverse new, can't access internet