Internet connections at work won't work!

aaa

New Member
Joined
Aug 28, 2017
Messages
2
Reaction score
3
Credits
0
Hello,

My Debian 9.1 stretch connects flawlessly, both through ethernet and wi-fi everywhere BUT at my work. I'm guessing they are using a particular set-up, but can't work it out.
I have three options available :
a) Wifi
b) Ethernet port in my wall
c) Ethernet port in my phone.

Options a) and c) works from windows (option b) does not, oddly enough)

a) Wifi

When I try to connect to the wifi (let's call is SSID), I'm prompted with

Password dialog - Kde daemon
For accessing the wireless network 'SSID' you need to provide a password below

I enter my password, wait a bit, and am prompted with the same dialog box. After some back and forth, a dialog box pops up with

Wireless Interface (wlp2s0)
No secrets were provided
and
SSID
Connection 'SSID' deactivated

dmesg:

Code:
[ 1009.127464] wlp2s0: authenticate with f0:7f:06:da:94:3f
[ 1009.190973] wlp2s0: send auth to f0:7f:06:da:94:3f (try 1/3)
[ 1009.192229] wlp2s0: authenticated
[ 1009.196337] wlp2s0: associate with f0:7f:06:da:94:3f (try 1/3)
[ 1009.300400] wlp2s0: associate with f0:7f:06:da:94:3f (try 2/3)
[ 1009.404404] wlp2s0: associate with f0:7f:06:da:94:3f (try 3/3)
[ 1009.508379] wlp2s0: association with f0:7f:06:da:94:3f timed out
[ 1012.380801] usblp0: removed
[ 1012.380823] Did not find alt setting 1 for intf 0, config 1
......
[ 1115.652801] wlp2s0: send auth to f0:7f:06:eb:d6:cf (try 1/3)
[ 1115.653516] wlp2s0: authenticated
[ 1115.667783] wlp2s0: associate with f0:7f:06:eb:d6:cf (try 1/3)
[ 1115.771812] wlp2s0: associate with f0:7f:06:eb:d6:cf (try 2/3)
[ 1115.875841] wlp2s0: associate with f0:7f:06:eb:d6:cf (try 3/3)
[ 1115.979821] wlp2s0: association with f0:7f:06:eb:d6:cf timed out
[ 1126.007964] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1126.022723] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

ifconfig:

Code:
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether a4:4c:c8:11:67:6c  txqueuelen 1000  (Ethernet)
        RX packets 4761  bytes 2270236 (2.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1865  bytes 180473 (176.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xef300000-ef320000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 855  bytes 69551 (67.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 855  bytes 69551 (67.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 02:23:49:72:f6:5c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

b) Ethernet port in my wall

Whenver I try to connect, I get two notification windows:

New 802-3-ethernet connection
Connection 'New 802-3-ethernet connection' deactivated

and

Wired Interface (enp0s31f6)
IP configuration was unavailable

dmesg

Code:
[ 1383.674579] e1000e: enp0s31f6 NIC Link is Down
[ 1393.428585] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 1454.119478] atkbd serio0: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0).
[ 1454.119485] atkbd serio0: Use 'setkeycodes e008 <keycode>' to make it known.
[ 1454.198076] dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
[ 1467.018268] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1473.688374] atkbd serio0: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0).
[ 1473.688381] atkbd serio0: Use 'setkeycodes e008 <keycode>' to make it known.
[ 1473.772533] dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

dhclient -v

Code:
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlp2s0/7e:04:fd:fb:5b:45
Sending on   LPF/wlp2s0/7e:04:fd:fb:5b:45
Listening on LPF/enp0s31f6/a4:4c:c8:11:67:6c
Sending on   LPF/enp0s31f6/a4:4c:c8:11:67:6c
Sending on   Socket/fallback
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlp2s0 interface.
DHCPREQUEST of 10.3.1.11 on enp0s31f6 to 255.255.255.255 port 67
receive_packet failed on wlp2s0: Network is down
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlp2s0 interface.
DHCPREQUEST of 10.3.1.11 on enp0s31f6 to 255.255.255.255 port 67
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 19
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlp2s0 interface.
DHCPDISCOVER on enp0s31f6 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on enp0s31f6 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on enp0s31f6 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 18
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlp2s0 interface.
DHCPDISCOVER on enp0s31f6 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlp2s0 interface.
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

systemctl status networking.service
Code:
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-08-28 12:24:36 EDT; 37min ago
     Docs: man:interfaces(5)
  Process: 626 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 268 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exi
 Main PID: 626 (code=exited, status=1/FAILURE)

Aug 28 12:24:36 debian ifup[626]: than a configuration issue please read the section on submitting
Aug 28 12:24:36 debian ifup[626]: bugs on either our web page at www.isc.org or in the README file
Aug 28 12:24:36 debian ifup[626]: before submitting a bug.  These pages explain the proper
Aug 28 12:24:36 debian ifup[626]: process and the information we find helpful for debugging..
Aug 28 12:24:36 debian ifup[626]: exiting.
Aug 28 12:24:36 debian ifup[626]: ifup: failed to bring up eth0
Aug 28 12:24:36 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Aug 28 12:24:36 debian systemd[1]: Failed to start Raise network interfaces.
Aug 28 12:24:36 debian systemd[1]: networking.service: Unit entered failed state.
Aug 28 12:24:36 debian systemd[1]: networking.service: Failed with result 'exit-code'.

c) Ethernet through the phone

The phone is a Cisco phone (VLAN) -- UC Phone CP-7841, there is an ethernet port on it.
The computer connects flawlessly, but can't access anything:

ping 8.8.8.8
Code:
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C--- 8.8.8.8 ping statistics ---
218 packets transmitted, 0 packets received, 100% packet loss

dhclient -v

Code:
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlp2s0/7e:04:fd:fb:5b:45
Sending on   LPF/wlp2s0/7e:04:fd:fb:5b:45
Listening on LPF/enp0s31f6/a4:4c:c8:11:67:6c
Sending on   LPF/enp0s31f6/a4:4c:c8:11:67:6c
Sending on   Socket/fallback
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlp2s0 interface.
DHCPREQUEST of 10.3.1.11 on enp0s31f6 to 255.255.255.255 port 67
receive_packet failed on wlp2s0: Network is down
DHCPACK of 10.3.1.11 from 10.3.0.1
RTNETLINK answers: File exists
bound to 10.3.1.11 -- renewal in 350271 seconds.

route -n

Code:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.3.0.1        0.0.0.0         UG    0      0        0 enp0s31f6
0.0.0.0         10.3.0.1        0.0.0.0         UG    100    0        0 enp0s31f6
10.3.0.0        0.0.0.0         255.255.254.0   U     100    0        0 enp0s31f6
10.9.14.10      10.3.0.1        255.255.255.255 UGH   100    0        0 enp0s31f6
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 enp0s31f6


Additional information:

/etc/network/interfaces

Code:
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback

/etc/network/interfaces.d/setup

Code:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
 


Hi @aaa and a hearty Welcome to linux.org.

A fair bit of this may be beyond my pay grade, but I guess a couple of obvious questions for others to assist might include:

  1. Are you allowed to access your work's internet? and
  2. What medium are you using with your Stretch in terms of its housing unit - is it a laptop, a tablet, a phone?
Cheers and good luck

Wizard
 
Thanks for your kind words.
It looks indeed like the restriction came from the (really odd) way the access to Internet was restricted at my work.

Thanks for the insight and the welcoming words.
 
Is work a windows environment? They might be doing domain authentication and since your linux is not part of the domain it isn't allowed to use the internet.
 

Members online


Top