On Nov 28, 2012, at 2:29 PM, Michael Knill wrote:
> Thanks Lonnie. Yes you are right.
> I tried setting a public address with Dyn DDNS and it worked fine actually.
> I don't need any routes as devices on the data VLAN only need to access
> Astlinux and nothing else.
> I thought about using the external interface but I don't want to open up
> ports and don't want to use VPN.
>
> I might try Davids suggestion of running two instances of inadyn and I will
> let you know how it goes.
I'd vote against that. If someday we decided to change from inadyn to
something else, that solution would break. No plans of such a change at the
moment.
Note that the first LAN interface automatically has a local DNS entry...
pbx ~ # head -n4 /etc/hosts
--
# Automatically generated from internal state.
127.0.0.1 localhost
192.168.101.1 pbx.priv.abelbeck.com pbx
--
this is derived from your Hostname and Domain setting in the Network tab.
Lonnie
>
> Regards
> Michael Knill
>
>
>
>
> On 29/11/2012, at 2:08 AM, Lonnie Abelbeck wrote:
>
>> Michael,
>>
>> Ahhh, you are doing a scenario #1, but only for phones, in parallel with the
>> existing data network.
>>
>> But, you want connectivity from the existing data network to your AstLinux
>> network for admin purposes ?
>>
>> Your solution seems fine (manually adding LAN gateway to DNS), not that
>> using Dynamic DNS probably wound not work anyway since many dyndns services
>> won't allow updates with a private IP address in the public DNS.
>>
>> It would seem you need some local static routes as well to route between the
>> private AstLinux LAN subnet and the pre-existing data subnet.
>>
>> Possibly using a VPN to access your AstLinux network via the public
>> interface might be the easiest for simple admin purposes, on demand.
>>
>> Lonnie
>>
>>
>> On Nov 28, 2012, at 12:17 AM, Michael Knill wrote:
>>
>>> Thanks Lonnie but you missed a scenario. As we still only have DSL
>>> broadband here and/or if I am installing a separate system with broadband
>>> connection for a customer, the data network needs connectivity to the
>>> internal data VLAN interface on Astlinux but it is not the default gateway
>>> so only controls phones.
>>>
>>> So any other options? I have been assigning a static address for the LAN
>>> interface and manually adding it to my DNS.
>>>
>>> Regards
>>> Michael Knill
>>>
>>>
>>>
>>>
>>> On 28/11/2012, at 3:44 PM, Lonnie Abelbeck wrote:
>>>
>>>> Hi MIchael,
>>>>
>>>> No, Dynamic DNS is only for the EXT interface.
>>>>
>>>> I don't see how this is a problem, the phone's VLAN's are under your
>>>> control, correct ?
>>>>
>>>> Network -> Network Services: { Configure DNS Hosts }
>>>>
>>>> can define a DNS entry for your LAN1 gateway address, who's scope would
>>>> only be local to AstLinux.
>>>>
>>>> Normally there are two scenarios:
>>>>
>>>> 1) AstLinux is the primary router at the edge, all services are derived
>>>> from AstLinux. AstLinux rules ! :-)
>>>>
>>>> 2) AstLinux plugs into an existing network, the EXT interface is obtained
>>>> from the existing network, all the rest of the AstLinux interfaces LAN1,
>>>> LAN2, etc. drive the phones, PoE switches, wireless AP's, etc. .
>>>>
>>>> Of couse there can be a hybrid of #1 and #2, but #2 provides the most plug
>>>> and play install approach to an existing network, keeping all pre-existing
>>>> (known and unknown) IP's isolated from your AstLinux system.
>>>>
>>>> Lonnie
>>>>
>>>>
>>>> On Nov 27, 2012, at 10:13 PM, Michael Knill wrote:
>>>>
>>>>> Hi group
>>>>>
>>>>> Just out of interest. Is it possible to advertise more than one interface
>>>>> with inadyn. I want to advertise EXT and LAN1 interface to Dyn (different
>>>>> subdomains).
>>>>> This is so I can distribute a full plug and play system where the phones
>>>>> are on a dedicated VLAN and the data VLAN obtains its address via DHCP.
>>>>> This means that User Admin, soft phones and Click2Call can use a fixed
>>>>> URL and I don't need to worry about trying to find a spare address on the
>>>>> customers network.
>>>>>
>>>>> Regards
>>>>> Michael Knill
>>
>>
>> ------------------------------------------------------------------------------
>> Keep yourself connected to Go Parallel:
>> INSIGHTS What's next for parallel hardware, programming and related areas?
>> Interviews and blogs by thought leaders keep you ahead of the curve.
>> http://goparallel.sourceforge.net
>> _______________________________________________
>> 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].
>
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> _______________________________________________
> 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].
>
>
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________
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].
