Can you give us info about W8960N setup?

jimasek wrote

Can you give us info about W8960N setup?

What info would you need?
I've not changed much to the defaults, changed the network subnet to my home network subnet (192.168.0.xx), setup ADSL ( BT) , no problems there.
Setup dhcp with about 15 entries for fixed IP addresses, the node in question I tried using both a fixed address outside the dhcp server setup and within it with a fixed address.
The setup a Nat virtual server rule for the port I want to have forwarded from the outside world to the node. Specify the port start and end address as same port no and the IP address of the node.
That should do it, right?
I have a similar setup in my cisco router, when I swap in the td-link one, outgoing connections from the node work, returning traffic to the port in the port forwarding rule does not work.
It feels like the router firewall still blocks the traffic. Using an outside port test website, show the port itself is open.
When returning the cisco router the return traffic comes in again.

Peter

Do you have public IP address on the WAN port?

I'm using the one that BT is assigning and I am using dyndns.
You might be onto something here, I need to see if there is an option in the tp-link router to notify dyndns of the new ipaddress given by BT when swapping the routers.

I haven't asked about ddns, do you know what is the public IP address or not? If you don't know please show me status tab from TP-LINK. Second question what kind of services do you have in local network on those ports?

jimasek wrote

I haven't asked about ddns, do you know what is the public IP address or not? If you don't know please show me status tab from TP-LINK. Second question what kind of services do you have in local network on those ports?

Yes I know what the public address is. When you asked for that I realised that I did not setup ddns, the external connections back are made not using an ip address but a logical dns name registered via dyndns. I 'forgot' to set that up, it was already done in the cisco router.
An other point to look after is the option in the dhcp window.

Enable IGMP Snooping

Standard Mode

Blocking Mode

Default seems to be on and in blocking mode.
This caused considerable grief for my Sonos setup and my Solar monitoring components from SMA. Kept getting dropped connections, setting it to Standard Mode made things far more stable.

Have you tested it from another IP address, another internet connection?

peterbr wrote

An other point to look after is the option in the dhcp window.

Enable IGMP Snooping

Standard Mode

Blocking Mode

Default seems to be on and in blocking mode.
This caused considerable grief for my Sonos setup and my Solar monitoring components from SMA. Kept getting dropped connections, setting it to Standard Mode made things far more stable.

Switching IGMP off completely in both the tp-link router and netgear switch made the environment even more stable. Seems the tp-link router does not like the netgear switch much -;)