Re: Wan/Lan problem

From	Henning Follmann <hfollmann@itcfollmann.com>
Newsgroups	linux.debian.user
Subject	Re: Wan/Lan problem
Date	2017-03-30 13:30 +0200
Message-ID	<tqGr8-5AE-15@gated-at.bofh.it> (permalink)
References	<tqarg-7UU-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On March 28, 2017 7:46:02 PM EDT, Mike McClain <mike.junk.46@copper.net> 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
>
>When eth0 is up and eth1 down,
>                    the Linux box can access the web.
>                    'ping ATTrouter' works.
>When eth0 is up and eth1 up,
>                    the Linux box can not access the web.
>                    the Win2K box can access the web.
>                    the Linux box can not access the Win2K shares.
>                    'ping ATTrouter' fails.
>                    'ping -Ieth0 ATTrouter' works.
>When eth0 is down and eth1 up,
>                    the Linux box can access the Win2K shares.
>When eth0 is down and eth1 down,
>                    it's quiet.
>
>The ATT router is set to 'Pass Through' giving the Linux box the ATT
>router's IP address.
>The Linux box is set to use DHCP.
>This might explain why I loose the LAN connection when eth0 up.
>
>Why can the Linux box not see the web while the Win2K box can?
>
>I've not found or at least recognized the problem in the HowTo's.
>Pointer's or suggestions?
>
>Thanks,
>Mike
>
>#   /etc/hosts
>192.168.1.254    ATTrouter
>#192.168.1.64    outbound.att.net    att
>127.0.0.1       localhost
>192.168.1.2     playground      play
>192.168.1.3     south40         s40
>192.168.1.1     router
># ----------------------- end hosts
>
># /etc/networks
>default		0.0.0.0
>loopback	127.0.0.0
>link-local	169.254.0.0
>localnet	192.168.1.0
># ----------------------- end networks
>
># /etc/resolv.conf
>domain attlocal.net
>search attlocal.net
>nameserver 192.168.1.254
># ----------------------- end resolv.conf
>
>#   /etc/network/interfaces
># This file describes the network interfaces available on your system
># and how to activate them. For more information, see interfaces(5).
>
># The loopback network interface
>auto lo
>iface lo inet loopback
>
># The primary network interface
>allow-hotplug eth1
>#   eth0 = onboard eth port
>iface eth0 inet dhcp
>#   eth1 = 3Com PCI 3c905C card
>iface eth1 inet static
>        address 192.168.1.2
>        netmask 255.255.255.0
>        network 192.168.1.0
>        broadcast 192.168.1.255
># dns-* options are implemented by the resolvconf package, if installed
>        dns-nameservers 208.67.222.222 208.67.220.220
># ----------------------- end interfaces
>
>--
>"I reckon some folks figure it a compliment to be called
>'broad-minded.'
>Back home, broad-minded is just another way of saying a feller is too
>lazy to form an opinion."    - Will Rogers



You put eth0 and eth1 into the same network segment.
That most likely is your problem
Either you bridge eth0 and eth1 or if you want your linux box as a firewall you pick a different ntwork for eth1

-- 
Henning Follmann

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