The computer in question has a Linux SO and is connected to a local network that has DHCP service active. I configured a public ip address to be given to that computer by the DHCP and I can ssh into it using this ip address. Now comes the weird part.
ifconfig returns a 169.254.x.x address. I have read that 169.254.x.x is given to a computer when DHCP fails to give it a proper address. But it did give a proper address, I can ssh to it (using the public IP address) and sites as http://www.whatsmyip.org/ tell me the computer has the public ip address I configured on the DHCP.
How can this be possible and what details should I include in this post?
When I asked my colleague to restart his network
this was his output:
* Caching service dependencies ... [ ok ] * Unmounting network filesystems ... [ ok ] * Bringing down interface eth0 * Stopping dhcpcd on eth0 ... [ ok ] * Bringing up interface eth0 * dhcp ... * Running dhcpcd ... control_open: Connection refused eth0: adding address fe80::f85f:1ef7:db63:7475 eth0: waiting for carrier eth0: carrier acquired DUID 00:01:00:01:1b:ef:52:ea:dc:85:de:20:38:fa eth0: IAID a9:04:2c:82 eth0: soliciting an IPv6 router eth0: rebinding lease of 22.214.171.124 eth0: probing for an IPv4LL address eth0: DHCP lease expired eth0: soliciting a DHCP lease eth0: using IPv4LL address 169.254.78.15 eth0: adding route to 169.254.0.0/16 forked to background, child pid 6332 [ ok ] * received address 169.254.78.15/16 [ ok ] * Mounting network filesystems ...
The output of
ifconfig is as follows:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 169.254.78.15 netmask 255.255.0.0 broadcast 169.254.255.255 inet6 fe80::f85f:1ef7:db63:7475 prefixlen 64 scopeid 0x20<link> ether 48:85:a3:04:2d:81 txqueuelen 1000 (Ethernet) RX packets 113090 bytes 80195148 (76.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 39425 bytes 7462270 (7.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 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 0 (Local Loopback) RX packets 2259 bytes 217008 (211.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2259 bytes 217008 (211.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether df:83:de:11:37:fb 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
ip addr shows both IPs, 169.x.x.x and 193.x.x.x. Still haven't discover why 169.x.x.x is given by DHCP server.