One way of doing it is to setup a simple BGP rule, use specific route to
one peer and default the rest of the route to your main gateway.

You need to get the ASN from APNIC first then you can do independent
routing.

Regards,
JR


On 7/3/11 6:43 AM, Marlon Guzman wrote:
> Hi Jan,
> 
> I am not sure how to start. We are setting up a dedicated local
> bandwidth from ePLDT which is their VIX. Part of that, you need to get
> your own ASN and a BGP capable router/switch.
> 
> We now have an ASN courtesy of ePLDT for our dedicated 100mbps VIX and
> Juniper NetScreen 25 which is a Firewall/Router capable of BGP. Though
> ePLDT hasn't given us the next step of the implementation. I need some
> assistance in creating BGP instances for our setup. Our client needs
> peering with PLDT DSL users and since the shared VIX of ePLDT doesn't
> have one, the only way is to get a dedicated VIX so that PLDT will allow
> peering with PLDT DSL users.
> 
> Thanks!
> 
> On Sat, Jul 2, 2011 at 11:47 PM, <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     Send PLUG mailing list submissions to
>            [email protected] <mailto:[email protected]>
> 
>     To subscribe or unsubscribe via the World Wide Web, visit
>            http://lists.linux.org.ph/mailman/listinfo/plug
>     or, via email, send a message with subject or body 'help' to
>            [email protected]
>     <mailto:[email protected]>
> 
>     You can reach the person managing the list at
>            [email protected]
>     <mailto:[email protected]>
> 
>     When replying, please edit your Subject line so it is more specific
>     than "Re: Contents of PLUG digest..."
> 
> 
>     Today's Topics:
> 
>       1. Re: traceroute & ping help (Dan Sweeney)
>       2. BGP (Marlon Guzman)
>       3. Re: BGP (Jan Chaves)
>       4. Re: traceroute & ping help (John Osena)
> 
> 
>     ----------------------------------------------------------------------
> 
>     Message: 1
>     Date: Sat, 2 Jul 2011 20:49:44 +0800
>     From: Dan Sweeney <[email protected] <mailto:[email protected]>>
>     Subject: Re: [plug] traceroute & ping help
>     To: "Philippine Linux Users' Group \(PLUG\) Technical Discussion List"
>            <[email protected] <mailto:[email protected]>>
>     Message-ID: <[email protected]
>     <mailto:[email protected]>>
>     Content-Type: text/plain; charset=us-ascii
> 
>     Should probably move this thread to PHNOG Mailing-list
>     [email protected] <mailto:[email protected]>
> 
>     do good stuff
>     Dan
>     On Jul 2, 2011, at 8:08 PM, Dan Sweeney wrote:
> 
>     > Thanks Zak,
>     >
>     > Most of the ISP's in the PH peer locally one place or another..
>     but PLDT is sort of the hold out..
>     >
>     > The bottom line is maximum IP network consumers in the PH
>     (approximately 68%) reside within PLDT's network control.
>     >
>     >> From the information I have it seems that for hosting commercial
>     applications (cloud based or otherwise) a Content Delivery Network
>     could set up in almost any and they should BUY a link to BTN
>     (AS3491) asPLDT peers with them to get bits into AS9299 (PLDT).
>     >
>     > Given the costs of ePLDT Vitro, PHIX, Globe MK2, ETPI, DataOne etc
>     etc add infinitem add nausea one would have to compare them and add
>     in the cost of a link to BTN or Reach.
>     >
>     > BTN is also a *related* company to Reach (AS4637) which is another
>     option locally (over at RCBC Towers in Makati). I'm not exactly sure
>     how BTN and Reach deal with each other business wise (kinda like
>     I-Gate/Infocom and PLDT) but both BTN and Reach are part of the
>     Hutchinson holdings from HK Telecom..
>     >
>     > Anyways.. though dated 3 years ago the link posted shows how
>     ePLDT/PLDT and Globes networks are set up.. however NOTE IN DIAGRAM
>     the VIX router DOES NOT ALLOW TRANSIT. Its not an exchange router..
>     its ePLDT's border router. There is a significant difference.
>     >
>     > http://www.noaccess.com/~dsweeney/Y_Cache_PH.jpg
>     >
>     > Do good Stuff
>     > Dan
>     >
>     >
>     >
>     > On Jul 2, 2011, at 2:18 PM, Zak Elep wrote:
>     >
>     >> Great posts! Guess that really confirms my understanding of how
>     our ISPs today push our packets around ...
>     >>
>     >> On Jul 2, 2011 2:13 PM, "Dan Sweeney" <[email protected]
>     <mailto:[email protected]>> wrote:
>     >>> Oh yeah.. and whats weird about all this is that the
>     198.32.172.0/24 <http://198.32.172.0/24> block shows AS9821 which
>     belongs to DOST-PH-AP
>     >>>
>     >>> Go figure..
>     >>>
>     >>> Do good stuff
>     >>> Dan
>     >>> On Jul 2, 2011, at 1:57 PM, Dan Sweeney wrote:
>     >>>
>     >>>> Well...
>     >>>>
>     >>>> As 198.32.172.0/24 <http://198.32.172.0/24> is a block PLDT
>     (AS9299) hands out from PHIX (AS7707).
>     >>>>
>     >>>> Ping:
>     >>>>
>     >>>> They filter ping from other networks (outside of AS9299) going
>     into AS7707 so its not likely if your not on PLDT myDSL, PLDT
>     Corporate or Smart Broadband.
>     >>>>
>     >>>> Traceroute will work up to the point the traffic transitions
>     into PLDT's AS but will most likely die at that point.
>     >>>>
>     >>>> As far as Globe Tatoo (AS4775).. They NAT (and if your on their
>     WiMAX DOUBLE NAT) you getting to the outside world.. so thats the
>     first strike against performance.
>     >>>>
>     >>>> Globe doesn't have a direct peer with PLDT worth mentioning in
>     the Philippines.. So you reach them buy going OUT of the Philippines
>     and thru some public IX
>     >>>>
>     >>>> So from Globe AS4775 backbone tracing to 198.32.172.140 dies at:
>     >>>>
>     >>>> Tracing the route to 198.32.172.140
>     >>>>
>     >>>> 1 124.6.180.117 [AS4775] 4 msec 4 msec 4 msec
>     >>>> 2 120.28.0.137 [AS4775] 4 msec 4 msec 4 msec
>     >>>> 3 120.28.0.178 [AS4775] 4 msec 4 msec 4 msec
>     >>>> 4 203.177.3.5 [AS4775} 4 msec 4 msec 4 msec
>     >>>> 5 * * *
>     >>>> 6 * * *
>     >>>>
>     >>>> Basically when it hits the transition point going out of Globes
>     network icmp is filtered.
>     >>>>
>     >>>> From SkyBroadband:
>     >>>>
>     >>>> traceroute to 198.32.172.140 (198.32.172.140), 64 hops max, 52
>     byte packets
>     >>>> 1 192.168.100.1 (192.168.100.1) 1.242 ms 1.308 ms 1.121 ms
>     >>>> 2 * 114.108.230.1 (114.108.230.1) 47.098 ms 25.536 ms
>     >>>> 3 ge-1-4.sj1.skybroadband.com.ph
>     <http://ge-1-4.sj1.skybroadband.com.ph> (114.108.192.153
>     <tel:%28114.108.192.153>) 15.177 ms 18.800 ms 16.102 ms
>     >>>> 4 * 10ge1-1-0.gw.sj.skybroadband.com.ph
>     <http://10ge1-1-0.gw.sj.skybroadband.com.ph> (114.108.192.133
>     <tel:%28114.108.192.133>) 71.260 ms 39.370 ms
>     >>>> 5 202.78.121.2 (202.78.121.2) 24.924 ms 92.842 ms 18.963 ms
>     >>>> 6 202.164.168.221 (202.164.168.221) 27.052 ms 93.345 ms
>     po14.ccore.rsv.bayan.net.ph <http://po14.ccore.rsv.bayan.net.ph>
>     (202.78.96.186 <tel:%28202.78.96.186>) 21.440 ms
>     >>>> 7 202.164.168.221 (202.164.168.221) 16.651 ms 10.807 ms *
>     >>>> 8 * * 13.91.0.202.mix.static.eastern-tele.com
>     <http://13.91.0.202.mix.static.eastern-tele.com> (202.0.91.13)
>     171.043 ms
>     >>>> 9 * * *
>     >>>>
>     >>>> Same thing.. hits the transition point and dies..
>     >>>>
>     >>>> From ETPI
>     >>>>
>     >>>> Tracing the route to 198.32.172.140
>     >>>>
>     >>>> 1 97.17.85.115.ids.service.eastern-tele.com
>     <http://97.17.85.115.ids.service.eastern-tele.com> (115.85.17.97)
>     [AS 9658] 0 msec 0 msec 0 msec
>     >>>> 2 rar-a.g1-11.corenet.eastern-tele.com
>     <http://rar-a.g1-11.corenet.eastern-tele.com> (120.89.5.53) [AS
>     9658] 0 msec 4 msec 0 msec
>     >>>> 3 82.128.50.116.corenet.infra.eastern-tele.com
>     <http://82.128.50.116.corenet.infra.eastern-tele.com>
>     (116.50.128.82) [AS 9658] 0 msec 0 msec 0 msec
>     >>>> 4 mix-9658gw.manilaix.net.ph
>     <http://mix-9658gw.manilaix.net.ph> (202.0.91.18) [AS 9670] 4 msec 0
>     msec 0 msec
>     >>>> 5 * * *
>     >>>> 6 *
>     >>>>
>     >>>> Notice that Both SKyBroadband and ETPI think the best way to
>     PHIX 198.32.172.0/24 <http://198.32.172.0/24> is via MIX (ETPI's IX).
>     >>>>
>     >>>> From noaccess in Santa Clara California:
>     >>>>
>     >>>> raceroute to 198.32.172.162 (198.32.172.162), 30 hops max, 40
>     byte packets
>     >>>> 1 sj1-e1-0.net.noaccess.com <http://sj1-e1-0.net.noaccess.com>
>     (193.72.216.1) [AS15096] 0.398 ms 0.389 ms 0.387 ms
>     >>>> 2 v601.core1.fmt2.he.net <http://v601.core1.fmt2.he.net>
>     (64.62.142.145 <tel:%2864.62.142.145>) [AS6939] 0.642 ms 0.872 ms
>     1.072 ms
>     >>>> 3 * * *
>     >>>> 4 * * *
>     >>>>
>     >>>> dies again..
>     >>>>
>     >>>> And since the resource is available it seems that we should
>     look at going OUT from a machine inside PHIX in the 198.32.172.0/24
>     <http://198.32.172.0/24> block
>     >>>>
>     >>>> I have done so and its filtered at the border between PHIX
>     (AS7707) and PLDT (AS9299) even though PLDT basically controls both
>     networks.
>     >>>>
>     >>>> So you will probably die at 121.127.0.53 (I think the gateway
>     router between PHIX and PLDT).
>     >>>>
>     >>>> I'm to lazy today to hook up PLDT myDSL link but basically if
>     your not in PLDT's AS9299 or InfoCom (AS7629) you'll most likely get
>     pretty dismal performance trying to reach anything in PHIX.
>     >>>>
>     >>>> Do good stuff
>     >>>> Dan
>     >>>>
>     >>>>
>     >>>>
>     >>>>
>     >>>>
>     >>>>
>     >>>> On Jun 15, 2011, at 1:41 PM, John Osena wrote:
>     >>>>
>     >>>>> 198.32.172.130
>     >>>>
>     >>>
>     >>> _________________________________________________
>     >>> Philippine Linux Users' Group (PLUG) Mailing List
>     >>> http://lists.linux.org.ph/mailman/listinfo/plug
>     >>> Searchable Archives: http://archives.free.net.ph
>     >> _________________________________________________
>     >> Philippine Linux Users' Group (PLUG) Mailing List
>     >> http://lists.linux.org.ph/mailman/listinfo/plug
>     >> Searchable Archives: http://archives.free.net.ph
>     >
>     > _________________________________________________
>     > Philippine Linux Users' Group (PLUG) Mailing List
>     > http://lists.linux.org.ph/mailman/listinfo/plug
>     > Searchable Archives: http://archives.free.net.ph
> 
> 
> 
>     ------------------------------
> 
>     Message: 2
>     Date: Sat, 2 Jul 2011 23:14:46 +0800
>     From: Marlon Guzman <[email protected]
>     <mailto:[email protected]>>
>     Subject: [plug] BGP
>     To: [email protected] <mailto:[email protected]>
>     Message-ID:
>          
>      <CAMQuvy7EwKiMQ9v_FJCS8K98TtRP9Tovvtq+T9=edi8yyda...@mail.gmail.com
>     <mailto:[email protected]>>
>     Content-Type: text/plain; charset="utf-8"
> 
>     Anyone who has an idea with BGP on ASN? Thanks!
>     -------------- next part --------------
>     An HTML attachment was scrubbed...
>     URL:
>     
> http://lists.linux.org.ph/mailman/private/plug/attachments/20110702/00035642/attachment.htm
> 
>     ------------------------------
> 
>     Message: 3
>     Date: Sat, 2 Jul 2011 23:37:14 +0800
>     From: Jan Chaves <[email protected] <mailto:[email protected]>>
>     Subject: Re: [plug] BGP
>     To: "Philippine Linux Users' Group (PLUG) Technical Discussion List"
>            <[email protected] <mailto:[email protected]>>
>     Message-ID: <[email protected]
>     <mailto:[email protected]>>
>     Content-Type: text/plain;       charset=us-ascii
> 
>     Hi Marlon,
> 
>     BGP routing is a massive topic, where would you want to start? :)
> 
> 
>     Kind regards,
>     Jan
> 
>     On Jul 2, 2011, at 11:14 PM, Marlon Guzman <[email protected]
>     <mailto:[email protected]>> wrote:
> 
>     > Anyone who has an idea with BGP on ASN? Thanks!
>     > _________________________________________________
>     > Philippine Linux Users' Group (PLUG) Mailing List
>     > http://lists.linux.org.ph/mailman/listinfo/plug
>     > Searchable Archives: http://archives.free.net.ph
> 
> 
>     ------------------------------
> 
>     Message: 4
>     Date: Sat, 2 Jul 2011 08:47:10 -0700 (PDT)
>     From: John Osena <[email protected] <mailto:[email protected]>>
>     Subject: Re: [plug] traceroute & ping help
>     To: "Philippine Linux Users' Group \(PLUG\) Technical Discussion List"
>            <[email protected] <mailto:[email protected]>>
>     Message-ID:
>          
>      <[email protected]
>     <mailto:[email protected]>>
>     Content-Type: text/plain; charset="us-ascii"
> 
>     Dan, great diagram and excellent post...good stuff! Thank you.
> 
>     John
> 
>     --- On Sat, 7/2/11, Dan Sweeney <[email protected]
>     <mailto:[email protected]>> wrote:
> 
>     From: Dan Sweeney <[email protected] <mailto:[email protected]>>
>     Subject: Re: [plug] traceroute & ping help
>     To: "Philippine Linux Users' Group (PLUG) Technical Discussion List"
>     <[email protected] <mailto:[email protected]>>
>     Received: Saturday, July 2, 2011, 8:08 PM
> 
>     Thanks Zak,
> 
>     Most of the ISP's in the PH peer locally one place or another.. but
>     PLDT is sort of the hold out..
> 
>     The bottom line is maximum IP network consumers in the PH
>     (approximately 68%) reside within PLDT's network control.
> 
>     >From the information I have it seems that for hosting commercial
>     applications (cloud based or otherwise) a Content Delivery Network
>     could set up in almost any and they should BUY a link to BTN
>     (AS3491) asPLDT peers with them to get bits into AS9299 (PLDT).
> 
>     Given the costs of ePLDT Vitro, PHIX, Globe MK2, ETPI, DataOne etc
>     etc add infinitem add nausea one would have to compare them and add
>     in the cost of a link to BTN or Reach.
> 
>     BTN is also a *related* company to Reach (AS4637) which is another
>     option locally (over at RCBC Towers in Makati). I'm not exactly sure
>     how BTN and Reach deal with each other business wise (kinda like
>     I-Gate/Infocom and PLDT) but both BTN and Reach are part of the
>     Hutchinson holdings from HK Telecom..
> 
>     Anyways.. though dated 3 years ago the link posted shows how
>     ePLDT/PLDT and Globes networks are set up.. however NOTE IN DIAGRAM
>     the VIX router DOES NOT ALLOW TRANSIT. Its not an exchange router..
>     its ePLDT's border router. There is a significant difference.
> 
>     http://www.noaccess.com/~dsweeney/Y_Cache_PH.jpg
> 
>     Do good Stuff
>     Dan
> 
> 
> 
>     On Jul 2, 2011, at 2:18 PM, Zak Elep wrote:
> 
>     > Great posts! Guess that really confirms my understanding of how
>     our ISPs today push our packets around ...
>     >
>     > On Jul 2, 2011 2:13 PM, "Dan Sweeney" <[email protected]
>     <mailto:[email protected]>> wrote:
>     > > Oh yeah.. and whats weird about all this is that the
>     198.32.172.0/24 <http://198.32.172.0/24> block shows AS9821 which
>     belongs to DOST-PH-AP
>     > >
>     > > Go figure..
>     > >
>     > > Do good stuff
>     > > Dan
>     > > On Jul 2, 2011, at 1:57 PM, Dan Sweeney wrote:
>     > >
>     > >> Well...
>     > >>
>     > >> As 198.32.172.0/24 <http://198.32.172.0/24> is a block PLDT
>     (AS9299) hands out from PHIX (AS7707).
>     > >>
>     > >> Ping:
>     > >>
>     > >> They filter ping from other networks (outside of AS9299) going
>     into AS7707 so its not likely if your not on PLDT myDSL, PLDT
>     Corporate or Smart Broadband.
>     > >>
>     > >> Traceroute will work up to the point the traffic transitions
>     into PLDT's AS but will most likely die at that point.
>     > >>
>     > >> As far as Globe Tatoo (AS4775).. They NAT (and if your on their
>     WiMAX DOUBLE NAT) you getting to the outside world.. so thats the
>     first strike against performance.
>     > >>
>     > >> Globe doesn't have a direct peer with PLDT worth mentioning in
>     the Philippines.. So you reach them buy going OUT of the Philippines
>     and thru some public IX
>     > >>
>     > >> So from Globe AS4775 backbone tracing to 198.32.172.140 dies at:
>     > >>
>     > >> Tracing the route to 198.32.172.140
>     > >>
>     > >> 1 124.6.180.117 [AS4775] 4 msec 4 msec 4 msec
>     > >> 2 120.28.0.137 [AS4775] 4 msec 4 msec 4 msec
>     > >> 3 120.28.0.178 [AS4775] 4 msec 4 msec 4 msec
>     > >> 4 203.177.3.5 [AS4775} 4 msec 4 msec 4 msec
>     > >> 5 * * *
>     > >> 6 * * *
>     > >>
>     > >> Basically when it hits the transition point going out of Globes
>     network icmp is filtered.
>     > >>
>     > >> From SkyBroadband:
>     > >>
>     > >> traceroute to 198.32.172.140 (198.32.172.140), 64 hops max, 52
>     byte packets
>     > >> 1 192.168.100.1 (192.168.100.1) 1.242 ms 1.308 ms 1.121 ms
>     > >> 2 * 114.108.230.1 (114.108.230.1) 47.098 ms 25.536 ms
>     > >> 3 ge-1-4.sj1.skybroadband.com.ph
>     <http://ge-1-4.sj1.skybroadband.com.ph> (114.108.192.153
>     <tel:%28114.108.192.153>) 15.177 ms 18.800 ms 16.102 ms
>     > >> 4 * 10ge1-1-0.gw.sj.skybroadband.com.ph
>     <http://10ge1-1-0.gw.sj.skybroadband.com.ph> (114.108.192.133
>     <tel:%28114.108.192.133>) 71.260 ms 39.370 ms
>     > >> 5 202.78.121.2 (202.78.121.2) 24.924 ms 92.842 ms 18.963 ms
>     > >> 6 202.164.168.221 (202.164.168.221) 27.052 ms 93.345 ms
>     po14.ccore.rsv.bayan.net.ph <http://po14.ccore.rsv.bayan.net.ph>
>     (202.78.96.186 <tel:%28202.78.96.186>) 21.440 ms
>     > >> 7 202.164.168.221 (202.164.168.221) 16.651 ms 10.807 ms *
>     > >> 8 * * 13.91.0.202.mix.static.eastern-tele.com
>     <http://13.91.0.202.mix.static.eastern-tele.com> (202.0.91.13)
>     171.043 ms
>     > >> 9 * * *
>     > >>
>     > >> Same thing.. hits the transition point and dies..
>     > >>
>     > >> From ETPI
>     > >>
>     > >> Tracing the route to 198.32.172.140
>     > >>
>     > >> 1 97.17.85.115.ids.service.eastern-tele.com
>     <http://97.17.85.115.ids.service.eastern-tele.com> (115.85.17.97)
>     [AS 9658] 0 msec 0 msec 0 msec
>     > >> 2 rar-a.g1-11.corenet.eastern-tele.com
>     <http://rar-a.g1-11.corenet.eastern-tele.com> (120.89.5.53) [AS
>     9658] 0 msec 4 msec 0 msec
>     > >> 3 82.128.50.116.corenet.infra.eastern-tele.com
>     <http://82.128.50.116.corenet.infra.eastern-tele.com>
>     (116.50.128.82) [AS 9658] 0 msec 0 msec 0 msec
>     > >> 4 mix-9658gw.manilaix.net.ph
>     <http://mix-9658gw.manilaix.net.ph> (202.0.91.18) [AS 9670] 4 msec 0
>     msec 0 msec
>     > >> 5 * * *
>     > >> 6 *
>     > >>
>     > >> Notice that Both SKyBroadband and ETPI think the best way to
>     PHIX 198.32.172.0/24 <http://198.32.172.0/24> is via MIX (ETPI's IX).
>     > >>
>     > >> From noaccess in Santa Clara California:
>     > >>
>     > >> raceroute to 198.32.172.162 (198.32.172.162), 30 hops max, 40
>     byte packets
>     > >> 1 sj1-e1-0.net.noaccess.com <http://sj1-e1-0.net.noaccess.com>
>     (193.72.216.1) [AS15096] 0.398 ms 0.389 ms 0.387 ms
>     > >> 2 v601.core1.fmt2.he.net <http://v601.core1.fmt2.he.net>
>     (64.62.142.145 <tel:%2864.62.142.145>) [AS6939] 0.642 ms 0.872 ms
>     1.072 ms
>     > >> 3 * * *
>     > >> 4 * * *
>     > >>
>     > >> dies again..
>     > >>
>     > >> And since the resource is available it seems that we should
>     look at going OUT from a machine inside PHIX in the 198.32.172.0/24
>     <http://198.32.172.0/24> block
>     > >>
>     > >> I have done so and its filtered at the border between PHIX
>     (AS7707) and PLDT (AS9299) even though PLDT basically controls both
>     networks.
>     > >>
>     > >> So you will probably die at 121.127.0.53 (I think the gateway
>     router between PHIX and PLDT).
>     > >>
>     > >> I'm to lazy today to hook up PLDT myDSL link but basically if
>     your not in PLDT's AS9299 or InfoCom (AS7629) you'll most likely get
>     pretty dismal performance trying to reach anything in PHIX.
>     > >>
>     > >> Do good stuff
>     > >> Dan
>     > >>
>     > >>
>     > >>
>     > >>
>     > >>
>     > >>
>     > >> On Jun 15, 2011, at 1:41 PM, John Osena wrote:
>     > >>
>     > >>> 198.32.172.130
>     > >>
>     > >
>     > > _________________________________________________
>     > > Philippine Linux Users' Group (PLUG) Mailing List
>     > > http://lists.linux.org.ph/mailman/listinfo/plug
>     > > Searchable Archives: http://archives.free.net.ph
>     > _________________________________________________
>     > Philippine Linux Users' Group (PLUG) Mailing List
>     > http://lists.linux.org.ph/mailman/listinfo/plug
>     > Searchable Archives: http://archives.free.net.ph
> 
>     _________________________________________________
>     Philippine Linux Users' Group (PLUG) Mailing List
>     http://lists.linux.org.ph/mailman/listinfo/plug
>     Searchable Archives: http://archives.free.net.ph
>     -------------- next part --------------
>     An HTML attachment was scrubbed...
>     URL:
>     
> http://lists.linux.org.ph/mailman/private/plug/attachments/20110702/8e01a9f6/attachment.htm
> 
>     ------------------------------
> 
>     _________________________________________________
>     Philippine Linux Users' Group (PLUG) Mailing List
>     http://lists.linux.org.ph/mailman/listinfo/plug
>     Searchable Archives: http://archives.free.net.ph
> 
>     End of PLUG Digest, Vol 76, Issue 4
>     ***********************************
> 
> 
> 
> 
> -- 
> Marlon D. Guzman
> Solid Hosting <http://www.solidhosting.ph>
> Systems Administrator
> 
> 24/7 Support Hotline: 632.937.4091 and 632.697.5450
> Smart: 0908.876.0226 <tel:0908.876.0226>
> Globe: 0915.205.4922 <tel:0915.205.4922>
> Sun: 0922.885.1362
> 
> 
> 
> _________________________________________________
> Philippine Linux Users' Group (PLUG) Mailing List
> http://lists.linux.org.ph/mailman/listinfo/plug
> Searchable Archives: http://archives.free.net.ph

_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
http://lists.linux.org.ph/mailman/listinfo/plug
Searchable Archives: http://archives.free.net.ph

Reply via email to