search for: find_interface_addresses

I am having problems making RTSP connections to a Windows Streaming Media Server (ie "connecting to media...." but WMP never connects). There are no error messages in /var/log/messages. It was suggested to me that SNAT might perform better than MASQ in this respect. I edited my shorewall/masq file as such: eth0 eth1 12.34.56.78 or should it be? eth0 10.0.0.0/24

Hello Shorewall list, I''m a happy Shorewall user since a few years now and everything works fine for me except one thing that I try to implement since a week, the multi-isp. I''ve downloaded the 2.4.0 Stable release yesterday and tried the RC2 since a week. My config is a Debian running a kernel 2.4.27 home made with the CONNMARK.diff patch applied I''m using 2 ISP,

I''ve installed Shorewall 3.0.5 on a Debian Sarge box, and I''m attempting to route internet traffic through a couple of ISPs, and I''ve come up against some problems. The first is that one of my links is a pppoe connection to a wireless modem, and I can''t configure it to have a static IP address... therefore I can''t see how I can set up the two

I have two feeds, one with a static IP and one with a dynamic IP. How can I configure a Multi-ISP setup with the dynamic IP, or can I? I don''t think the gateway will change, just the interface IP. -- Chris Mason NetConcepts (264) 497-5670 Fax: (264) 497-8463 Int: (305) 704-7249 Fax: (815)301-9759 UK 44.207.183.0271 Cell: 264-235-5670 Yahoo IM: netconcepts_anguilla@yahoo.com --

My dcgui-qt (chat/file-sharing program) doesn''t work and I''m pretty sure it''s my firewall settings. dcgui-qt is a direct connect (file sharing & chat) client. According to the FAQ here (http://dcplusplus.sourceforge.net/faq/faq.php) all I should need to do is: ------- #ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL #

I''ve upgraded a 3-interface system from 2.0.8 to 3.2.6 on Debian, and I''m not able to make DNAT work anymore. If someone could offer a suggestion of where to look to fix this, it would be very much appreciated. Problem Summary: If I set DETECT_DNAT_IPADDRS=Yes, then I can''t access anything on my DMZ via DNAT. If I set DETECT_DNAT_IPADDRS=No, then **EVERYTHING**

I''ve upgraded a 3-interface system from 2.0.8 to 3.2.6 on Debian, and I''m not able to make DNAT work anymore. If someone could offer a suggestion of where to look to fix this, it would be very much appreciated. Problem Summary: If I set DETECT_DNAT_IPADDRS=Yes, then I can''t access anything on my DMZ via DNAT. If I set DETECT_DNAT_IPADDRS=No, then **EVERYTHING**

...qt ip rule del fwmark 1 + echo qt ip rule del fwmark 1 + eval qt ip rule del fwmark 1 ++ qt ip rule del fwmark 1 ++ ip rule del fwmark 1 + ensure_and_save_command ip rule add fwmark 1 table 1 + eval ip rule add fwmark 1 table 1 ++ ip rule add fwmark 1 table 1 + echo ip rule add fwmark 1 table 1 ++ find_interface_addresses eth0 ++ ip -f inet addr show eth0 ++ grep inet ++ sed ''s/inet //;s/\/.*//;s/ peer.*//'' + for address in ''$(find_interface_addresses $interface)'' + run_and_save_command qt ip rule del from 200.173.215.82 + echo qt ip rule del from 200.173.215.82 + eval qt ip rule...