Join us now. It is free, and it takes less than 1 minute to register.
Register now
Subscribe to our daily newsletter. It is free, and it comes with many benefits.


+ Reply to Thread
Page 32 of 45 FirstFirst ... 2228293031323334353642 ... LastLast
Results 466 to 480 of 674

Thread: RouteSentry: Manage 2 ADSL account connections on 1 pc, 1 line, 1 modem (local/intnl)

  1. #466
    Super Grandmaster
    Join Date
    Feb 2009
    Location
    Stellenbosch
    Posts
    8,152
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default

    SlyFly, I haven't tested Windows 7 RC yet, but I suppose WinRoute will work like in Vista where you have to set your Router into half-bridge mode, let your Router dial your International (combined int & local) account with a PPPoE connection and then add a PPPoE connection on your PC that dials to your Local account.

    If you don't manage with RouteSentry, you can always try using persistent routes setup initially by a batch file - see http://www.aalwyne.co.za/local_IP_range.shtml
    Note: in this case you also require to setup the Router in half-bridge mode, although you HAVE TO let your Router dial the LOCAL account with this method! Just use a PPPoE connection and leave the RASPPPoE stuff. If it doesn't seem to work correctly, try selecting the "Use default gateway on remote network" option under the PPPoE connection's TCP/IP v4 properties on your PC.

    I'll try to test RouteSentry with Windows 7 beta on 1st of May when my friend has international cap again

  2. #467
    Grandmaster stroebs's Avatar
    Join Date
    Jan 2009
    Location
    Newlands
    Posts
    2,002
    Blog Entries
    1
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)

    Default

    I'm a little confused... I don't exactly know how to set my router into half-bridged mode or set my router into bridged mode completely either! I try dial a connection from within win7 and it says it can't dial cos the router gave it an error...

    Can someone possibly help me set it up at all? I have a Surecom 9410SX-g ADSL2+ Router
    These are the options that I have to choose from: Here
    Last edited by stroebs; 30-04-2009 at 06:25 PM.
    I make regular use of my indicators

  3. #468
    Super Grandmaster APoc184's Avatar
    Join Date
    Sep 2008
    Location
    Tshwanetoria
    Posts
    20,027
    Mentioned
    6 Post(s)
    Tagged
    0 Thread(s)

    Default

    I noticed that www.nationalgeographic.com does not get routed through local.

    Can somebody please give me the range to enter into masktool so that I can add it to the localroutes file. Or post the lines to enter into the file.

    Thanks.

    Can I maybe suggest that someone upload an updated localroutes file or content.
    So if you have edited and added numerous IP's in localroutes, please post the details here or PM the list.
    Be the person you needed when you were younger.

  4. #469
    Super Grandmaster
    Join Date
    Feb 2009
    Location
    Stellenbosch
    Posts
    8,152
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default

    APoC84, my localroutes contains an IP range that includes www.nationalgeographic.com: 165.165.0.0 or 165.165.0.0/16
    Please note that they have numerous adds & other content hosted on other international sites though, like ngcache.travelscream.com, fls.doubleclick.net, www.google-analytics.com & ngeo.netmng.com are international sites and edge.quantserve.com is hosted locally on akamai servers. You can always try to block these sites by adding their domain names into the %windir%\system32\drivers\etc\hosts file or something like that.

    If you want an updated list you can use hyperterminal to connect to public-route-server.is.co.za and then type in show ip bgp. It will give you a list of all the network addresses with their netmasks (in CIDR format) (and unfortunately lots of data that you won't need). Or you can always goto http://www.aalwyne.co.za/local_IP_range.shtml and use his list of local addresses that gets updated every now and then.

  5. #470
    Grandmaster stroebs's Avatar
    Join Date
    Jan 2009
    Location
    Newlands
    Posts
    2,002
    Blog Entries
    1
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)

    Default RouteSentry setup Guide Win7/Vista.

    This guide is outdated.Try Pada's new routing app

    The following is a comprehensive setup guide for RouteSentry in Windows 7 or Windows Vista.

    You will need the following:
    -A computer running Windows 7 or Windows Vista.
    -TWO ADSL internet accounts (One with International bandwidth and one with local bandwidth)
    -An ADSL router.

    STEP 1: Put your router in Bridged mode if it is not already in bridged mode.

    STEP 2: Create yout two PPPoE connections by going into Network and Sharing Center and clicking "Set up a new connection on a network".

    *NB: You have to set up two connections: One Local and one international

    STEP 3: Download this registry file to your computer and run (merge) the registry file.

    STEP 4: Restart your computer.

    STEP 5: Go to Network and Sharing Center > Change adapter settings (on the left-hand pane) > Right click on LOCAL connection > Properties > Networking tab > Internet Protocol Version 4 > Advanced > UNTICK "Use default gateway on remote network > Click the "OK" box three times.

    *NB: ONLY do this for LOCAL connection!

    STEP 6: Go to Network and Sharing Center > Change adapter settings (on the left-hand pane) > Go to each network connection and UNTICK TCP/IP Protocol V6

    STEP 7: BEFORE you open RouteSentry, download/view the text file HERE and copy everything in the file into "C:\Program Files\Route Sentry\localroutes.dat" (Open localroutes.dat with notepad or any other text editor)

    STEP 8: Open RouteSentry as Administrator > Choose your international and local connections > connect both.

    STEP 9: Go to this international link and this local link to get your local and international IP addresses. If they are the same, it is not working.

    If the routing is not working, disconnect your local connection and connect it again. It should be working now. Repeat step 9 to check.

    If RouteSentry still refuses to work, Disconnect all connections and Download this file and run it. Follow the instructions.

    If you are having problems, send me or Pada a PM.

    __________________________________________________ _______________
    Having Problems?

    Local networking not working? (IE: Can't connect to computers on your network)
    Quote Originally Posted by Pada
    Run the following command, specified within the quotation marks, with Administrative privileges (or with UAC disabled) when your private IP address range is:
    10.0.0.*: "route add 10.0.0.0 mask 255.255.255.0 %IP% metric 1 -p"
    192.168.1.*: "route add 192.168.1.0 mask 255.255.255.0 %IP% metric 1 -p"
    NB: Replace %IP% in the commands above with your PC's IP address before running the command. The IP address must be within the private IP range.
    RouteSentry not working?
    Code:
    Disconnect your local connection and reconnect it again.
    Code:
    Download the updated local routes as in step 7.
    Code:
    Run RouteSentry as Administrator
    __________________________________________________ _____________________________________
    STILL CONFUSED???

    Try Pada's new routing app
    Last edited by stroebs; 19-10-2010 at 07:42 PM. Reason: Update 21/11/2009 - Added Pada's new app
    I make regular use of my indicators

  6. #471
    Super Grandmaster
    Join Date
    Feb 2009
    Location
    Stellenbosch
    Posts
    8,152
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Exclamation Faulty subnet masks with RouteSentry 1.01

    I've discovered that many route table entries in the localroutes.dat file that RouteSentry uses has incorrect subnet masks (255.255.255.0 instead of 255.255.0.0). Kalevra also noticed this:
    Quote Originally Posted by partly quoted kalevra View Post
    Just a heads up I just added some new addresses to my localroutes.dat, I found a few 165.146.x.x addresses that weren't routed locally.
    The wrong subnet masks are also in the batchfiles found at http://www.aalwyne.co.za/local_IP_range.shtml, although the script that does the routing for the WRT54G series routers (http://mybroadband.co.za/vb/showpost...&postcount=799) doesn't have this flaw!

    I reckon they got their routing table from querying "show ip bgp" from the public-route-server.is.co.za. It returns all the local network destinations with their CIDR values in most cases. In the cases where the CIDR value is left out, (AntiBody & Aalwyne) assumed the default being 24! Instead the default is 16 (meaning subnet mask of 255.255.0.0 and NOT 255.255.255.0).

    I have no idea where to get an updated & corrected version of the localroutes.dat, unless you open a telnet/hyperterminal session to public-route-server.is.co.za and query: "show ip bgp".

    If I get some time off during the week/today I might be able to code an application to update that localroutes.dat file from the public-route-server.is.co.za

  7. #472
    Senior Member
    Join Date
    Mar 2004
    Location
    The Willows, Pretoria
    Posts
    231
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default Faulty subnet masks

    But if the CIDR is left out, can you assume the default to be 16? Shouldn't you look at the class of the IP address to determine what the correct mask should be? At one stage I also assumed /16, recently changed it ...

    Here is my python script, if it will help, to get routes from local-route-server.is.co.za. It formats the output for use with iproute, change if you want it in a different format. Also, it uses the netaddr library (should be a newish version) to make the resulting list more compact (it usually about halves the number of routes)
    Code:
    #! /usr/bin/python
    
    import telnetlib
    import re
    import netaddr
    
    def telnet(host, prompt):
        session = telnetlib.Telnet(host)
        session.read_until(prompt, 5)        # Wait for prompt
        session.write('terminal length 0\n')
        session.read_until(prompt, 5)        # Wait for prompt
        session.write('show ip bgp\n')
        return session.read_until(prompt)    # Return all results until prompt
    
    host = 'local-route-server.is.co.za'
    prompt  = 'local-route-server>'
    bgp_routes = telnet(host, prompt)
    
    nets = []
    
    # Regular expression to split subnet of the form xxx.xxx.xxx.xxx/xxx
    r = re.compile('[./]')
    
    for line in bgp_routes.split('\r\n'):
        # The lines we are looking for looks something like this:
        #     *> 216.5.192.0/21   168.209.255.8            0 3741 2905 i
        # We are interested in the second column ...
        if line.startswith('*'):
            subnet = line.split()[1]
            # Split address into quads for easier testing ...
            q = r.split(subnet)
            if len(q) < 5:
                # IP address is missing the subnet mask, so determine the mask
                # from the class of the IP address ...
                if int(q[0]) < 128:
                    # Leading bit 0xx, so class A ...
                    subnet += '/8'
                elif int(q[0]) < 192:
                    # Leading bits 10x, so class B ...
                    subnet += '/16'
                else:
                    # Only class C left ...
                    subnet += '/24'
            # Now we have a properly formatted CIDR address block, add it to 
            # our list of nets ...
            nets.append(netaddr.CIDR(subnet))
    
    # Summarize nets, i.e. remove subnets and join adjacent ones ...
    compacted_nets = netaddr.CIDR.summarize(nets)
    
    for net in compacted_nets:
        print net
    In the resulting net list, the 165.146.x.x range would be caught by the 165.144.0.0/14 subnet, as one can see by using netaddr ...

    Code:
    >>> from netaddr import *
    >>> ip=CIDR('165.144.0.0/14')
    >>> ip.iprange()
    IPRange('165.144.0.0', '165.147.255.255')
    >>>

  8. #473
    Super Grandmaster
    Join Date
    Feb 2009
    Location
    Stellenbosch
    Posts
    8,152
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default

    cenuij, you are correct. There are also some cases in that list that has no CIDR specified and then a subnet mask of 255.255.255.0 should be used. So looking at the class you should be able to distinguish between CIDR 16 & 24. I was unable to see any route entries with other CIDR values, but if you can prove that with your script I would be grateful!
    To get a list of all the routes without a specified CIDR value, you can use:
    Code:
    show ip bgp | include ^...([0-9]+[.])+[0-9]+_
    If you are uncertain about the subnet mask, then you can always do a seperate request for those IP addresses again: "show ip bgp <IP> | include BGP". eg.
    Code:
    local-route-server>show ip bgp 165.144.0.0 | include BGP
    BGP routing table entry for 165.144.0.0/16, version 53903044
    local-route-server>show ip bgp 146.232.0.0 | include BGP
    BGP routing table entry for 146.232.0.0/16, version 53902950
    local-route-server>show ip bgp 165.165.0.0 | include BGP
    BGP routing table entry for 165.165.0.0/16, version 53903055
    local-route-server>show ip bgp 192.96.46.0 | include BGP
    BGP routing table entry for 192.96.46.0/24, version 53955399
    Note: The above section indicates that 165.144.0.0 should use CIDR 16 & NOT 14!
    Last edited by Pada; 03-05-2009 at 05:38 PM.

  9. #474
    Member
    Join Date
    Aug 2006
    Posts
    12
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default Thanks stroebs

    Hey stroebs,

    I followed your instructions and my routesentry is now working in windows 7! Thanks a lot man, appreciate it.

  10. #475
    Senior Member
    Join Date
    Mar 2004
    Location
    The Willows, Pretoria
    Posts
    231
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default

    Ah cool, thanks, didn't know about the "include BGP" thing.

    So I have modified the script so it prints out all the nets without masks (first column), the mask as (re)queried from the server in the second column, and then in the third column the mask as I calculate it (using the IP class) .

    Here is the script:
    Code:
    #! /usr/bin/python
    
    import telnetlib
    import re
    
    host = 'local-route-server.is.co.za'
    prompt  = 'local-route-server>'
    
    session = telnetlib.Telnet(host)
    session.read_until(prompt, 5)        # Wait for prompt
    session.write('terminal length 0\n')
    session.read_until(prompt, 5)        # Wait for prompt
    session.write('show ip bgp\n')
    bgp_routes = session.read_until(prompt)    # Return all results until prompt
    nets = []
    
    r = re.compile('[./]')
    
    for line in bgp_routes.split('\r\n'):
        # The lines we are looking for looks something like this:
        #     *> 216.5.192.0/21   168.209.255.8            0 3741 2905 i
        # We are interested in the second column ...
        if line.startswith('*'):
            subnet = line.split()[1]
            # Split address into quads for easier testing ...
            q = r.split(subnet)
            if len(q) < 5:
                # IP address is missing the subnet mask, so determine the mask
                # from the class of the IP address ...
    	    original = subnet
    	    if int(q[0]) < 128:
                    # Leading bit 0xx, so class A ...
                    subnet += '/8'
                elif int(q[0]) < 192:
                    # Leading bits 10x, so class B ...
                    subnet += '/16'
                else:
                    # Only class C left ...
                    subnet += '/24'
    
                # Also try to get the subnet mask from the server, to verify ...
    		
    	    session.write('show ip bgp %s | include BGP\n' % original)
    	    response = session.read_until(prompt).split('\r\n')[1]
    	    ip_with_bgp = response.split()[5].strip(',')
    	    print "%s : %s %s" % (original, ip_with_bgp, subnet),
    	    if ip_with_bgp != subnet:
    	    	print "<--------------------"
                else:
    	    	print ""
    And the results (shortened, there were 666 nets without masks):

    Code:
    137.158.0.0	137.158.0.0/17	137.158.0.0/16	<--------------------
    137.215.0.0	137.215.0.0/16	137.215.0.0/16	
    139.53.0.0	139.53.0.0/16	139.53.0.0/16	
    143.128.0.0	143.128.0.0/16	143.128.0.0/16	
    143.160.0.0	143.160.0.0/24	143.160.0.0/16	<--------------------
    146.64.0.0	146.64.0.0/16	146.64.0.0/16	
    146.141.0.0	146.141.0.0/16	146.141.0.0/16	
    146.182.0.0	146.182.0.0/16	146.182.0.0/16	
    146.230.0.0	146.230.0.0/16	146.230.0.0/16	
    146.231.0.0	146.231.0.0/16	146.231.0.0/16	
    146.232.0.0	146.232.0.0/16	146.232.0.0/16	
    147.110.0.0	147.110.0.0/16	147.110.0.0/16	
    152.106.0.0	152.106.0.0/16	152.106.0.0/16	
    152.107.0.0	152.107.0.0/16	152.107.0.0/16	
    152.108.0.0	152.108.0.0/16	152.108.0.0/16	
    152.110.0.0	152.110.0.0/16	152.110.0.0/16	
    152.111.0.0	152.111.0.0/16	152.111.0.0/16	
    152.112.0.0	152.112.0.0/16	152.112.0.0/16	
    155.159.0.0	155.159.0.0/16	155.159.0.0/16	
    155.234.0.0	155.234.0.0/16	155.234.0.0/16	
    155.235.0.0	155.235.0.0/16	155.235.0.0/16	
    155.237.0.0	155.237.0.0/16	155.237.0.0/16	
    155.238.0.0	155.238.0.0/16	155.238.0.0/16	
    155.239.0.0	155.239.0.0/16	155.239.0.0/16	
    155.240.0.0	155.240.0.0/16	155.240.0.0/16	
    156.8.0.0	156.8.0.0/16	156.8.0.0/16	
    160.123.0.0	160.123.0.0/16	160.123.0.0/16	
    160.124.0.0	160.124.0.0/16	160.124.0.0/16	
    163.195.0.0	163.195.0.0/17	163.195.0.0/16	<--------------------
    163.196.0.0	163.196.0.0/16	163.196.0.0/16	
    163.197.0.0	163.197.0.0/16	163.197.0.0/16	
    163.200.0.0	163.200.0.0/16	163.200.0.0/16	
    163.201.0.0	163.201.0.0/16	163.201.0.0/16	
    164.88.0.0	164.88.0.0/16	164.88.0.0/16	
    164.155.0.0	164.155.0.0/16	164.155.0.0/16	
    165.4.0.0	165.4.0.0/16	165.4.0.0/16	
    165.8.0.0	165.8.0.0/16	165.8.0.0/16	
    165.9.0.0	165.9.0.0/16	165.9.0.0/16	
    165.25.0.0	165.25.0.0/16	165.25.0.0/16	
    165.143.0.0	165.143.0.0/16	165.143.0.0/16	
    165.144.0.0	165.144.0.0/16	165.144.0.0/16	
    165.145.0.0	165.145.0.0/16	165.145.0.0/16	
    165.146.0.0	165.146.0.0/16	165.146.0.0/16	
    165.147.0.0	165.147.0.0/16	165.147.0.0/16	
    165.148.0.0	165.148.0.0/16	165.148.0.0/16
    .
    .
    .	
    196.208.0.0	196.208.0.0/24	196.208.0.0/24	
    196.209.251.0	196.209.251.0/24	196.209.251.0/24	
    196.216.56.0	196.216.56.0/24	196.216.56.0/24	
    196.220.32.0	196.220.32.0/24	196.220.32.0/24	
    196.220.33.0	196.220.33.0/24	196.220.33.0/24	
    196.220.34.0	196.220.34.0/24	196.220.34.0/24	
    196.220.35.0	196.220.35.0/24	196.220.35.0/24	
    196.220.36.0	196.220.36.0/24	196.220.36.0/24	
    196.220.37.0	196.220.37.0/24	196.220.37.0/24	
    196.220.38.0	196.220.38.0/24	196.220.38.0/24	
    196.220.39.0	196.220.39.0/24	196.220.39.0/24	
    196.220.56.0	196.220.56.0/24	196.220.56.0/24	
    196.220.57.0	196.220.57.0/24	196.220.57.0/24	
    196.220.58.0	196.220.58.0/24	196.220.58.0/24	
    196.220.59.0	196.220.59.0/24	196.220.59.0/24	
    196.220.60.0	196.220.60.0/24	196.220.60.0/24	
    196.220.61.0	196.220.61.0/24	196.220.61.0/24	
    196.220.62.0	196.220.62.0/24	196.220.62.0/24	
    196.220.63.0	196.220.63.0/24	196.220.63.0/24	
    198.54.7.0	198.54.7.0/24	198.54.7.0/24	
    198.54.42.0	198.54.42.0/24	198.54.42.0/24	
    198.54.58.0	198.54.58.0/24	198.54.58.0/24	
    198.54.64.0	198.54.64.0/24	198.54.64.0/24	
    198.54.65.0	198.54.65.0/24	198.54.65.0/24	
    198.54.66.0	198.54.66.0/24	198.54.66.0/24	
    198.54.71.0	198.54.71.0/24	198.54.71.0/24	
    198.54.80.0	198.54.80.0/24	198.54.80.0/24	
    198.54.82.0	198.54.82.0/24	198.54.82.0/24	
    198.54.83.0	198.54.83.0/24	198.54.83.0/24	
    198.54.84.0	198.54.84.0/24	198.54.84.0/24	
    198.54.91.0	198.54.91.0/24	198.54.91.0/24	
    198.54.92.0	198.54.92.0/24	198.54.92.0/24	
    198.54.148.0	198.54.148.0/24	198.54.148.0/24	
    198.54.149.0	198.54.149.0/24	198.54.149.0/24	
    198.54.154.0	198.54.154.0/24	198.54.154.0/24	
    198.54.163.0	198.54.163.0/24	198.54.163.0/24	
    198.54.165.0	198.54.165.0/24	198.54.165.0/24	
    198.54.170.0	198.54.170.0/24	198.54.170.0/24	
    198.54.173.0	198.54.173.0/24	198.54.173.0/24	
    198.54.174.0	198.54.174.0/24	198.54.174.0/24	
    198.54.196.0	198.54.196.0/24	198.54.196.0/24	
    198.54.202.0	198.54.202.0/24	198.54.202.0/24	
    198.54.204.0	198.54.204.0/24	198.54.204.0/24	
    198.54.205.0	198.54.205.0/24	198.54.205.0/24	
    198.54.206.0	198.54.206.0/24	198.54.206.0/24	
    198.54.208.0	198.54.208.0/24	198.54.208.0/24	
    198.54.219.0	198.54.219.0/24	198.54.219.0/24	
    198.54.222.0	198.54.222.0/24	198.54.222.0/24	
    198.54.223.0	198.54.223.0/24	198.54.223.0/24	
    198.54.225.0	198.54.225.0/24	198.54.225.0/24	
    198.54.228.0	198.54.228.0/24	198.54.228.0/24	
    198.54.229.0	198.54.229.0/24	198.54.229.0/24	
    198.54.248.0	198.54.248.0/24	198.54.248.0/24	
    198.54.253.0	198.54.253.0/24	198.54.253.0/24	
    199.7.66.0	199.7.66.0/24	199.7.66.0/24	
    199.7.68.0	199.7.68.0/24	199.7.68.0/24	
    199.7.77.0	199.7.77.0/24	199.7.77.0/24	
    202.85.244.0	202.85.244.0/24	202.85.244.0/24	
    202.133.108.0	202.133.108.0/24	202.133.108.0/24	
    202.157.187.0	202.157.187.0/24	202.157.187.0/24	
    203.26.78.0	203.26.78.0/24	203.26.78.0/24	
    203.56.62.0	203.56.62.0/24	203.56.62.0/24	
    203.142.6.0	203.142.6.0/24	203.142.6.0/24	
    203.149.208.0	203.149.208.0/24	203.149.208.0/24	
    204.61.210.0	204.61.210.0/24	204.61.210.0/24	
    204.69.234.0	204.69.234.0/24	204.69.234.0/24	
    204.74.108.0	204.74.108.0/24	204.74.108.0/24	
    204.74.112.0	204.74.112.0/24	204.74.112.0/24	
    204.74.114.0	204.74.114.0/24	204.74.114.0/24	
    206.223.136.0	206.223.136.0/24	206.223.136.0/24	
    207.179.7.0	207.179.7.0/24	207.179.7.0/24	
    209.88.20.0	209.88.20.0/24	209.88.20.0/24	
    209.88.21.0	209.88.21.0/24	209.88.21.0/24	
    209.88.114.0	209.88.114.0/24	209.88.114.0/24	
    209.203.1.0	209.203.1.0/24	209.203.1.0/24	
    209.203.2.0	209.203.2.0/24	209.203.2.0/24	
    209.203.4.0	209.203.4.0/24	209.203.4.0/24	
    209.203.6.0	209.203.6.0/24	209.203.6.0/24	
    209.203.15.0	209.203.15.0/24	209.203.15.0/24	
    209.203.20.0	209.203.20.0/24	209.203.20.0/24	
    209.203.22.0	209.203.22.0/24	209.203.22.0/24	
    209.203.25.0	209.203.25.0/24	209.203.25.0/24	
    209.203.26.0	209.203.26.0/24	209.203.26.0/24	
    209.203.28.0	209.203.28.0/24	209.203.28.0/24	
    209.203.30.0	209.203.30.0/24	209.203.30.0/24	
    209.203.33.0	209.203.33.0/24	209.203.33.0/24	
    209.203.39.0	209.203.39.0/24	209.203.39.0/24	
    209.203.55.0	209.203.55.0/24	209.203.55.0/24	
    209.203.58.0	209.203.58.0/24	209.203.58.0/24	
    209.203.59.0	209.203.59.0/24	209.203.59.0/24	
    209.203.62.0	209.203.62.0/24	209.203.62.0/24	
    212.85.218.0	212.85.218.0/24	212.85.218.0/24	
    216.0.48.0	216.0.48.0/24	216.0.48.0/24	
    216.0.50.0	216.0.50.0/24	216.0.50.0/24	
    221.133.37.0	221.133.37.0/24	221.133.37.0/24	
    221.133.43.0	221.133.43.0/24	221.133.43.0/24
    Hmm, so 3 of them don't agree ... weird ... ?

    Also, the '165.144.0.0/14' is merely the result of the 'summarize' function; '165.144.0.0/14' is equivalent to 165.144.0.0/16' + '165.145.0.0/16' + '165.146.0.0/16' + '165.147.0.0/16' as retrieved from the server

  11. #476
    Super Grandmaster
    Join Date
    Feb 2009
    Location
    Stellenbosch
    Posts
    8,152
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Talking C# 2008 app to update RouteSentry routes

    I've now coded an application in Visual C# Express 2008 that outputs an updated localroutes.dat that is used by RouteSentry by querying public-route-server.is.co.za:23. To update it will roughly generate 400kB network traffic.

    The app also outputs a 2 batch-files that can be used to route all the local traffic through a specified gateway & remove the route entries too. I got that idea from http://www.aalwyne.co.za/local_IP_range.shtml
    The enable_local.bat will add persistent route table entries (meaning that they will stay there even after a restart). The disable_local.bat will remove those entries.

    The 19kB zipfile can be downloaded from:
    My source can be found at http://www.quickshare.co.za/files/yq...rogram.cs.html

    I don't know the .Net environment that well, so I think you will need .Net Framework 3 to run my 32bit app. Also I'm not sure if it will run on x64 OS.
    Last edited by Pada; 04-05-2009 at 02:38 AM. Reason: new version

  12. #477
    Senior Member
    Join Date
    Mar 2004
    Location
    The Willows, Pretoria
    Posts
    231
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default

    Quote Originally Posted by cenuij View Post
    Code:
    137.158.0.0	137.158.0.0/17	137.158.0.0/16	<--------------------
    .
    .
    .
    143.160.0.0	143.160.0.0/24	143.160.0.0/16	<--------------------
    .
    .
    .
    163.195.0.0	163.195.0.0/17	163.195.0.0/16	<--------------------
    Hmm, so 3 of them don't agree ... weird ... ?
    I think I understand now why those entries don't agree with one another; in the telnet session, if you look for 137.158.0.0 you find two subnets for it, one with a mask of /17, and the other with no mask:
    Code:
    local-route-server>show ip bgp | include ^...137.158.0.0*
    *> 137.158.0.0/17   168.209.255.8                          0 3741 6149 36982 i
    *> 137.158.0.0      168.209.255.8                          0 3741 2905 22355 22355 36982 36982 36982 36982 i
    local-route-server>
    So, if you do the "local-route-server>show ip bgp 137.158.0.0 | include BGP" command, which one of those two subnets will it display? Seems like the first one ...
    Code:
    local-route-server>show ip bgp 137.158.0.0 | include BGP                   
    BGP routing table entry for 137.158.0.0/17, version 56521272
    local-route-server>
    ... even though both nets are there, which you can verify:

    Code:
    local-route-server>show ip bgp 137.158.0.0/17 | include BGP
    BGP routing table entry for 137.158.0.0/17, version 56522763
    local-route-server>show ip bgp 137.158.0.0/16 | include BGP
    BGP routing table entry for 137.158.0.0/16, version 56522764
    local-route-server>
    And just to show that the 137.158.0.0/16 is the valid one and not 137.158.0.0/24, we can check:

    Code:
    local-route-server>show ip bgp 137.158.0.0/24 | include BGP
    local-route-server>
    The above also applies to the other two anomalies:
    Code:
    local-route-server>show ip bgp | include ^...143.160.0.0*
    *> 143.160.0.0/24   168.209.255.8                          0 3741 6149 8094 i
    *> 143.160.0.0      168.209.255.8                          0 3741 5713 2018 i
    local-route-server>show ip bgp 143.160.0.0 | include BGP   
    BGP routing table entry for 143.160.0.0/24, version 56537690
    local-route-server>show ip bgp 143.160.0.0/24 | include BGP
    BGP routing table entry for 143.160.0.0/24, version 56537690
    local-route-server>show ip bgp 143.160.0.0/16 | include BGP
    BGP routing table entry for 143.160.0.0/16, version 56537691
    local-route-server>show ip bgp | include ^...163.195.0.0*
    *  163.195.0.0/17   168.209.255.8                          0 3741 ?
    *  163.195.0.0      168.209.255.8                          0 3741 i
    local-route-server>
    local-route-server>show ip bgp 163.195.0.0 | include BGP   
    BGP routing table entry for 163.195.0.0/17, version 56539328
    local-route-server>show ip bgp 163.195.0.0/17 | include BGP
    BGP routing table entry for 163.195.0.0/17, version 56539328
    local-route-server>show ip bgp 163.195.0.0/16 | include BGP
    BGP routing table entry for 163.195.0.0/16, version 56539329
    local-route-server>
    From which I can probably say that using "show ip bgp 163.195.0.0 | include BGP" to determine the missing subnet mask is not quite right; you should use the class of the ip to determine the mask (/16 in this case, since it is a class B ip) and maybe just use "show ip bgp 163.195.0.0/16 | include BGP" just to verify?

    does this make sense?

  13. #478
    Super Grandmaster
    Join Date
    Feb 2009
    Location
    Stellenbosch
    Posts
    8,152
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Post C# 2008 app to update & reduce RouteSentry routes

    Well done. This means that your first python script was correct the first time round.
    cenuij, thanks so much for all your help.

    * Microsoft C# 2008 Express console app to update & reduce RouteSentry localroutes *
    Downloads for my latest version 0.7:
    To use:
    Download the binaries zip-file & extract it to a temporary folder. Read the ReadMe file for more info.
    You can replace the old (Nov 2008) RouteSentry localroutes.dat file with the new (5 May 2009) one from the zip-file.
    Or if you don't want to use RouteSentry, and prefer to use batchfiles to setup persistent routes, see http://www.aalwyne.co.za/local_IP_range.shtml on how to use those 2 batchfiles

    If you want the absolute latest version of local routes, given by the public-route-server.is.co.za (TCP port 23), launch the application, read the prompts and then it will update all the extracted files (except for the readme & the app ofcourse). The app will generate approx. 150kB's local internet traffic.

    In my latest version I've removed all the duplicate route table entries & removed all overlapping entries, however I haven't merged any route table entries yet. This latest version outputs much smaller files & also transfers much smaller internet data since it calculates the missing CIDR values according to the leading byte (like cenuij's python script).

    I would appreciate it if someone can double-check all the routes that I've removed :P
    Like my app reduced:
    Code:
    *  41.0.0.0/16      168.209.255.8                          0 3741 5713 36994 i
    *  41.0.5.0/24      168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.6.0/24      168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.8.0/24      168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.13.0/24     168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.24.0/24     168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.30.0/24     168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.48.0/20     168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.128.0/20    168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.156.0/24    168.209.255.8                          0 3741 5713 36994 ?
    *  41.0.157.0/24    168.209.255.8                          0 3741 5713 36994 i
    *  41.0.196.0/24    168.209.255.8                          0 3741 5713 36994 i
    *  41.0.236.0/24    168.209.255.8                          0 3741 5713 36994 i
    *  41.0.248.0/24    168.209.255.8                          0 3741 5713 36994 i
    .
    .
    *  165.148.0.0      168.209.255.8                          0 3741 5713 i
    *  165.148.30.0/24  168.209.255.8                          0 3741 5713 5734 ?
    *  165.148.128.0/17 168.209.255.8                          0 3741 5713 5734 ?
    *  165.148.248.0/23 168.209.255.8                          0 3741 5713 i
    *  165.148.248.0/22 168.209.255.8                          0 3741 5713 i
    *  165.148.252.0/22 168.209.255.8                          0 3741 5713 i
    to
    Code:
    41.0.0.0/16
    165.148.0.0/16
    Last edited by Pada; 06-05-2009 at 08:52 PM. Reason: Changed hosting

  14. #479
    Senior Member Lord-Flame13's Avatar
    Join Date
    Mar 2009
    Posts
    189
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default

    Awesome, thanks guys (esspically stroebs) im going to install win7 this weekend and routesentry is a major requirment.

  15. #480
    Grandmaster stroebs's Avatar
    Join Date
    Jan 2009
    Location
    Newlands
    Posts
    2,002
    Blog Entries
    1
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)

    Default

    Only glad to help peeps
    I make regular use of my indicators

+ Reply to Thread
Page 32 of 45 FirstFirst ... 2228293031323334353642 ... LastLast

Bookmarks

Bookmarks

Posting Permissions

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