If your aim is for the astlinux box to have the public IP address assigned to 
it the easiest way to do it is connection ethernet ADSL modem to a NIC such as 
the X-Modem http://www.adslnation.com/products/xmodem-m3.php

Darren

On 23 Aug 2010, at 16:22, Tom Chadwin wrote:

> I'm in the UK, and currently do have a few spare DSL lines kicking around
> (though they are spare because I have identified them as unused, and are
> slated for removal). But excuse the dilletante ignorance: our Astlinux
> EXTIFs connect to ADSL modem/routers. I did ask a while back about the
> ability to get a hw NIC to do PPPoA, and was told it was impossible. How
> could I help? Would I need an ADSL card (ie is that what you are
> suggesting)?
> 
> To answer your previous question: we have PSTN cards to connect to the PSTN.
> Because our DSL is limited to a theoretical max of 832kbps, VoIP is
> unrealistic other than between our sites. Our set-up is therefore:
> 
> 
> SIP handsets + PAP2Ts
>       |
> Astlinux - ADSL modem/routers - IAX2 over ADSL to another site
>       |
> PSTN card (berofix BRI or PRI, or Digium TDM POTS card)
>       |
>    PSTN
> 
> 
> Go ASCII.
> 
> Hope this clarifies
> 
> Tom
> 
> 
>> -----Original Message-----
>> From: Philip Prindeville [mailto:[email protected]] 
>> Sent: 21 August 2010 00:54
>> To: [email protected]
>> Subject: Re: [Astlinux-users] Second external NIC for VPN
>> 
>>  On 8/20/10 8:03 AM, Tom Chadwin wrote:
>>>> Another issue, only one interface can be PPPoE, not both.
>>>> (Assuming you are using PPPoE for your ADSL)
>>> Nope: PPPoA via external routers.
>> 
>> I'm working on PPPoA support right now.  Just need to order a circuit.
>> 
>> BTW:  where are you located, and do you have any spare DSL 
>> circuits (or one you could loan for testing)?
>> 
>> Might be faster than getting a circuit delivered.
>> 
>> -Philip
>> 
>> 
>> 
>>>> Another issue, IPsec is only supported as static IP to static IP.
>>> All sites have /29 static subnets, so no problem there. Home users 
>>> obviously are dynamic.
>>> 
>>>> Another issue, L2TP/IPsec server is not supported.  On the other 
>>>> hand, OpenVPN can be configured to handle your needs, but all your 
>>>> clients would have to switch to OpenVPN.
>>> Not too much of an issue, to be honest - our current L2TP/IPSec 
>>> road-warrior connection have utterly unexplained problems 
>> as it is, so 
>>> a change would not be out of the question.
>>> 
>>> Tom
>> 
>> 
>> --------------------------------------------------------------
>> ----------------
>> This SF.net email is sponsored by 
>> 
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge 
>> http://p.sf.net/sfu/RIM-dev2dev 
>> _______________________________________________
>> Astlinux-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>> 
>> Donations to support AstLinux are graciously accepted via 
>> PayPal to [email protected].
>> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Astlinux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to 
> [email protected].


------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].

Reply via email to