Hi,
Jari Marikainen wrote:
I would like to forward incoming traffic from internet to "<195.198.111.x> port 80" to "<some other ip on the internet> port 80" in FC3 on the same interface.
I would try the DNAT/SNAT iptables targets, along the lines of: iptables -t nat -A PREROUTING -p tcp --dport 80 -d 195.198.111.x \ -j DNAT --to-destination 65.114.4.69 iptables -t nat -A POSTROUTING -p tcp --dport 80 -d 65.114.4.69 \ -j SNAT --to-source <your external IP address on this machine>
The second line makes the real server send it's replies through the same path (otherwise it will reply directly to the client)
You have to enable/allow forwarding for everything to work.
hth, /Andy
--- Andy ag1234@carmen.se wrote:
Hi,
Jari Marikainen wrote:
I would like to forward incoming traffic from internet to "<195.198.111.x> port 80" to "<some other ip on the internet> port
80"
in FC3 on the same interface.
I would try the DNAT/SNAT iptables targets, along the lines of: iptables -t nat -A PREROUTING -p tcp --dport 80 -d 195.198.111.x \ -j DNAT --to-destination 65.114.4.69 iptables -t nat -A POSTROUTING -p tcp --dport 80 -d 65.114.4.69 \ -j SNAT --to-source <your external IP address on this machine>
The second line makes the real server send it's replies through the same path (otherwise it will reply directly to the client)
You have to enable/allow forwarding for everything to work.
hth, /Andy
Are you sure? If I read the original note correctly, he wants to have his machine see an incoming packet on one interface, and then forward it to another address on the SAME interface. And he specifically said that he wants to catch traffic coming FROM the internet and forward it TO a different address, also on the internet.
That's not port-forwarding, that's redirection, and it is best handled by setting up Apache to recognize the incoming connection, and then setting a REDIRECT which sends a message back to the client to tell it to go look somewhere else.
Unless he has a multi-homed system with more than one interface on the internet, I'm not sure that forwarding/routing will work.
Am I wrong?
David
__________________________________ Do you Yahoo!? All your favorites on one personal page � Try My Yahoo! http://my.yahoo.com
Recently, all of the video in firefox has stopped working. I assume this is because I keep letting yum update to the latest version (I'm now on firefox 1.0.0.14) and something has broken.
In trying to troubleshoot this I'm come to this question: Where does firefox look for its plugins: /usr/lib/firefox-2.0.0.14/plugins or /usr/lib/mozilla/plugins? Here are the contents of both directories:
root@PuteB Mon May 05 07:33:19 [355] /usr/lib/firefox-2.0.0.14/plugins $ ls libflashplayer.so libnullplugin.so libunixprintplugin.so
root@PuteB Mon May 05 07:25:25 [353] /usr/lib/mozilla/plugins $ ls gecko-mediaplayer-dvx.so libswfdecmozilla.so gecko-mediaplayer-dvx.xpt libtotem-basic-plugin.so gecko-mediaplayer-qt.so libtotem-basic-plugin.xpt gecko-mediaplayer-qt.xpt libtotem-complex-plugin.so gecko-mediaplayer-rm.so libtotem-complex-plugin.xpt gecko-mediaplayer-rm.xpt libtotem-gmp-plugin.so gecko-mediaplayer.so libtotem-gmp-plugin.xpt gecko-mediaplayer-wmp.so libtotem-mully-plugin.so gecko-mediaplayer-wmp.xpt libtotem-mully-plugin.xpt gecko-mediaplayer.xpt libtotem-narrowspace-plugin.so libflashplayer.so libtotem-narrowspace-plugin.xpt libgnashplugin.so nphelix.so libjavaplugin.so nphelix.xpt
Which files should be where? Is there any logic to this system?
Thanks for any insights or suggestions. --Jerry
On 2008-05-05, Gerhard Magnus magnus@agora.rdrop.com wrote:
Recently, all of the video in firefox has stopped working. I assume this is because I keep letting yum update to the latest version (I'm now on firefox 1.0.0.14) and something has broken.
In trying to troubleshoot this I'm come to this question: Where does firefox look for its plugins: /usr/lib/firefox-2.0.0.14/plugins or /usr/lib/mozilla/plugins?
Fedora's Firefox looks in /usr/lib/firefox-2.0.0.14/plugins, but some 3rd party plugin installers drop them in /usr/lib/mozilla/plugins. Just create sym-links from /usr/lib/mozilla/plugins to /usr/lib/firefox-2.0.0.14/plugins, e.g.:
ln -s /usr/lib/mozilla/plugins/* /usr/lib/firefox-2.0.0.14/plugins/
John Thompson wrote:
On 2008-05-05, Gerhard Magnus magnus@agora.rdrop.com wrote: Fedora's Firefox looks in /usr/lib/firefox-2.0.0.14/plugins, but some 3rd party plugin installers drop them in /usr/lib/mozilla/plugins. Just create sym-links from /usr/lib/mozilla/plugins to /usr/lib/firefox-2.0.0.14/plugins, e.g.:
ln -s /usr/lib/mozilla/plugins/* /usr/lib/firefox-2.0.0.14/plugins/
Firefox is *supposed* to use an internal search path to look for plugins. (According to the last Mozilla documentation I read) its supposed to include the current install directory (in this case /usr/lib/firefox-2.0.0.14.plugins), a generic firefox location (usually /usr/lib/firefox/plugins) and the old mozilla directory /usr/lib/mozilla/plugins. If Fedora is modifying this path, then they are changing users expectations, which usually is a bad thing. However, I will agree with you. I haven't had luck with the above either, and I usually end up putting symlinks in place to make it work the way I want it to.