which ip address for router?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mikk
    Senior Member
    • Jun 2008
    • 289

    #1

    which ip address for router?

    I'm trying to link two routers together wirelessly using dd-wrt on the client, while I can connect to the primary router I get no net access. My pc connected direct gets internet ok but is usually handed ip 192.168.1.72 (prefered) The primary router is 192.168.1.254 . There are four or five devices attached to the primary wirelessly. If I'm correct its an ip address issue but do I set my client router to 192.168.1.253 or down near 192.168.1.73. Currently I dont have full access to the primary router but nothing has worked so far. Any ideas?
  • Rawwen
    DK Veteran
    • May 2011
    • 328

    #2
    I would help You but I dont know whats the problem.
    Routers are connected by WLAN? They are in something like WDS?
    What's problem to addres routers ex. 192.168.1.1 and 192.168.1.2, use mask /24.
    Configure dhcp on R1 192.168.1.3 to 192.168.1.20
    Configure dhcp on R2 192.168.1.21 to 192.168.1.40
    Both mask /24 (255.255.255.0).
    Maybe I think about something else?

    Comment

    • smokin
      Senior Member
      • Jul 2009
      • 255

      #3
      This may work, but wireless rawwen..... didn't think you could do it this way....real question, why 2 routers? why not a use a expander/switcher box to increase ports?? Which is what I suspect is the reason here...
      Technomate-Dreambox-Spiderbox

      Comment

      • mikk
        Senior Member
        • Jun 2008
        • 289

        #4
        The routers are at different addresses, the signal I get from the primary is useable but marginal (dd-wrt will boost & repeat the signal). I had a similar set up working previously with (diffrent primary router) a more 'normal' 192.168.0.1 primary or server handing out x.0.2, x.0.3 etc. with my client router set at 0.4 The 0.254 is throwing me, and why would it give my pc 0.72 miles away from its own ip address?
        Last edited by mikk; 28 November, 2011, 09:34.

        Comment

        • Mjolinor
          V.I.P. VIC
          • Jan 2009
          • 1093

          #5
          Originally posted by mikk
          The routers are at different addresses, the signal I get from the primary is useable but marginal (dd-wrt will boost & repeat the signal). I had a similar set up working previously with (diffrent primary router) a more 'normal' 192.168.0.1 primary or server handing out x.0.2, x.0.3 etc. with my client router set at 0.4 The 0.254 is throwing me, and why would it give my pc 0.72 miles away from its own ip address?
          The IP is served from one or both of your routers. You need to make sure only one router is serving DHCP. The address it serves is dictated by the router and your settings in there, you define the pool of available addresses. Assuming your netmask is 255.255.255.0 then anywhere between 192.168.1.1 to 192.168.1.254 is valid and they will all work the same.

          You need to set up a WDS between the 2 routers to do what you need them to do. That is not trivial and there are a lot better explanations of how to do it on the Openwrt web pages than can be written here ina few minutes so go there and read.

          Comment

          • Mjolinor
            V.I.P. VIC
            • Jan 2009
            • 1093

            #6
            You may find it easier to use OLSR, WDS is now an old way of doing this but OLSR is more complex.

            Comment

            • mikk
              Senior Member
              • Jun 2008
              • 289

              #7
              Dhcp is turned off on the client router, I think wds doesnt allow wireless interface at the client ie. to use like an access point, that is why I chose dd-wrt wireless bridged repeater. I'll have another go and get back

              Comment

              • Mjolinor
                V.I.P. VIC
                • Jan 2009
                • 1093

                #8
                You can create virtual interfaces on one wireless card, one will be the hot spot, the other will be the WDS.

                Either way it is not an elegant solution and will give you problems even if it is all working OK.

                If you only have a client server wireless relationship then you have to set up a rake of static routes and use masquerading and that is a huge can of worms.

                Comment

                • mikk
                  Senior Member
                  • Jun 2008
                  • 289

                  #9
                  How about a wireless wifi extender, any good? I read a monkey could set one up. I've got my eye on a Belkin (the old b/g one) and a Buffalo, cheap.

                  Comment

                  Working...