Jump to content

XelsFIN

Members
  • Posts

    15
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by XelsFIN

  1. Hi,

    LW is looking for an ECL team

    Little bit about me

    I've played EASHL since NHL10. I've been almost exclusively a right handed left winger. My experience in league games goes back to ECL predecessor consolehockey. In ECL I've played a couple of seasons in ECL Pro with Voodoo People and Nemesis. Last season i had a break from league games and played clubgames with Club De Caballeros

    Playing Style

    As a winger I'm an opportunistic forechecker and a defensively responsible player. On the offensive side I'm always trying set myself up for a onetimer pass on a leftside, scoring goals is my biggest upside and I'm decent at stickhandling. I fancy a bit less of a straightforward game and like to play with players looking for soft spots on the ice, where I could pass to, edging towards a scoring chance.

    What I'm looking for in a club

    I'm looking for a Pro or a Lite club on the rise. Team that has a fun atmosphere and players with a positive attitude. I prefer a Finnish speaking team.

    I'm able to play most evenings and I have no connection issues
     

    If you are interested you can msg me on PSN:  XelsFIN

    EDIT: I've found a team

    Best Regards,

    Xels

    • Like 5
    • Thanks 2
    • Love it! 2
  2. 12 minutes ago, Kenu said:

    I moved this topic to the NHL 16-section, as I see that is more fitting.

    Has anyone blocked the IP using a Cisco router? I'm using the Cisco EPC3825 router (provided by DNA) and I can't seem to get it working. I tried using the IP-filtering page for this in the router settings, but adding that IP gives me an "Invalid IP address" error.

    Is it better to connect to the router some other way than through the browser interface? I don't see any command options on my router, similar to what @XelsFIN mentioned about his Buffalo.

    The web interface should suffice, if there is no option in the webinterface then i highly doubt it´s possible to do with said router.

     

    Here is what mine looks like, quite basic router model, Buffalo Nfiniti WZR-HP-G300NH2EU:

    Untitled.png

    • Like 1
  3. If anybody is using any of the Buffalo wrt-line routers go to Administration -> Commands

    paste these, and click run commands button:

    iptables -I OUTPUT -d 159.153.95.65 -j logdrop
    iptables -I FORWARD -d 159.153.95.65 -j DROP

    now you should have no way of accessing that server, cant ping or trace. If you reboot the router then you have to this again, i don't advise using the write to firewall option in commands section as iptables command writes directly to Linux kernel running on your router.

    • Like 1
  4. I'm still able to ping gosprodfeapp0474.ea.com so i guess my Buffalo router only blocks web page content from opening when url is blocked, probably not gonna do me anything good then

    Managed to get it blocked with my router, i cant ping it anymore, no access what-so ever to that server =) Had to use Iptables commands in administration in WRT. If anyone has DD-WRT based router you can try adding this to admin commands:

    iptables -I OUTPUT -d 159.153.95.65 -j logdrop
    iptables -I FORWARD -d 159.153.95.65 -j DROP

    • Like 2
  5. Yeah I got the same, my Cisco EPC3828D router only has parental blocking available so trying through there. Also contacted my ISP via email if I have any other chance to block that IP or URL (Don't trust that parental control)

    I'm still able to ping gosprodfeapp0474.ea.com so i guess my Buffalo router only blocks web page content from opening when url is blocked, probably not gonna do me anything good then

  6. ...And an update. The servers, like you suspected, were reversed. Human error of course, from the US side. Apparently they were very tired at the time of sending the message :)

    Anyways, the IP to block is indeed 159.153.95.65

    so dn for 159.153.95.65 is probably gosprodfeapp0474.ea.com ? My router has only URL blocking so im gonna have to try with what nslookup fetched for 159.153.95.65

  7. ...And an update. The servers, like you suspected, were reversed. Human error of course, from the US side. Apparently they were very tired at the time of sending the message :)

    Anyways, the IP to block is indeed 159.153.95.65

    so dn for 159.153.95.65 is probably gosprodfeapp0474.ea.com ? My router has only URL blocking so im gonna have to try with what nslookup fetched for 159.153.95.65

  8. ...And an update. The servers, like you suspected, were reversed. Human error of course, from the US side. Apparently they were very tired at the time of sending the message :)

    Anyways, the IP to block is indeed 159.153.95.65

    so dn for 159.153.95.65 is probably gosprodfeapp0474.ea.com ? My router has only URL blocking so i'm gonna have to try with what nslookup fetched for 159.153.95.65

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy