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

Groups > linux.debian.user > #179569

Re: Wan/Lan problem

Show all headers | View raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Mar 28, 2017 at 04:46:02PM -0700, 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
> 
> 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.

To repeat what Dan said with slightly different wording... check
your routing here:

  /sbin/route -n

(and check that above, "when eth0 is up and eth1 is down").

I'll bet that the "Linux box" default route has moved from
"AT&T modem/router" to "my router", and now things that the
InterTubes are now to be found that way.

(I skip the rest for when we have some more light on the
above part -- bumping one's head on a Gateway Goblin is no
fun ;-)

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljbgYMACgkQBcgs9XrR2kaSNwCdHsBY1kNplnCo/Npr3wjdg43Y
SYEAnjfcYe+dUt+uRui6Y7RxQRjAhxMG
=N+Fp
-----END PGP SIGNATURE-----

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