cannot ssh into a box with DHCP assigned IP address

Anton Shterenlikht mexas at bristol.ac.uk
Wed Feb 20 15:03:26 UTC 2013


	Date: Wed, 20 Feb 2013 15:43:43 +0100
	From: Matthias Apitz <guru at unixarea.de>
	To: freebsd-questions at freebsd.org
	Subject: Re: cannot ssh into a box with DHCP assigned IP address

	> > I have on the problem box (ssh server):
	> > 
	> > wlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1
	> > 500
	> >        ether 00:21:5c:50:68:c3
	> >        inet 172.21.220.12 netmask 0xfffffc00 broadcast 255.255.255.255
	> >        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	> >        media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
	> >        status: associated
	> >        ssid eduroam channel 1 (2412 MHz 11g) bssid 00:3a:98:62:cd:a0
	> >        country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
	> >        AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 bmiss 10 scanvalid 450
	> >        bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5
	> >        protmode CTS wme roaming MANUAL
	> > 
	> > I'm trying to ssh from 137.222.187.241.

	The class B network 172.16.0.0 to 172.31.255.255 is not routed in
	Internet (see RFC1918). This is a so called "private addr" you get from
	your Access Point. It is hided by the AP (or by some other router more
	far away) behind a real IP addr. You can check what this addr is by
	going to the page http://myip.nl/

	And you can not SSH to the addr shown there, at least normally it would not
	be NAT'ed to your addr you got by DHCP.

	No way.

fuck.. This is the first thing I should've checked.
Sorry for wasting everybody's time.
The irony is that I know very little about
networking, but the three private IP ranges
is something I actually knew about.

Thanks

Anton


More information about the freebsd-ports mailing list