[SOLVED] Can't configure new Actiontec wireless NDSL modem/router on Dell Linux mint 18 cinnamon.

Zupe · 01-13-2017, 05:14 PM

WHEN i asked the terminal window
dhcclient eth0 -vv it said
Usage: client [-4|-6][-SNTPI1dvrxi] [-nw] [-p <port>] [-D LL|LLT]
[-s server-addr] [ -cf config-file]
[-df duid-file] [-lf lease-file]
[--pf pid-file] [--no-pid] [-e VAR=val]
[-sf script-file] [interface]

TheEzekielProject · 01-13-2017, 05:18 PM

Quote:

Originally Posted by Zupe

TEP
I did as you suggested on two speparate commends First Command not found and on second the execute operation it said Failed to execute operation: No such file or directory found

Are you referring to

Code:

sudo systemctl start dhclient@eth0.service
sudo systemctl enable dhclient@eth0.service

as returning

Code:

Command not found

and

Code:

Failed to execute operation: No such file or directory found?

And did you try

Code:

dhclient eth0 -vv

?

This is peculiar. Normally with a wired connection, on a fresh install, you should only need to execute

Code:

ip link set eth0 up

and

Code:

 dhclient eth0

which should get you connected
Please post the output of

Code:

ip a

Zupe · 01-13-2017, 05:20 PM

Jeremy
I did find IPv4 when I right clicked on 'the wired connection 1'
under IPv4 addresses it was set to automatic (DHCP) and 'on'
other choices are manual link-local Only and Shared to other Computers

Zupe · 01-13-2017, 05:35 PM

ip a ooo its a lot so wait for it
l: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default glen 1
link/look back 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 :: 1/128 scope host
valid_lft forever preferred_lft forever

2. enol: <BROADCAST, MULTICAST, UP, LOWER_up> mtu 1500 qdisc pfifo_fast state UP group default glen 1000
link ether 5c:26:0a:88:d0:f9 brd ff:ff:ff:ff:ff:ff:ff:ff
3.wlp2s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default glen 1000
link/ether 08:11:96:85:f6:f4: brd ff:ff:ff:ff:ff:ff:ff

TheEzekielProject · 01-13-2017, 05:37 PM

It appears your ethernet interface is

Code:

enol

rather than eth0
Please try

Code:

ip link set enol up
dhclient enol
ping -c 3 www.google.com

Zupe · 01-13-2017, 05:42 PM

The EzekielProject
from your earlier post asking me to put ip link set eth0 up
I got
Cannot find device "eth0" (a I am using a zero)
same result for dhclient eth0

okay I will try thAT NEW COMMAND

TheEzekielProject · 01-13-2017, 05:43 PM

Please see post #50

Zupe · 01-13-2017, 05:44 PM

i GET CANNOT FIND DEVICE "enol"

Zupe · 01-13-2017, 05:47 PM

I get
No command 'enol found did you mean Cammand 'znol'
from package 'zephr-clients' (universe)
enol command not found

Zupe · 01-13-2017, 05:48 PM

Is that eno all letters then a l or a 1?
well for the record I tried enol eno1 en01(number) en0l(letter)

TheEzekielProject · 01-13-2017, 05:52 PM

That is information that you posted from the command

Code:

ip a

Please see bolded below

Quote:

2. enol: <BROADCAST, MULTICAST, UP, LOWER_up> mtu 1500 qdisc pfifo_fast state UP group default glen 1000
link ether 5c:26:0a:88:d0:f9 brd ff:ff:ff:ff:ff:ff:ff:ff
3.wlp2s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default glen 1000
link/ether 08:11:96:85:f6:f4: brd ff:ff:ff:ff:ff:ff:ff
windows_vista Zupe is online now Add to Zupe's Reputation

To avoid errors, you might copy/paste the device name from your own terminal output

Zupe · 01-13-2017, 05:59 PM

well Dear Ezekiel I am getting pretty tired. I REALLY appreciate your help.

I had renewed the terminal window because it just started putting > along the edge and I can' tell if the enol was a mistake in typing or not. I did try that command with every combination of e, n o or 0 and 1 or l

Its funny they look different when typed from when the 1 or l are posted

Zupe · 01-13-2017, 06:07 PM

I can not cut and paste. Believe me I would LOVE not to type all this out.

Zupe · 01-13-2017, 06:10 PM

I am going to leave now. I will work on a reinstall tomorrow or maybe chuck the laptop out the window onto the driveway... repeatedly.

thanks to both of you.

TheEzekielProject · 01-13-2017, 06:17 PM

The next time you have a terminal do that, ctrl+c should get you out.
For the majority of this troubleshooting we've been applying our efforts to a device that doesn't exist on your system (eth0). This is one downside of transcribing terminal output.
In post #3, you say the output of

Code:

ifconfig

is

Quote:

I couldn't cut and paste because I can't get online but I copied your message and changed what was different. Gosh what big numbers you have Jeremy!

eth0 Link encap:Ethernet HWaddr 5c:26:0a:88:d0:f9
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrical
RX packets:3 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:573(573.0 MiB) TX bytes:0 (0.0B)
Interrupt:20 Memory:e2e00000-e2e20000

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:376 errors:0 dropped:0 overruns:0 frame:0
TX packets:376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:30240 (30.2 KB) TX bytes:30240 (30.2 KB)

as that is a very common device name, I didn't really question it.

But in post #49, you say the out output of

Code:

ip a

is

Quote:

l: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default glen 1
link/look back 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 :: 1/128 scope host
valid_lft forever preferred_lft forever

2. enol: <BROADCAST, MULTICAST, UP, LOWER_up> mtu 1500 qdisc pfifo_fast state UP group default glen 1000
link ether 5c:26:0a:88:d0:f9 brd ff:ff:ff:ff:ff:ff:ff:ff
3.wlp2s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default glen 1000
link/ether 08:11:96:85:f6:f4: brd ff:ff:ff:ff:ff:ff:ff

Ideally, you should have "eth0" OR "enol" in the output of both "ip a" and "ifconfig"; they shouldn't differ. Assuming "enol" is actually your network interface, rather than "eth0" (which is confirmed by the "device not found" errors you posted about earlier. We've targeting the wrong, nonexistent device.

If you were to once again

Code:

ip a

and with your mouse, highlight and right click to copy the device name that you earlier transcribed as "enol", then type

Code:

dhclient right click and paste device name here

I'm fairly confident you will be connected