issue with thibor

Discussion in 'HyperWRT Firmware' started by taichi, Nov 29, 2005.

  1. taichi

    taichi Network Guru Member

    I might have found a problem with Thibor 10192005 release..
    I had Thibor working fine and its a great firmware..
    My ip was 192.168.103 and had azureus running fast and smooth with no Nat problem but then my router changed my ip to 192.168.100 and so I changed all the port forwarding to the new ip.. Thats when the problem started, my Azureus showed all my connections as NAT. The only way I got it bt working again was to use a static 192.168.103 ip even though I had port forward to the correct port when the ip was 192.168.100..

    I was looking at the iptable and notice:
    10 logaccept udp -- anywhere udp dpt:1070
    11 logaccept udp -- anywhere udp dpt:1720
    12 logaccept tcp -- anywhere tcp dpt:1720
    13 logaccept tcp -- anywhere tcp dpt:1720
    14 logaccept udp -- anywhere udp dpt:1720

    Can anyone explain what was happen?
    As you probably notice im a newbie with linux/networking

  2. Thibor

    Thibor Super Moderator Staff Member Member

    why did you not create a static lease for your machine running azureus?
    if you telnet into the router and flush the firewall rules it should create the correct mappings, also do "nvram get forward_port0" and port1, port2, port3 for UPnP mappings which also could be the cause. i have seen azureus not release the port mappings before. to flush the firewall rules in telnet do "iptables -F; reboot"
  3. taichi

    taichi Network Guru Member

    thanks.. I'll try that later tonight
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice