Re: *sigh* Can not get LAN internet ready since FC3 install

From: Stormblaze (stormblaze_at_gmail.com)
Date: 11/10/04

  • Next message: Kevin Old: "iptables still seems active even after disabled in FC 3"
    Date: Tue, 9 Nov 2004 23:08:09 -0500
    To: edward@tripled.iinet.net.au
    
    

    I got it working. I'd forgotten to turn ip forwarding on. Been 4 years
    since I turned it on last time lol. My iptables script works. I knew
    something else was up when I flushed everything and just created
    default policies to ACCEPT and it still didn't.

    Once ip forwarding was turned on all is well.

    Gonna go to bed now. Tomorrow I tackle configuring my web server and
    samba and then hopefully start getting mysql up and running.

    Xwindows is fubar'd but I changed runlevel to 3 for now. I'll tackle
    it later. I see that some issues with i810 are known so I'll do some
    research.

    On Wed, 10 Nov 2004 11:20:06 +0800, Edward <edward@tripled.iinet.net.au> wrote:
    >
    >
    >
    >
    > Stormblaze wrote:
    >
    > > This is a fresh install. Previously I had Redhat 8 running nicely. I
    > > installed FC3 and configured the network and that went easy. The linux
    > > box can get to the internet just fine. But none of the computers on my
    > > network can.
    > >
    > > I had an iptables perl script that I've used for a while now. I ran it
    > > and even after it ran successfully I could not get to the internet
    > > from any of my workstation computers.
    > >
    > > I tried just creating some simple default policies set to ACCEPT just
    > > to try and get internet access but nothing has worked.
    > >
    > > Has something changed? How can I get this working?
    > >
    > > At this point I just want to be able to access the internet using the
    > > Linux server as a gateway. It has internet connectivity already and
    > > that's working fine. I can ping to the Linux box from my workstation
    > > just fine. I can even use ssh to log into the box so the LAN
    > > connection is working fine. Somehow I think the box isn't forwarding
    > > anything.
    > >
    > > ---
    > > "We should have a way of telling people they have bad breath without
    > > hurting their feelings. Like: Well I'm bored. Let's go brush our
    > > teeth. Or, I've got to make a phone call...hold this gum in your
    > > mouth.
    >
    > can you show us iptables -L -v?
    >
    > Without it we'd just be guessing and not really getting anywhere methinks.
    >
    > Regards,
    > Ed.
    >
    >

    -- 
    ---
    "We should have a way of telling people they have bad breath without
    hurting their feelings. Like: Well I'm bored. Let's go brush our
    teeth. Or, I've got to make a phone call...hold this gum in your
    mouth.
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Kevin Old: "iptables still seems active even after disabled in FC 3"

    Relevant Pages

    • Re: How would you like to find this?
      ... floating around the Internet for the last 10 years or so. ... I would like to share a letter a friend recently sent to someone (no ... Neiman Marcus doesn't really sell a $200 cookie recipe. ... browser since you're probably forwarding us a copy of the Neiman Marcus ...
      (rec.autos.makers.mazda.miata)
    • Re: Forwarders versus root hints
      ... > There was some confusion on my part about the benfits forwarding offers ... DNS server on the firewall/gateway (e.g., ... very imporant server from visiting the Internet) it just adds ... And it will not work on a TRUE DNS 'root', ...
      (microsoft.public.windows.server.dns)
    • RE: Whiteboard and application sharing do not work
      ... You are connected to the Internet through a non-UPnP symmetric NAT ... > You are connected to the Internet through a non-UPnP symmetric NAT ... > Port Forwarding: ... > ports under Port Forwarding. ...
      (microsoft.public.windowsxp.messenger)
    • Re: iptables - internal addresses cannot see external interface
      ... I've managed to kludge the attached ... > iptables script together, and everything seems to be working so far, ... > server facing the internet. ...
      (comp.os.linux.security)
    • Re: iptables - internal addresses cannot see external interface
      ... > iptables script together, and everything seems to be working so far, ... Internet clients would still be able to find your outside connection from ... any internet DNS hostname or IP. ...
      (comp.os.linux.security)