<div>I was referring to your router at home, not the VPN router on your company's side.</div>
<div><span class="gmail_quote">On 12/5/07, <b class="gmail_sendername">Mark K. Zanfardino</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Asheesh - I'm sure that the best overall solution would be to run a<br>native VPN solution, I'm just not sure that this router supports it or
<br>that I have enough information to make the necessary configuration<br>work. Time permitting I will try to get to an upcoming meeting and see<br>if I can get more hands-on help. Thanks!<br><br>Nathan - Sadly this is a company router and I'm not in a position to
<br>change it. We have too many processes relying on this router performing<br>as it does today that my singular need for a linux connection to it is<br>not enough to justify the time and expense of swapping it out or<br>
replacing the firmware, as much as I might like to. So, either I get a<br>native linux solution working or I keep coming into the office...<br><br>Cheers!<br><br>Asheesh Laroia wrote:<br>> On Wed, 5 Dec 2007, Mark K. Zanfardino wrote:
<br>><br>>> I haven't made much progress with this since yesterday, but I have<br>>> read a few more suggestions and will be taking them into<br>>> consideration. If I make any progress I will post the results here.
<br>><br>> If you need help with my suggestion, I should probably be at the next<br>> SF-LUG meeting. I believe that using a native VPN client is the only<br>> way you will be able to get it to work natively!
<br>><br>> -- Asheesh.<br>><br>> --<br>> Some of the trademarks mentioned in this product appear for<br>> identification<br>> purposes only.<br>><br>><br></blockquote></div><br>