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