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

Groups > linux.debian.user > #179582

Re: Wan/Lan problem

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

I'm going to join the fray and take a crack at this. I'll try to help as
best I can to resolve the situation in your current setup, but I would like
to say that I agree with what others have posted and would say that this is
a little (but not too much) unorthodox. Typically desktop, server,
application, and personal machines are put behind the router in the IPv4
paradigm. We then use NATing to allow multiple machines onto the interwebs.
However I only say it is somewhat unorthodox, as dedicated network
equipment is often given external IP addresses. It just look like you are
using your Linux box as network equipment and as a personal machine.

I'm going to focus on questions concerning when both NIC's are up, seeing
as this is probably the desired end result.


On Wed, Mar 29, 2017 at 9:51 AM, Mike McClain <mike.junk.46@copper.net>
wrote:

>
> > > 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.
>
>
   1. What does a traceroute show on the Windows box?
   2. What does a tcpdump or wireshark output of a ping to 99.188.244.1
   show on both Linux and Windows?
   3. What happens when you remove the 192.168.1/24 route? Does the Linux
   box then have internet access? Does the Windows box lose internet access?
   4. A quick way to start to narrow down where the problem or problems
   exist is to completely disable your firewall and perform your tests again.
   If any of them succeed then you know it has something to do with netfilter.

I'll try to look at your config more and see if I can spot anything in
particular.

Thanks,
Joshua Schaeffer

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