Quote:
Originally Posted by shep
You have the subnet mask in hex - see openbsd faq above
|
Specifying the subnet mask as a hexidecimal value is fine. Examples in the
urtw(4) manpage do the same.
A more fundamental problem
tetrodozombie will have in the future is assuming that an address of 10.0.0.1 will always work in all situations. From the limited information provided, it appears he is using his laptop in a Border's cafe which is exposing a 10.0.0.0/24 private subnet. While the addressing used may work in this specific Border's, it is not guaranteed to work in all coffee shops. I would recommend reading
RFC1918 as well as Wikipedia's beginning article on
private networks to provide introductory background on such addressing. The larger issue which needs to be explored & studied is general IP addressing including subnetting. Wikipedia has an article on
this as well. Note that this is simply introductory information for the uninitiated. More in depth tutorials & books need to be read in order to thoroughly master the subject. Understanding this topic is highly recommended if you continue to use OpenBSD in networked situations.
Two very good online tutorials can be found at the following:
Note that 10.0.0.0/8
(classful) is typically referred in in private addressing discussions. Apparently, this particular Border's is further subnetting this down to a /24 private network which isn't altogether surprising, but getting this information would require talking to the in-house staff. Perhaps all Border's expose this specific private subnet, but the point to be taken away from this message is that such a decision is not dictated by IP addressing; rather if such an exposure is widely used, it is as a arbitrary corporate convention.
It is good
tetrodozombie figured out his own configuration issues. OpenBSD is a small project, & much of the support infrastructure found in larger, more established comunities such as Windows & Linux will likely never be as pervasive or complete for the OpenBSD community. Learning to critically read & understand what information is available
(manpages + FAQ + mailing lists) is necessary to use the operating system effectively.