nick
Wed Apr 09 15:38:28 PDT 2008
On Apr 9, 5:28=A0pm, nick <cipher7...@gmail.com> wrote:
> On Apr 9, 3:58=A0pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
>
>
>
>
>
> > "nick" <cipher7...@gmail.com> wrote in message
>
> >news:9b3831d0-c0b4-4078-97e4-3055f34bcc1f@a70g2000hsh.googlegroups.com...=
>
> > > I went to a site that had a VPN/Router device. It looked as if it was
> > > in bridged ethernet mode with Bellsouth's Netopia device because
>
> > Probably true.
>
> > > Ok well it seems that Bellsouth reset all the settings on the Netopia.=
> > > The only way to get the Internet to work was to tell the VPN/Router to=
> > > pull an IP automatically from the Netopia device.
>
> > > That was fine until I tried to reestablish the VPN. I'm aware that
> > > VPN's may have problems with NAT. I assumed that the original tech
> > > setup the router in bridged ethernet so that it would "look" as if the=
> > > VPN/Router held the Netopia's public IP thereby facilitating the VPN
> > > connection.
>
> > Yep. Except it didn't "look" like it had the Public IP#,...it actually d=
id
> > have the Public IP#
>
> > > Instead I left it as is, and used IP Passthrough on the Netopia to the=
> > > VPN/Router. However, users are complaining that the connection to the
> > > remote software shifts in speed. Could this be because of IP
> > > passthrough?
>
> > That could be. The VPN Passthrough functionality has additonal "over-hea=
d"
> > added to the mix that was not there before.
>
> > > Or could it be just their cruddy DSL that keeps going out?
>
> > Could be that too. =A0VPN will only match up with and run at the slower
> > "upload" speed of the DSL. =A0The faster "download" speed is just going =
to
> > waste and is unusable to the VPN. =A0But then it could also be *both* at=
the
> > same time,...VPN Passthrough plus the crappy DSL.
>
> > Best solution is to either put the Netopia and the VPN/Router back exact=
ly
> > as it was before when it was working right,...or throw out the Netopia a=
nd
> > replace it with a "straight" simple DSL Modem (no NAT, no router, no
> > firewall) that is compatible with the Bell South DSL,...then configure t=
he
> > VPN/Router directly with the Public IP# Specs. =A0 The VPN /Router may a=
lso
> > need to be capable of using PPPoE,...that is the only logical reason tha=
t
> > there ever would have been any "DSL Sign-On" information in the first pl=
ace.
> > There is no "sign-on" information for non-PPPoE DSL connections. =A0At t=
his
> > point the VPN/Router will "become" their "firewall",...so then you can c=
all
> > it their VPN/Firewall.
>
> > --
> > Phillip Windellwww.wandtv.com
>
> > The views expressed, are my own and not those of my employer, or Microso=
ft,
> > or anyone else associated with me, including my cats.
> > -----------------------------------------------------
>
> Good Lord, man! If I could only carry you around in my pocket! Thanks,
> Phillip! You're the best!- Hide quoted text -
>
> - Show quoted text -
Phillip, I'm used to the device getting the public IP. What I mean is
that if I take a cable modem, or a dsl modem, and put it on the
network it will be assigned an IP. However, it may or may not work
depending on whether the device is registered/compatible. So in my
mind it would seem as if the VPN router was acting as the DSL modem
(Netopia). Therefore the DSL modem would not be needed.
If I take the DSL modem away then the connection would be non-
existent. That is, that the VPN/Router cannot act as a DSL device. So
technically the signal comes in and hits the DSL. The DSL is assigned
an IP. In IP Passthrough the TCP/IP packets get passed to the VPN/
Router so that it gets the IP address?
So without the DSL there would be no show. So technically, what is
different about bidged ethernet versus IP passthrough?
And what certified person would know this stuff? A CCNA? I don't
recall studying this stuff for MCSE.