This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

L2TP: Advertise Routes and Domains?

Is it possible to have the Astaro L2TP server advertise routes and search domains to the connecting client?

For example, on a non-Astaro L2TP VPN, I am able to configure the server in a way that the client receives the following info (this is pasted from the client's log):

Mon Feb 27 11:02:32 2012 : rcvd [ACSCP ConfAck id=0x1  ]

Mon Feb 27 11:02:32 2012 : rcvd [ACSP data 

    

    ]

Mon Feb 27 11:02:32 2012 : sent [ACSP data ]

Mon Feb 27 11:02:32 2012 : rcvd [ACSP data 

    

    ]

How can I get the Astaro L2TP to publish similar info to clients when they connect?

This thread was automatically locked due to age.

Parents

0 BAlfson over 13 years ago

Does this KnowledgeBase article solve the first problem? Howto - Allow Remote Access Users to Reach Another Site via a Site-to-Site Tunnel

Also, I need to advertise certain DNS search domains to these VPN clients as well.

I don't understand. Could you please be more specific?

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 13 years ago

Does this KnowledgeBase article solve the first problem? Howto - Allow Remote Access Users to Reach Another Site via a Site-to-Site Tunnel

Also, I need to advertise certain DNS search domains to these VPN clients as well.

I don't understand. Could you please be more specific?

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 rcrcr over 13 years ago in reply to BAlfson

Sure,

there are certain private domain names that need to be advertised to the clients upon connecting so that the clients know that (1) lookups for these domains should be directed to the VPN's DNS and not the client's WAN DNS, and that (2) these domains should be appended (in order) by the clients when as an implied domain when attempting to resolve DNS lookups from only a hostname.

(Sort of like DHCP Option 119.)

Under the above scenario,

if example1.private and example2.private had been advertised,

(1) the client would query its usual DNS to resolve "yahoo.com".

(2) the client would query the VPN DNS to resolve "host.example1.private".

(3) the client would query the VPN DNS to resolve "host2", which it would query as "host2.example1.private", and then as "host2.example2.private" if the first lookup failed.

Remote Access --> Advanced --> Domain Name is where I would think this could be set, but did not work in my trial.
Cancel
Vote Up 0 Vote Down

Cancel