On Mon, 30 May 2016 at 04:21, S. P. Molnar <s.mol...@sbcglobal.net> wrote:

> I am running Debian v-8.4.0 and have encountered a problem with my
> internet connection.  I duid a fresh reinstall after the computer
> crashed due to fan failure about a month ago.  I automatically set up
> the internet connection during the installation and it worked until
> several days ago when I had need to reboot the system.
>
> Now, however, the internet connection is not started on booting the
> system and it is necessart to run 'dhclient eth0' as root.
>
> ifconfig returns:
>
> root@AbNormal:/home/comp# ifconfig
> eth0      Link encap:Ethernet  HWaddr bc:ee:7b:5e:83:36
>            inet addr:192.168.1.116  Bcast:192.168.1.255 Mask:255.255.255.0
>            inet6 addr: 2602:306:bcd2:41d0:beee:7bff:fe5e:8336/64
> Scope:Global
>            inet6 addr: fe80::beee:7bff:fe5e:8336/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:5314 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:1994 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:2035132 (1.9 MiB)  TX bytes:242660 (236.9 KiB)
>
> 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:88 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>            RX bytes:20113 (19.6 KiB)  TX bytes:20113 (19.6 KiB)
>
> vmnet1    Link encap:Ethernet  HWaddr 00:50:56:c0:00:01
>            inet addr:172.16.96.1  Bcast:172.16.96.255 Mask:255.255.255.0
>            inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> vmnet8    Link encap:Ethernet  HWaddr 00:50:56:c0:00:08
>            inet addr:172.16.221.1  Bcast:172.16.221.255 Mask:255.255.255.0
>            inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> Further, /etc/NetworkManager/system-connections/Wired Connection 1 is:
>
>
> [connection]
> id=Wired connection 1
> uuid=53ac3b1f-4121-41d3-a303-45b1b75577e9
> type=802-3-ethernet
>
> [802-3-ethernet]
>
> [ipv4]
> method=auto
>
> [ipv6]
> method=auto
> ip6-privacy=2
>
> I am, however, loathe to edit the file as I don't know what I would be
> doing.
>
> A solution to the problem would be much appreciated as my wife uses to
> compute for Ebay
>
> Thanks in advance.
>
> --
> Stephen P. Molnar, Ph.D.        Life is a fuzzy set
> www.Molecular-Modeling.net      Stochastic and multivariate
> (614)312-7528 (c)
> Skype:  smolnar1
>
>
It sounds like either dhclient is not running as part of your boot process,
or it's running too early in the boot process.

Since you mentioned you are running 8.4, which is Jessie, I assume you are
running systemd. That being the case, run as root:
journalctl -b > log.txt
And post it somewhere we can see (it could be long) so we can see what
happens when / if dhclient is run at boot. You may want to look through the
log for dhclient relevant stuff if you don't want to post the whole thing,
or go through it removing personal stuff eg fixed ip addresses, as posting
the contents of the boot log can sometimes be a security risk.

Mark

Reply via email to