Topic: Forwarded port doesn't work, logfile says denied?

[Makje]

At home we've got SME 6.5 running for samba and internet acces. Today i wanted to install a p2p program called DC++ which i've had running for years on different locations with various routers (clarkconnect, freesco etc), but not yet on my present location, isp ans SME.

To get in active mode i have to forward a port directly to me, which i did, but i doesn't work. I've forwarded both TCP and UDP port 1228 to my local network adress and checked that it's all typed correctly. While trying to find the problem i stumbled on the logs that SME made and from 13:00 today (that's when i started with DC++) i've got a lot of logs like this:

Jan 28 13:21:17 smeprive kernel: denylog:IN=eth1 OUT=eth0 SRC=87.3.18.28 DST=192.168.16.107 LEN=174 TOS=0x00 PREC=0x20 TTL=117 ID=47098 PROTO=UDP SPT=1082 DPT=1228 LEN=154
Jan 28 13:21:17 smeprive kernel: denylog:IN=eth1 OUT=eth0 SRC=217.197.178.60 DST=192.168.16.107 LEN=228 TOS=0x00 PREC=0x20 TTL=113 ID=23967 PROTO=UDP SPT=1869 DPT=1228 LEN=208
Jan 28 13:21:17 smeprive kernel: denylog:IN=eth1 OUT=eth0 SRC=87.3.27.129 DST=192.168.16.107 LEN=178 TOS=0x00 PREC=0x20 TTL=116 ID=59899 PROTO=UDP SPT=2662 DPT=1228 LEN=158
Jan 28 13:21:17 smeprive kernel: denylog:IN=eth1 OUT=eth0 SRC=82.52.129.139 DST=192.168.16.107 LEN=149 TOS=0x00 PREC=0x20 TTL=117 ID=43756 PROTO=UDP SPT=3434 DPT=1228 LEN=129
Jan 28 13:21:17 smeprive kernel: denylog:IN=eth1 OUT=eth0 SRC=87.3.18.28 DST=192.168.16.107 LEN=159 TOS=0x00 PREC=0x20 TTL=117 ID=47099 PROTO=UDP SPT=1082 DPT=1228 LEN=139

192.168.16.107 is my local network adress and the destination port 1228 is also correct (the UDP protocol is mostly used for searching for files when using DC++, which is the best way of checking wether active mode was succesfull).

My question now offcourse is: Why does SME deny acces on port 1228 to me when i've made a port forwarding rule for that and how do i solve it??

[Makje]

Nobody has any idea? I've checked it over and over and the settings appear to be right. I've altered the forwarded port to 1229 but still the same problem, checked internal ip and it just IS correct.

Jan 30 22:59:42 smeprive kernel: denylog:IN=eth1 OUT=eth0 SRC=80.74.196.84 DST=192.168.16.107 LEN=165 TOS=0x00 PREC=0x20 TTL=112 ID=59565 PROTO=UDP SPT=1147 DPT=1229 LEN=145
Jan 30 22:59:42 smeprive kernel: denylog:IN=eth1 OUT=eth0 SRC=80.74.196.84 DST=192.168.16.107 LEN=153 TOS=0x00 PREC=0x20 TTL=112 ID=59566 PROTO=UDP SPT=1147 DPT=1229 LEN=133

When i remove the forwarding of port 1229 to my ip i still get the same logfiles as when i do forward port 1229, so i can only conclude that it's SME that is blocking port 1229-even after i've forwarded it, but WHY?

By the way, SME is on Server Mode servergateway. Am i missing something else? some setting that i forgot?

[CharlieBrady]

My question now offcourse is: Why does SME deny acces on port 1228 to me when i've made a port forwarding rule for that and how do i solve it??

It's possible there's a bug. Have you applied all available updates? Have you checked the bug tracker? Have you considered reporting a bug?