Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179573

Re: Wan/Lan problem

Show all headers | View raw

On Wednesday, March 29, 2017 03:17:37 AM David Christensen wrote:
> On 03/28/2017 04:46 PM, Mike McClain wrote:
> > Howdy,
> > I have a WAN/LAN challenge I'm hoping for help with.
> > 
> > I'm runniing Debian 7.11 on a Pentium 3 with 250MB ram.
> > 
> > mike@/deb7:~> uname -a
> > Linux playground 3.2.0-4-686-pae #1 SMP Debian 3.2.84-2 i686 GNU/Linux
> > 
> > The situation is this:
> >      phone        eth0         eth1
> > 
> > AT&T-------|   |--------|   |--------|   |-------|   |
> > 
> >         AT&T modem/     Linux         my         Win2K
> >         
> >             router       box         router       box

I apologize because this doesn't answer your question but proposes an 
alternative arrangment that, I believe, would be easier to configure.

I don't know the physical arrangement of your devices (in your home or office), 
but my arrangement (and most arrangements I've seen) are a little different and 
maybe you want to try an arrangment more like this:

Put your router immediately after the AT&T modem, then (assuming there are 
multiple ethernet ports on the router), put your Linux box on one eth port and 
the Windows box on another.  (That would require 3 ports on the router.)

If you don't have 3 ports on the router, consider getting a switch to place 
after the router, and put the Linux and Windows boxes on 2 separate outputs 
from the switch.

Either of these is a much more standard arrangement, and I have very little 
trouble with any of this.  (The troubles I have had are not relevant to the 
arrangement--things like Earthlink / Verizon outages and dealing with their 
customer non-support, an anomaly in how a Westell modem worked (now using a 
ZyXel), and difficulties in understanding and configuring QOS (primarily for 
VOIP).)

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Wan/Lan problem Mike McClain <mike.junk.46@copper.net> - 2017-03-29 03:20 +0200
  Re: Wan/Lan problem Dan Ritter <dsr@randomstring.org> - 2017-03-29 04:20 +0200
    Re: Wan/Lan problem Mike McClain <mike.junk.46@copper.net> - 2017-03-29 18:10 +0200
      Re: Wan/Lan problem Joshua Schaeffer <jschaeffer0922@gmail.com> - 2017-03-29 20:50 +0200
      Re: Wan/Lan problem David Christensen <dpchrist@holgerdanske.com> - 2017-03-29 21:20 +0200
      Re: Wan/Lan problem <tomas@tuxteam.de> - 2017-03-29 21:50 +0200
  Re: Wan/Lan problem David Christensen <dpchrist@holgerdanske.com> - 2017-03-29 09:20 +0200
    Re: Wan/Lan problem rhkramer@gmail.com - 2017-03-29 15:00 +0200
      Re: Wan/Lan problem Mike McClain <mike.junk.46@copper.net> - 2017-03-29 23:30 +0200
        Re: Wan/Lan problem rhkramer@gmail.com - 2017-03-30 15:50 +0200
  Re: Wan/Lan problem <tomas@tuxteam.de> - 2017-03-29 11:50 +0200
  Re: Wan/Lan problem kAt <giathnygeia@openmailbox.org> - 2017-03-29 23:10 +0200
  Re: Wan/Lan problem Henning Follmann <hfollmann@itcfollmann.com> - 2017-03-30 13:30 +0200
    Re: Wan/Lan problem Mike McClain <mike.junk.46@copper.net> - 2017-03-31 02:50 +0200
      Re: Wan/Lan problem Henning Follmann <hfollmann@itcfollmann.com> - 2017-03-31 03:50 +0200
        Re: Wan/Lan problem [SOLVED] Mike McClain <mike.junk.46@copper.net> - 2017-03-31 23:10 +0200

csiph-web