#1327 closed (worksforme)
ta
| Reported by: | dm666 | Owned by: | somebody |
|---|---|---|---|
| Keywords: | l2tp | Cc: |
Description
DD-WRT v24-sp2 (11/25/09) mini (and all others).
320N is unable to connect to ISP when specifying Gateway (L2TP Server) name. When specifying IP address for L2TP server connection is successful.
Change History (5)
comment:1 Changed 3 years ago by BrainSlayer
comment:2 Changed 3 years ago by BrainSlayer
conside that the dns server provided by your dhcp server must be able to resolv the addresses, otherwise it cant work
comment:3 Changed 3 years ago by dm666
When using automatic configuration (see screen shot below) the modem has an internal cable company IP address and the DNS provided allows to ping the L2TP gateway name. http://img245.imagevenue.com/img.php?image=12492_320N_DNS1_122_217lo.jpg
However when I specify the L2TP gateway name (not IP) the router is unable to connect but able to resolve the name, see below. http://img12.imagevenue.com/img.php?image=12494_320N_DNS2_122_342lo.jpg
This configuration works fine when using direct connection and other router.
Mark.
dark_mark_666ATyahoo.com
comment:4 Changed 3 years ago by BrainSlayer
- Resolution set to worksforme
- Status changed from new to closed
- Summary changed from unable to establish internet connection when using L2TP server name (IP works fine). to ta
even if it resolves, you see that the request times out. it will build a host route for the l2tp server to your standard gateway and establishes the connection. but so far i see, your l2tp server is not reachable, even if it resolves correctly. consider that i tested name based l2tp servers in my own network in a similar configuration. reopen if you have more informations
it has been tested with dns round robin and works without issues here on broadcom devices. i will recheck the kernel config for the 320N which is 2.6 based