李财有方: 买房子要趁早

李财有方: 买房子要趁早
2010/03/01 3:39:24 PM
●李孙耀
有一位住在泰国南部的小商人，和我分享他投资房地产的经验。
1998年金融风暴横扫东南亚，曼谷的房地产跌到无人问津的惨况，那时候他看上一个价值30万令吉（300万铢）的产业想买来作投资。刚好那时候他家隔壁的房子也要出售，价钱也一样，经过一番考虑，最后他选择了隔壁的房子。
曼谷产业飙涨
12年后的今天，那个曼谷的产业已经飞涨至90万令吉了，而他家隔壁的房子却因为泰南局势的动荡，市值只有25万令吉而已，还比12年前来的便宜。
他惋惜地说：投资产业，最重要的是地点。
2004年他的孩子要去曼谷打工，打算在那儿租个房子，租金是每月1000令吉（1万铢）。
有了前车之鉴，他不想再失去产业增值的机会，所以这次他就不租房子而改为购买，当时的房价是25万令吉。
6年后的今天，那儿的房价已经是50万令吉了，而租金也随着房价水涨船高，上到2000令吉。
有能力就别租
他庆幸的说：有能力购买的时候，千万不要去租。
从他的例子里，我们可以看得到，租房子和买房子是有很大的分别：房租是会随着房价逐步高升，而且租户也将错失产业增值机会。
所以买房子要趁早，趁着还年轻的时候，如果能力所及就要去买，不要去租，把租房子的钱改为供房子。租房子是消费，而供房子是投资。
不要小看这简简单单的一个决策，20年后它的分别就很大了。
就举个例子，如果你是一个年轻人，今年25岁，刚刚出来社会工作，住在租来的房子，省吃省用，每年有能力储蓄1万令吉。
先看第一种情况：你只懂得储蓄，不懂得投资，所以你就这样子的储蓄下去，到了50岁那年，你终于储蓄到了25万令吉的存款。
再看第二种情况：你储蓄了5年后，到了30岁那年你决定购买一间价值25万令吉的房子，你就用5万令吉的储蓄钱还了头期，然后贷款20万令吉分20年来供。
因为你拥有了自己的房子，不必再租了，所以你就把省下的房租加上储蓄钱用来供房子，到了50岁那年，你终于把房子供完了。
屋价越来越贵
就根据这两种情况来分析，你觉得25年后，拥有25万令吉的存款或拥有一间没有负债的房子哪一个比较好？
在一般正常的情况下，房子只会越来越贵，不会越来越便宜。
过去如此，将来也是一样。
20年前 15万令吉就可以兴建一间独立式洋楼，今天没有50万根本就做不到，这只是建筑成本的通货膨胀率而已，还没有计算土地的成本呢，如果再加上装修费，一间像样的独立式洋楼价值超过百万就是等闲事了。
如果以过去的经验来做参考，25年后的房子肯定价值不菲。就以每年3%的通货膨胀率来做考量，25年后房价也会涨价一倍。今天价值25万令吉的房子，25年后也会超过50万令吉。
所以价值超过50万令吉的房子，肯定是比25万令吉的存款来的重要。
可能有人会说，但是那笔钱存在银行，每年也是会有利息呀。
可是，别忘了，房租也不可能会25年不变的，房租也是会随着房价而步步高升，微薄的存款利息，万万无法抵消节节上涨的房租。
目前政府正在想方设法，提高人民的收入，逐步废除津贴，使国家经济转型让国民迈入高收入国家的行列，这些措施将会引发另一轮的通货膨胀。
通货膨胀会使金钱的价值变小，但是却会使房地产变得更加的昂贵。
年轻人，如果今天你已经有能力买房子，但是，却还是租房子，是时候改变了，不要再等了。
（作者为大马著名理财专家）

Junos VLAN & Trunking

Today, I’m going to give a quick introduction to VLANs and trunking in JUNOS. VLANs in JUNOS work almost opposite like they do in IOS. You first create a VLAN with a vlan-name and then you assign a vlan-id (dot1q tag). By default all switch-ports are assigned to the ‘default’ vlan which is untagged (no vlan-id is assigned).

To create a VLAN:

set vlans <vlan-name> vlan-id <#>

You then assign interfaces to a VLAN individually:

set interfaces <interface-name> unit 0 family ethernet-switching
vlan members <vlan-name>

Fairly straight-forward right? Now on to trunking, which differs a good bit from what we are used to with IOS. By default, JUNOS does not specify a native-vlan. Trunks, by default, do not support any (allow) any VLANs. Trunks also do no auto-negotiate by default.

To set an interface as a trunk:

set interfaces <interface-name> unit 0 family ethernet-switching
port-mode trunk

You can then either explicitly allow individual VLANs, or you can allow all VLANs on the trunk:

set interfaces <interface-name> unit 0 family ethernet-switching
vlan members all

If you would like to trunk to a Cisco device, you must first create a “native” vlan (it would help to name it ‘native’) with a vlan-id of 1 (unless you’ve changed the native-vlan on the Cisco device). You can then specify the native-vlan on the trunk interface:

set interfaces <interface-name> unit 0 family ethernet-switching
native-vlan-id <#>

I know that this does not appear to be a very easy way of assigning interfaces to VLANs, but at this point in my study it’s all that I’ve got. I am going to do some more research into this, as I’m sure there is a more efficient way of doing things.

----------------------------------------------------------------------------------------------------------------------------

That’s actually a pretty easy way to configure VLANs. But FYI, the Juniper recommended best practice (which I 100% agree with) for configuring VLANs is that you configure untagged (access) VLANs under the VLAN itself, and tagged (trunked) VLANs under the interface.

For example, to accomplish the following:
- create VLANs 10 and 20
- set ge-0/0/0 & ge-0/0/1 as untagged VLAN 10
- set ge-0/0/2 & ge-0/0/3 as untagged VLAN 20
- set ge-0/0/47 as tagged (trunked) with VLANs 10 and 20

you would do the following:

set interfaces ge-0/0/0 unit 0 family ethernet-switching
set interfaces ge-0/0/1 unit 0 family ethernet-switching
set interfaces ge-0/0/2 unit 0 family ethernet-switching
set interfaces ge-0/0/3 unit 0 family ethernet-switching
set interfaces ge-0/0/47 unit 0 family ethernet-switching port-mode trunk
set interfaces ge-0/0/47 unit 0 family ethernet-switching vlan members [ VLAN10 VLAN20 ]
set vlans VLAN10 vlan-id 10
set vlans VLAN20 vlan-id 20
set vlans VLAN10 interface ge-0/0/0.0
set vlans VLAN10 interface ge-0/0/1.0
set vlans VLAN20 interface ge-0/0/2.0
set vlans VLAN20 interface ge-0/0/3.0

Much easier (and cleaner) to configure the untagged VLANs under the VLAN itself.

Also, to create RVIs (the equivalent of SVIs in IOS), you’d simply do:
set interfaces vlan unit 10 family inet 10.10.10.0/24
set interfaces vlan unit 20 family inet 20.20.20.0/24
set vlans VLAN10 l3-interface vlan.10
set vlans VLAN20 l3-interface vlan.20

JunOS basic configuration

Testing

To check if everything work, let’s configure 2 Olives:

root@%cli
root>edit
[edit]
root#

[edit]
root#set system root-authentication plain-text-password
New password:
Retype new password:

[edit]
root#set interfaces em0 unit 0 family inet address 10.0.0.1/8
[edit]
root#commit
commit complete

Configure the other device using the same commands but with another IP address (e.g. 10.0.0.2/8) and ping.

root#exit
Exiting configuration mode
root> ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2): 56 data bytes

64 bytes from 10.0.0.2: icmp_seq=0 ttl=64 time=9.771 ms
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.614 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.693 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.630 ms

Additionally, configure OSPF (or any other multicast based protocol) to test if your routers can talk to each other using multicast packets. Again, type those commands on both routers:

root# set protocols ospf area 0 interface em0

[edit]
root# commit
commit complete

[edit]
root# exit
Exiting configuration mode

Then monitor the traffic from one of the router, you should see some multicast traffic (from/to 224.0.0.5):

root> monitor traffic interface em0

02:30:30.973748 Out IP 10.0.0.1 > 224.0.0.5: OSPFv2, Hello, length 48
02:30:31.007675  In IP 10.0.0.2 > 224.0.0.5: OSPFv2, Hello, length 48

Is everything working? yes? then you are successfully running JunOS! Happy networking