Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


9 posts

Wannabe Geek


Topic # 25128 12-Aug-2008 20:14
Send private message

Hi maverick and other helpful fellow geeks...

I have "a bit of a doozy" of a problem (WxC Tech Support's words) with my SPA2102 VoIP router, on an XNet Fusion ADSL plan.
... and I hope you can help... otherwise I will have to call WxC back to log a proper trouble ticket if I can't resolve this in the next few days.

Context:
  • PPPoA to Ethernet bridge modem: D-Link DSL-300T (Normally any PC or router can pull the proper WAN IP and DNS servers via DHCP from XNet, so it is nakedly/directly connected to the DSL network).
    Details: http://www.thinkbroadband.com/hardware/reviews/2004/q4/dlink-dsl300t.html
    G.dmt ADSL link speed: 7616kbps down / 896kbps up  (Rock on Chorus!)
     
  • NAT Router: SMC Barricade SMC2804WBR 802.11g -- solid, has run like a charm for me since 2004 under heavy punishment.
    Details: http://reviews.cnet.com/routers/smc-smc2804wbr-barricade-54mbps/1995-3319_7-21100137.html
     
  • The SPA2102 device connects and establishes the line properly when set with Static IP on the WAN side, behind my existing NAT router... but...

Problem:
  • The SPA2102 does not pick up a valid WAN IP address or DNS IPs when set to DHCP on the WAN interface when connected to the DSL-300T, with or without the SMC plugged into the LAN-side.  (ie. The Xnet BRAS doesn't play nicely with the SPA2102... Did disclosing it's MAC address doom it to a life of exclusion?! Cry),
    This seems very strange, as every other device I have owned, including a 'Lingo' VoIP ATA with inline bridge-mode QoS from VoIP provider Primus Communications (of the USA), has worked just fine behind this modem, and with the SMC router as the LAN-side client. 
     
  • Aside from that, and frustratingly, the 'Bridge mode' in the SPA2102 does not seem to work (even when my IP address range on the LAN side is not in conflict, per other suggested fixes in threads on these Geekzone forums).  So with the SPA2102 in the place where it logically should be, in between modem and router so it can prioritise voice, the SMC now can't get the DHCP WAN IP and DNS IPs like it normally does from the DSL-300T.  (Bah! humbug! Not only does the SPA2102 not work... it also breaks everything else!) Yell
     
  • Then, in the current setup, with the SPA2102 behind my SMC (so it's in my LAN), the SPA2102 is owning my LAN: killing my internet connection's usability. (I thought it only needed 64kbps up and down?!)
     
  • Additionally, because of being located behind the NAT along with our laptops/PCs, the SPA2102 is not able to apply a QoS priority to voice traffic over data traffic... I anticipate that this will hurt our VFX service's usability when we're hammering the data connection... the routine problem faced by Linksys PAP2T basic ATA users. 
     
Next steps:
  • If possible, I will try spoofing a (laptop-like Wink) MAC address and hostname on the SPA2102's WAN side to see if that
    allows me to properly get a WAN IP and DNS IPs from the Xnet BRAS.
     
  • Then tonight I'm going to try a Zyxel Prestige 660HW ADSL2+ modem/router (using it only as the ADSL modem; ie. with SPI, Media Bandwidth Management, and the built-in 802.11g AP all disabled) with the SPA2102 behind it, and a standard 802.11g Access-point (non-NAT) on the SPA2102's LAN-side.  So the SPA2102 should then be my NAT router as well as ATA with voice-priority over data. 
    Unfortunately, I think the Zyxel will insist on NAT'ing as well... but that shouldn't be a show-stopper... all the sessions should carry through correctly (the proof being my ability to use the SMC to NAT LAN traffic onto its Ethernet WAN port while also sitting behind the Zyxel which NATs sessions onto the DSL connection oblivious to the fact that they've already been NAT'd by the SMC).

    ... and I'll report back tomorrow. 

How to help?
  • VFX users: Have you experienced similar issues with the SPA2102?  (My one is an Xnet-packaged original, new, and provisioned correctly after I used Static IP on the WAN side behind my existing NAT router.)
     
  • WxC staff: Any ideas on the WAN-side DHCP issue with the SPA2102?  Are there any known incompatibilities with ADSL modems?  (I bought the SPA2102 rather than a WAG54GP2 as I was hoping to one day move to a fibre-based access solution with Xnet and maintain my VFX line seamlessly while changing the access line... and maybe I'll also carry the unit around with me to other locations to use VFX service from there... eg. hotels, my parent's house on Orcon ADSL, and my mate's place on an NZWireless 802.11b last-mile access network... ie. Places where I'll also connect my laptop by Ethernet, preferably to the LAN-side of the SPA2102.) 
     
  • WxC or C1 (to assist in trying my solution of last resort): offer a trade-in on my SPA2102 for a WAG54GP2v2, pleeease?  (And cross fingers that it works!) 

Thanks in advance for your assistance!

~Heath



Create new topic
3535 posts

Uber Geek
+1 received by user: 125

Trusted

  Reply # 156396 12-Aug-2008 20:57
Send private message

heathm:The SPA2102 device connects and establishes the line properly when set with Static IP on the WAN side, behind my existing NAT router...

I installed a SPA2102 with VFX about 18 months ago and that's the only way I could get it to work as well.

heathm:The SPA2102 does not pick up a valid WAN IP address or DNS IPs when set to DHCP on the WAN interface when connected to the DSL-300T, with or without the SMC plugged into the LAN-side.  (ie. The Xnet BRAS doesn't play nicely with the SPA2102...

Yep, I found the same problem.  In my case the router was a ZyXEL (not the 660HW that you have, but an earlier model).

heathm:Aside from that, and frustratingly, the 'Bridge mode' in the SPA2102 does not seem to work (even when my IP address range on the LAN side is not in conflict, per other suggested fixes in threads on these Geekzone forums).

Yep, that was my experience too Yell

heathm:So with the SPA2102 in the place where it logically should be, in between modem and router so it can prioritise voice, the SMC now can't get the DHCP WAN IP and DNS IPs like it normally does from the DSL-300T.  (Bah! humbug! Not only does the SPA2102 not work... it also breaks everything else!) Yell

My experience as well.

heathm:Then, in the current setup, with the SPA2102 behind my SMC (so it's in my LAN), the SPA2102 is owning my LAN: killing my internet connection's usability.

Are the other devices which are being slowed down connected via the LAN port of your SPA2102, or via another LAN port of your SMC?

In my case, I have the WAN port of the SPA2102 connected to a LAN port on the ZyXEL, and all other devices use other LAN ports of the ZyXEL.  The LAN port of the SPA2102 is unused.

heathm:Additionally, because of being located behind the NAT along with our laptops/PCs, the SPA2102 is not able to apply a QoS priority to voice traffic over data traffic... I anticipate that this will hurt our VFX service's usability when we're hammering the data connection... the routine problem faced by Linksys PAP2T basic ATA users.

In my case, I have not found this to be a problem.  The bandwidth of a FS/FS connection is so much more than the pipes connecting to the other servers which are being accessed, that our connection is never saturated, hence QoS problems have never arisen.

Having said that, the SPA2102 is used at a business where no torrenting is used; your situation may be different.

heathm:VFX users: Have you experienced similar issues with the SPA2102?  (My one is an Xnet-packaged original, new, and provisioned correctly after I used Static IP on the WAN side behind my existing NAT router.)

My SPA2102 was the same, and my experience was very much the same as well.

Hence, in a more recent installation, I bought a second-hand PAP2T, plugged it into a spare router LAN port and we were up and running in a few minutes without any drama whatsoever.  Compared to the SPA2102, it was just too easy, and for this reason, I would not use one of these devices again.

If I needed Fax capability, I would use WRP400 or for voice only, I would stick with a PAP2T.

Cheers,
Grant.



9 posts

Wannabe Geek


Reply # 156480 13-Aug-2008 08:07
Send private message

grant_k: Are the other devices which are being slowed down connected via the LAN port of your SPA2102, or via another LAN port of your SMC?
In my case, I have the WAN port of the SPA2102 connected to a LAN port on the ZyXEL, and all other devices use other LAN ports of the ZyXEL.  The LAN port of the SPA2102 is unused.

Thanks Grant,
Yeah, my setup is the same -- ie. plugged side-by-side with the SPA2102 into the SMC and all on the same IP subnet, not on the LAN-side of the SPA-2102.  (In fact I'm at home now and had to unplug the SPA2102 as it was DOS'ing my WAN connection so even this geekzone page wouldn't load.) 

grant_k: My SPA2102 was the same, and my experience was very much the same as well.
Hence, in a more recent installation, I bought a second-hand PAP2T, plugged it into a spare router LAN port and we were up and running in a few minutes without any drama whatsoever.  Compared to the SPA2102, it was just too easy, and for this reason, I would not use one of these devices again.
If I needed Fax capability, I would use WRP400 or for voice only, I would stick with a PAP2T.

Yeah, so looks like I'll probably be pitching C1 for a Consumer Guarantees Act return credit for this SPA2102 so I can buy a WRP400. Problem is, I know they're going to give me grief because they just shift the hardware... so hopefully WxC comes to my rescue on this hardware exchange/swap-out. 

Cheers,
Heath



9 posts

Wannabe Geek


Reply # 157459 16-Aug-2008 21:07
Send private message

OK so I finally got time to test this (POS) SPA2102 with:
a) Spoofed/cloned MAC address, and separately:
b) Behind the Zyxel 660HW.

And unfortunately the problem persists: The SPA2102 refuses to pull a valid DHCP+WAN gateway address (and therewith DNS servers) from Xnet.  No other modem/router or ATA I have ever used has been this much of a pain to get connected. 
Even if I cut the SMC out of the equation, then even just my laptop sitting behind the SPA2102 can't ping out to Xnet's DNS servers -- eeew.  Yell

So the only way to get the SPA2102 to work seems to be "as a PC-like device in your LAN", using your normal router to do LAN-to-WAN Gateway tasks including relaying DNS. 
(Disclosure: Since a firmware update was pushed to it by Xnet's automated provisioning this SPA2102 isn't owning my LAN so much thankfully, but it's still nowhere near acceptable.) 

Readers, please take this as advice; DO NOT BUY AN SPA2102.
I am going to attempt to return my one to Xnet, on the basis that it was advertised as providing voice prioritisation which it clearly fails to do as it cannot be put inline in the way which it is advertised+instructed to be installed.  Frown  I will be buying a WRP400 and that had better work or there's going to be a strongly worded verbal critique of Xnet's "certification" and "provisioning" of this hardware. 




Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.