That's where my problem is. I can open them up on the linux box, but the moment I put the forwarding rule in they close again. I know the program/server on the other side is listening to the connections because I plugged it directly into my router and port forwarded on that and it worked, it just doesn't work through my suse machine ----------------------------------------------- Sent by freemail.servebeer.com Signup for your free 100mb Mail account today! Full pop3/smtp accounts available!! ----------------------------------------------- -----Original Message----- From: Carlos E. R. [mailto:robin1.listas@tiscali.es] Sent: 26 February 2005 02:27 To: 'Suse Mailing List' Subject: RE: [SLE] Problems with susefirewall2 The Saturday 2005-02-26 at 00:07 -0000, Stephen Furlong wrote:
Needs another bump up as ive had no reply yet :(
I'm no firewall expert, but I'll try.
Im running suse9.2 on my server box connected via wireless to my desktop machine. Im trying to poke through certain ports from my suse box onto my desktop machine. When I use the firewall wizard in yast and use the "expert options" to open the ports (4000:4200) shields up! Lists them as "closed".
Opening a port in the firewall is not enough; there must be a service or daemon behind responding on that port. Till that moment, they should show up as "closed". Also, if your intention is that another (2nd) machine answers on those ports, simply opening them up in the firewall is not enough. -- Cheers, Carlos Robinson -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com