longfellow21
Member
I am able to port forward for terraria but not for srb2.
have you checked the firewall? it's possible that your firewall is blocking incoming traffic to srb2.
tried all that. Didn't work unfortunately.Made sure this pc's ip address is static.Change it to both and the address make sure it's static and try 5030 TCP/UDP too.
I tried all 4 combinations ofDid you make sure to set the server's room to "Standard"/"Casual" when you tried to host?
i doubt that's going to help, since port-forwarding rules don't impact each other.Hm... maybe try removing the other ports and leave the SRB2 one only?
i doubt that's going to help, since port-forwarding rules don't impact each other.
@longfellow21, what router do you have?
-noipv6
in order to disable ipv6 functionality, since ipv6 hosting is currently broken in 2.2.13.Didnt see anything wrong with first two bullet points.a few points of interests i found:
if the last point in the list works, then you need to start srb2 with
- check the firewall, and make sure it's not configured to block traffic.
- check access control and make sure port 5029 from your system is allowed outgoing and incoming traffic.
- try to configure ipv6 pinhole for your system on port 5029 and verify if ipv6 connections work.
-noipv6
in order to disable ipv6 functionality, since ipv6 hosting is currently broken in 2.2.13.
when connecting via ipv6, you need to use the ipv6 address; enterDidnt see anything wrong with first two bullet points.
Made an ipv6 pinhole for terraria but it didnt work. Not sure if i did it right though.
View attachment 112836
ipconfig
into the command prompt and you should get something along the lines of this:C:\>ipconfig
Windows IP Configuration
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:2042:7be4:9c00:dabb:c1ff:fea6:f874
Link-local IPv6 Address . . . . . : fe80::dabb:c1ff:fea6:f874%3
IPv4 Address. . . . . . . . . . . : 192.168.0.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
IPv6 Address
field is what you need. when connecting directly to the server, you need to use the link-local one, but others connecting from outside need to use the ipv6 address instead. however, if you only have a link-local address, then it's not ipv6 interfering and there's a different issue at play. if you do, try starting srb2 with -noipv6
as mentioned before and that should fix it.I only have a link local ipv6 address. I don't have a regular "ipv6 address."when connecting via ipv6, you need to use the ipv6 address; enteripconfig
into the command prompt and you should get something along the lines of this:
Code:C:\>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:2042:7be4:9c00:dabb:c1ff:fea6:f874 Link-local IPv6 Address . . . . . : fe80::dabb:c1ff:fea6:f874%3 IPv4 Address. . . . . . . . . . . : 192.168.0.20 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1
thatIPv6 Address
field is what you need. when connecting directly to the server, you need to use the link-local one, but others connecting from outside need to use the ipv6 address instead. however, if you only have a link-local address, then it's not ipv6 interfering and there's a different issue at play. if you do, try starting srb2 with-noipv6
as mentioned before and that should fix it.