[nflug] Router Questions

kobear at sharedbrain.net kobear at sharedbrain.net
Sat Apr 8 08:33:49 EDT 2006


Joe,

You can see if you are using DHCP by going to a command prompt (Start --> Run
--> cmd) and typing "ipconfig /all".  Somewhere in there there should be a line
that says Dhcp Enabled : Yes|No

HTH,
Kyle


Quoting Joe <josephj at main.nc.us>:

> I have it configured as Dave suggested (see my original post).
> The DSL modem lives at 192.168.1.1 (I'm not sure what else it uses, but
> they're in the 192.168.1.x range.)
> The VoIP uses 192.168,251,x addresses.
> I got these from the tech help configuring them and from Zone Alarm
> firewall logs.  I have added both of these local subnets to my trusted
> zones in Zone Alarm.  The DSL modem works a bit better now - less
> arguing after I kill it by inserting the VoIP - but the VoIP still
> doesn't work or pass through the Internet.
>
> Verizon sent me a new modem and Sunrocket finally called back from level
> 3.  Now I just have to get back to the location so I can call them back
> and work on it again.
>
> So the consensus seems to be that I don't need a router at this point.
> That I should just hook them up in a row and get them to work.
>
> I have no idea what Win 98se does regarding DHCP (I was at the last
> meeting, but I'm still not even sure what DHCP is. Forget configuring
> it!)  I don't really want to get into the depths of networking any more
> than I have to at this point.  I'm sure I'll have to learn quite a bit
> more if I ever get wireless equipment in the future, but for now, I can
> wait.
>
> Any idea how I can tell about DHCP on my laptop?  I've been running
> winipgcfg (release and restore) and sometimes that seems to help, but I
> don't know if that has anything to do with DHCP.
>
> Joe
>
> kobear at sharedbrain.net wrote:
> > Quoting "David J. Andruczyk" <djandruczyk at yahoo.com>:
> >
> >
> >> --- Joe <josephj at main.nc.us> wrote:
> >>
> >>
> >>> I understand what a router is, but I've never worked with one, so
> >>> I've
> >>> got some basic questions.  I don't expect anyone on this list to
> >>> debug
> >>> my VoIP (SunRocket) problem.  The questions below are mostly OS and
> >>> vendor independent.
> >>>
> >>> I'm having trouble getting VoIP to work for my partner (I'll be
> >>> talking
> >>> to VoIP level 3 support later.)  She has Verizon DSL.  I don't
> >>> remember
> >>> the exact speeds, but it's about 800/168 (the slowest/cheapest).  The
> >>>
> >>> VoIP says it needs 90/90 to work.
> >>>
> >>> Currently, the DSL line comes into the Modem, out to the VoIP box,
> >>> and
> >>> then from the VoIP box into the notebook (Win 98se). Nothing has
> >>> wireless capabilities.
> >>>
> >>> When I hook up the DSL without the VoIP box, it works fine.  When I
> >>> put
> >>> the VoIP in the middle,  not only does it not work, but the DSL goes
> >>> away and when I remove the VoIP box, I have to argue with the DSL box
> >>>
> >>> for awhile to get it to work again.
> >>>
> >> Solution.  Install in sequence below:
> >> DSL line -> DSL modem-> VoIP box - >Laptop
> >>
> >> power off all device (INCLUDING the dsl modem)
> >> power up DSL modem,  wait till all lights on it say it's ready and
> >> working,   power up Voip box make sure it becomes "ready",  then power
> >> up laptop, and all should be working correctly now.  Make sure the
> >> laptop is configured for DHCP. (almost all are).
> >>
> >> Reason:  DSL and cable modems detect the MAC address of the device
> >> directly plugged into them (whether it be a router, computer, appliance
> >> device, etc), and refuse to accept traffic from any other MAC address
> >> unless powercycled.    MAC addresses do NOT cross router boundaries
> >> (read up on the OSI model if you really want to know why). The Voip box
> >> is essentially a simple router device with added gee-whiz stuff inside
> >> (the voip crap).
> >>
> >>
> >
> >
> > Actually, I think he said that he never had the DSL router not be the first
> > device facing the DSL network.  If that is the case, then the MAC address
> would
> > not change.
> >
> > I think that what is going on here is that you have a IP address
> > conflict/overlap the two networks.
> >
> > Let's take a standard out-of-the-box config.  Most routers plant the
> internal
> > addresses on the 192.168.1.x network.  If both the DSL router and the VOIP
> > router are doing this, then you have the following kind of problem:
> >
> > DSL Line (Public IP's) -->  DSL Modem (192.168.1.0/32 or 192.168.1.1) -->
> VOIP
> > Router (192.168.1.0/32 or 192.168.1.1) --> Internal network
> (192.168.1.0/24).
> >
> > Notice that both routers think that their address is 192.168.1.1.  When the
> VOIP
> > router gets traffic that it does not know what to do with, it is supposed
> to
> > hand it off to it's default gateway, which is the DSL modem.  But since it
> has
> > the same IP address as the modem, it cannot find a route to it, and
> therefore a
> > routing loop is created.
> >
> > Given this, most verizon routers can be setup in Bridged mode, thereby the
> VOIP
> > router can be given the public IP address for its WAN port and the problem
> is
> > likely solved.
> >
> > HTH,
> >
> > Kyle
> >
> >
> >
> >>
> >> Dave J. Andruczyk
> >>
> >> __________________________________________________
> >> Do You Yahoo!?
> >> Tired of spam?  Yahoo! Mail has the best spam protection around
> >> http://mail.yahoo.com
> >> _______________________________________________
> >> nflug mailing list
> >> nflug at nflug.org
> >> http://www.nflug.org/mailman/listinfo/nflug
> >>
> >>
> >
> >
> >
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> > _______________________________________________
> > nflug mailing list
> > nflug at nflug.org
> > http://www.nflug.org/mailman/listinfo/nflug
> >
> >
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug



More information about the nflug mailing list