Results 1 to 4 of 4

Thread: IPSec wildcard

  1. #1
    You're god damn right Barry's Avatar
    Join Date
    Jul 2003
    Posts
    1,484
    Thanks
    70
    Thanked
    75 times in 59 posts
    • Barry's system
      • Motherboard:
      • Gigabyte Z270M-D3H
      • CPU:
      • Intel i7 7700
      • Memory:
      • 16GB (2x8GB) Avexir 2400
      • Storage:
      • Samsung 860 256GB SSD, Sandisk Ultra 3D 500GB, LG BR Writer
      • Graphics card(s):
      • Evga GeForce GTX Titan X 12GB
      • PSU:
      • Corsair RM750I
      • Case:
      • Fractal Design Focus G
      • Operating System:
      • Windows 10 Professional
      • Monitor(s):
      • 28" Acer UHD 4K2K
      • Internet:
      • Sky Fibre

    IPSec wildcard

    On my dedi games servers we use IPSec to block unwelcome visitors and it works well but only with non dynamic IP's and 90% of people have dynamic IP's these days, I've googled page after page about wildcard banning with IP and submask with very little results

    I'm guessing it's like if the IP range is 12.34.***.*** and submask is 12.255.255.255 that banning 12.34.0.0 and 12.255.255.255 would work


    Any ideas?
    Someone left a note on a piece of cake in the fridge that said, "Do not eat!". I ate the cake and left a note saying, "Yuck, who the hell eats paper ?

  2. #2
    You're god damn right Barry's Avatar
    Join Date
    Jul 2003
    Posts
    1,484
    Thanks
    70
    Thanked
    75 times in 59 posts
    • Barry's system
      • Motherboard:
      • Gigabyte Z270M-D3H
      • CPU:
      • Intel i7 7700
      • Memory:
      • 16GB (2x8GB) Avexir 2400
      • Storage:
      • Samsung 860 256GB SSD, Sandisk Ultra 3D 500GB, LG BR Writer
      • Graphics card(s):
      • Evga GeForce GTX Titan X 12GB
      • PSU:
      • Corsair RM750I
      • Case:
      • Fractal Design Focus G
      • Operating System:
      • Windows 10 Professional
      • Monitor(s):
      • 28" Acer UHD 4K2K
      • Internet:
      • Sky Fibre
    Noone?
    Someone left a note on a piece of cake in the fridge that said, "Do not eat!". I ate the cake and left a note saying, "Yuck, who the hell eats paper ?

  3. #3
    Senior Member RVF500's Avatar
    Join Date
    Apr 2004
    Location
    Back in Sunny UK...and it is sunny too :D...pleasant surprise.
    Posts
    1,063
    Thanks
    0
    Thanked
    0 times in 0 posts
    Just how are you using IPSec? IPSec is basically used for negotiating VPN tunnels. It encompasses phase 1 and 2 of IKE and also the security protocols and transform sets used in negotiating a secure tunnel. Not blocking access. So yeah, it would keep out unwelcome visitors because without the correct settings on a VPN client or IPSec capable device you can't access the tunnel. So only valid users can get to your server.

    Your subnet mask won't work as it's invalid. Masks are binary numbers, so 12 is not valid. In fact IP addresses are binary numbers but we use dotted decimal so we poor dumb humans can read them. And DNS servers so we don't have to remember loads of dotted decimal ddresses. The mask to identify a B class of addresses (I know 12 is an A class, but the breakdown here is a B class) is 255.255.0.0 unless your device uses reverse masks (also called wildcards). If you have a specific range of addresses I'd be happy to help out with the masking. But you can get subnet calculators online. They'll do the job for you in no time.

    Are you sure you mean IPSec and not IPS? What are you using to host the security. Is it on your server or do you have a dedicated router/firewall?
    "You want loyalty? ......get a dog!"

  4. #4
    Administrator Moby-Dick's Avatar
    Join Date
    Jul 2003
    Location
    There's no place like ::1 (IPv6 version)
    Posts
    10,665
    Thanks
    53
    Thanked
    384 times in 313 posts
    I think you've firmly grabbed the wrong end of the stick.

    You want to add a rule to a re firewall or soft5ware filter to only allow certain IP's to connect.
    However I'm not convinced its the way to get things to work

    If you wished to ban 12.34.0.0 to 12.34.255.255 then adding 12.34.0.0 with a subnet mask of 255.255.0.0 would work.

    You need to know exactly what ranges you would like to exclude or find another way to do it.
    my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •