<p>Probably not. This is actually a complicated question about how names are resolved. At this early stage you might be overwhelmed by DNS and netBIOS etc. The easiest thing would be to put an entry into /etc/hosts or just use the IP.</p>
<p>Sent from my Android device. Please excuse my brevity.</p>
<div class="gmail_quote">On Aug 2, 2011 12:07 PM, "KeLLoGsX" <<a href="mailto:mans.xo@gmail.com">mans.xo@gmail.com</a>> wrote:<br type="attribution">> Thank you for the reading advice, haven't had the time yet but will certainly<br>
> bookmark them and have a look. In the meantime, I checked ipconfig /all and<br>> got:<br>> subnet mask 255.255.255.0<br>> default gateway 10.0.0.1<br>> dhcp 10.0.0.1<br>> dns 10.0.0.1<br>> <br>> I changed the etc/network/interfaces with appropriate numbers (broadcast,<br>
> gateway, network)<br>> <br>> *# ip addr*<br>> inet <a href="http://10.0.0.7/24">10.0.0.7/24</a> brd 10.0.0.255<br>> <br>> *# ip route*<br>> default via 10.0.0.1 dev wlan0<br>> <br>> I use static ip now because it works to connect with putty from my windows<br>
> pc. But if I get this host problem solved I can change to dhcp and connect<br>> via the host name instead, right?<br>> <br>> //KeLLoGsX<br>> <br>> <br>> Gustin Johnson-2 wrote:<br>>> <br>>> Well the obvious flaw is that the IP address you used does not match<br>
>> the network and broadcast that you defined (which is network that the<br>>> gateway belongs to). As a result your machine does not "see" the<br>>> gateway.<br>>> <br>>> This is not Linux specific but is networking 101. A good place to<br>
>> start would be the <a href="http://www.tcpipguide.com/">http://www.tcpipguide.com/</a> site. If you plan on<br>>> messing with networks, the book he is also selling there is worth<br>>> every penny. The Linux Advanced Routing and Traffic Control site<br>
>> (<a href="http://www.lartc.org">http://www.lartc.org</a>) is also a wealth of info.<br>>> <br>>> You do not need to memorize everything on those two sites, but they<br>>> both do a good job of covering the basics.<br>
>> <br>>> The short short version is that you either need to change the IP<br>>> address or change the rest. You also do not need the hostapd line<br>>> since this machine is acting as a "client" on an existing wifi<br>
>> network. You would use hostapd if you were building your own access<br>>> point.<br>>> <br>>> The rest of the hosts on your network, do they have 10.0.0.xxx IPs or<br>>> 192.168.1.xxx IPs? From Linux you can find the relevant info with "ip<br>
>> addr" and "ip route". The "ip addr" will give you an IP and netmask<br>>> in CIDR notation (xxx.xxx.xxx.xxx/nn), while other operating systems<br>>> may give you this info as separate IP and netmask entries. The info I<br>
>> am after follows "inet", not "inet6".<br>>> <br>>> On Windows "ipconfig /all" should get you the info you need to make<br>>> this work. Specifically you are looking for the netmask and gateway,<br>
>> I could probably guess/deduce the rest.<br>>> <br>>> Hth,<br>>> On Tue, Aug 2, 2011 at 1:09 AM, KeLLoGsX &<a href="mailto:lt%3Bmans.xo@gmail.com">lt;mans.xo@gmail.com</a>&gt; wrote:<br>>>> Hi Gustin,<br>
>>><br>>>> When I type *# ip route* I get this:<br>>>> <a href="http://10.0.0.0/24">10.0.0.0/24</a> dev wlan0 proto kernel scope link src 10.0.0.7<br>>>><br>>>> Don't know what this means... My interfaces look like this<br>
>>><br>>>> *# etc/network/interfaces *<br>>>> auto wlan0<br>>>> iface wlan0 inet static<br>>>> address 10.0.0.7<br>>>> netmask 255.255.255.0<br>>>> network 192.168.1.0<br>
>>> broadcast 192.168.1.255<br>>>> gateway 192.168.1.1<br>>>> hostapd /etc/hostapd/hostapd.wlan0.conf<br>>>> wpa-ssid ***<br>>>> wpa-psk ***<br>>>><br>>>> Haven't tried the traceroute yet but I will later today.<br>
>>><br>>>> //KeLLoGsX<br>>>><br>>>> --<br>>>> View this message in context:<br>>>> <a href="http://voyage-linux.34677.n3.nabble.com/Host-name-resolve-problem-tp3213232p3218197.html">http://voyage-linux.34677.n3.nabble.com/Host-name-resolve-problem-tp3213232p3218197.html</a><br>
>>> Sent from the Voyage Linux mailing list archive at Nabble.com.<br>>>><br>>>> _______________________________________________<br>>>> Voyage-linux mailing list<br>>>> <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
>>> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>>>><br>>> <br>>> _______________________________________________<br>
>> Voyage-linux mailing list<br>>> <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>>> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
>> <br>> <br>> <br>> --<br>> View this message in context: <a href="http://voyage-linux.34677.n3.nabble.com/Host-name-resolve-problem-tp3213232p3219722.html">http://voyage-linux.34677.n3.nabble.com/Host-name-resolve-problem-tp3213232p3219722.html</a><br>
> Sent from the Voyage Linux mailing list archive at Nabble.com.<br>> <br>> _______________________________________________<br>> Voyage-linux mailing list<br>> <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br></div>