Cannot open ports .. DLink modem

[monty77uk]

Hi all,

Trying to get L2TP VPN working (PPTP working already) but cannot seem to get the ports to open up.

Attached are my firewall rules and this is the error I see in the log when I use Open Port Check Tool or try to connect to the VPN:

Jun 2 19:10:05 kernel: Firewall Log -> IN=atm1 OUT=br0 SRC=204.16.252.112 DST=192.168.0.100 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=63721 DF PROTO=TCP SPT=60572 DPT=1701 WINDOW=5840 RES=0x00 SYN URGP=0 MARK=0x8000000

When I test port 1723 which I know works (PPTP VPN) I get 4 lines in the log:

Jun 2 19:20:06 kernel: Firewall Log -> IN=atm1 OUT=br0 SRC=204.16.252.112 DST=192.168.0.100 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=11415 DF PROTO=TCP SPT=42317 DPT=1723 WINDOW=5840 RES=0x00 SYN URGP=0 MARK=0x8000000
Jun 2 19:20:06 kernel: Firewall Log -> IN=atm1 OUT=br0 SRC=204.16.252.112 DST=192.168.0.100 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=11416 DF PROTO=TCP SPT=42317 DPT=1723 WINDOW=46 RES=0x00 ACK URGP=0 MARK=0x8000000
Jun 2 19:20:06 kernel: Firewall Log -> IN=atm1 OUT=br0 SRC=204.16.252.112 DST=192.168.0.100 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=11417 DF PROTO=TCP SPT=42317 DPT=1723 WINDOW=46 RES=0x00 ACK FIN URGP=0 MARK=0x8000000
Jun 2 19:20:07 kernel: Firewall Log -> IN=atm1 OUT=br0 SRC=204.16.252.112 DST=192.168.0.100 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=0 DF PROTO=TCP SPT=42317 DPT=1723 WINDOW=46 RES=0x00 ACK URGP=0 MARK=0x8000000

Any ideas? Driving me nuts!!

...the IP in question (.100) is connected to an Apple AEBS in bridged mode should that make any difference.


Cheers,
Monty

[monty77uk]

OK .. more playing.

Despite the port checker still saying the ports are closed I got L2TP working using a connection from my laptop over 3G network. Bizarrely identical configuration doesn't work on my iPhone but that could well be iOS issue.

Not comfortable that I have an extremely reliable AEBS router that I've now had to put in to bridge mode though so might look into swapping the DLink for a modem only solution in the near future.

Monty

[Kona Owner]

it seems there is a problem with the 1.11 firmware, have you tried rebooting it?