My linux is using shorewall 2.4.6. A few days ago, I check that the upnp library for linux is forked to another new project and updated to 1.4.x and the cvs version of linux-igd is also updated Then I again to build up a upnp gateway on my existing linux firewall gateway. All compilation process is smooth with having any errors. According to the upnp doc., I added route add -net 239.0.0.0 netmask 255.0.0.0 eth1 then started upnpd ppp0 eth1 no any errors log found in debug and messages log but my windows xp client still can''t regonize a upnp device (p.s. the upnp service of xp is started) Is there any configure need to add in shorewall ? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net''s Techsay panel and you''ll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
On Thu, 2006-07-20 at 10:51 +0800, Adrian Mak wrote:> > Is there any configure need to add in shorewall ?I don''t know -- see http://catb.org/esr/faqs/smart-questions.html#prune -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net''s Techsay panel and you''ll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
should I apply this patch on 2.4.x version mentioned in this http://www.shorewall.net/2.0/UPnP.html ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net''s Techsay panel and you''ll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
On Wed, 2006-07-19 at 20:13 -0700, Tom Eastep wrote:> On Thu, 2006-07-20 at 10:51 +0800, Adrian Mak wrote: > > > > > Is there any configure need to add in shorewall ? > > I don''t know -- see http://catb.org/esr/faqs/smart-questions.html#pruneAdrian, Let me try to explain why your question got the response that it did. It is unclear from your post if you have a currently working upnpd running under Shorewall or if you are trying to make it work from scratch. So your ending question "Is there any configure need[ed] in Shorewall?" was not possible to answer in any helpful way. Yes, Shorewall configuration is required for UPnP and there is documentation that explains that. Is there additional Shorewall configuration required to use the new version? Since you report that the Shorewall-generated ruleset isn''t issuing any messages, that is very unlikely. You have asked in a separate post if you need to patch the new version of upnpd -- I''ve looked at the CVS tree on Sourceforge and the answer appears to be "No". Adrian -- someone has to go first when new things are attempted. It appears that you are the first person on the Shorewall Users list to try the new UPnP code; so asking here what to do to make it work is probably not going to get you anywhere. If you do have a working setup using the old patched upnpd and the old library, then it would be useful if you would inform the new linuxigd and library developers that the same setup using the new code doesn''t work -- I''m sure that they will be interested in helping you solve the problem. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net''s Techsay panel and you''ll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Yes, you appear to be at the same stage I was once at trying to get UPnP working. I think what you''ll find is you''ll need to run tcpdump or ethereal on your internal interface, to listen out for UPnP packets - you might want to put logging on for all shorewall rules/policies, I found them helpful in tracking down how far the packets were going through the server (if they were making it to the upnpd daemon). As Tom pointed out, if you could post a note of what you did to get it working, it''d help everyone out - especially the developers, if the new code is broken. Thanks, Jan Mulders On 20/07/06, Tom Eastep <teastep@shorewall.net> wrote:> > On Wed, 2006-07-19 at 20:13 -0700, Tom Eastep wrote: > > On Thu, 2006-07-20 at 10:51 +0800, Adrian Mak wrote: > > > > > > > > Is there any configure need to add in shorewall ? > > > > I don''t know -- see http://catb.org/esr/faqs/smart-questions.html#prune > > Adrian, > > Let me try to explain why your question got the response that it did. > > It is unclear from your post if you have a currently working upnpd > running under Shorewall or if you are trying to make it work from > scratch. So your ending question "Is there any configure need[ed] in > Shorewall?" was not possible to answer in any helpful way. Yes, > Shorewall configuration is required for UPnP and there is documentation > that explains that. Is there additional Shorewall configuration required > to use the new version? Since you report that the Shorewall-generated > ruleset isn''t issuing any messages, that is very unlikely. > > You have asked in a separate post if you need to patch the new version > of upnpd -- I''ve looked at the CVS tree on Sourceforge and the answer > appears to be "No". > > Adrian -- someone has to go first when new things are attempted. It > appears that you are the first person on the Shorewall Users list to try > the new UPnP code; so asking here what to do to make it work is probably > not going to get you anywhere. > > If you do have a working setup using the old patched upnpd and the old > library, then it would be useful if you would inform the new linuxigd > and library developers that the same setup using the new code doesn''t > work -- I''m sure that they will be interested in helping you solve the > problem. > > -Tom > -- > Tom Eastep \ Nothing is foolproof to a sufficiently talented fool > Shoreline, \ http://shorewall.net > Washington USA \ teastep@shorewall.net > PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > > iD8DBQBEv43bO/MAbZfjDLIRAsrpAJ9v2KLIoCIs+TU0+K9/8FZMVhYvrgCgm06/ > JKr32WWILUmtnFK4RGNiGas> =gMj3 > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net''s Techsay panel and you''ll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users > > >------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net''s Techsay panel and you''ll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV