All of lore.kernel.org
 help / color / mirror / Atom feed
From: khollan <khollan@daktronics.com>
To: linuxppc-embedded@ozlabs.org
Subject: XLlTemac port forwarding probelm?
Date: Mon, 2 Jun 2008 14:37:26 -0700 (PDT)	[thread overview]
Message-ID: <17611404.post@talk.nabble.com> (raw)


Hi everyone,

I'm using my custom Xilinx board as a gateway for a networked webcam.  The
board is based on the ml410.  Basically eth1 is connected to the outside
world and eth0 is connected to the webcam.  I'm port forwarding port 80 with
iptables.  I can connect to the webcams web server by going to the IP
address of the Xilinx board just fine, but here comes my problem...

After the first initial load, which is relatively fast, all subsequent
refreshes become ungodly slow.  If I ifconfig down eth1 and bring it back up
the next refresh is fast again.  

I'm using Xilinx's Local Link Mac with the Fifo interface instead of DMA. 
Any ideas of whats going on?

Thanks

Kevin
-- 
View this message in context: http://www.nabble.com/XLlTemac-port-forwarding-probelm--tp17611404p17611404.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

                 reply	other threads:[~2008-06-02 21:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17611404.post@talk.nabble.com \
    --to=khollan@daktronics.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.