daytrek vigor 2820n
in [Linux Networking]
|
From: Ernst Schmidtmann on 18 Jun 2010 19:36 Hello together, I have a problem with my router. It's a daytrek vigor 2820. I have two LAN networks with different IP's, 192.168.2.x and 192.168.1. x. The router has the ip 192.168.1.x and it is easy to connect with an 192.168.1.x ip. But it doesn't work with the 2.x address. I can not find a way to change the router to accept 192.168.x.x connections. I don't even know, what is causing this problem, since I read everywhere the router is accepting connections in this form. I would appreciate to hear the reason for this behavior and probably how I can change it. Best regards, Ernst
From: Denis McMahon on 18 Jun 2010 20:06 On 19/06/10 00:36, Ernst Schmidtmann wrote: > Hello together, > > I have a problem with my router. It's a daytrek vigor 2820. I have two > LAN networks with different IP's, 192.168.2.x and 192.168.1. x. > > The router has the ip 192.168.1.x and it is easy to connect with an > 192.168.1.x ip. But it doesn't work with the 2.x address. > > I can not find a way to change the router to accept 192.168.x.x > connections. I don't even know, what is causing this problem, since I > read everywhere the router is accepting connections in this form. > > I would appreciate to hear the reason for this behavior and probably how > I can change it. Change the netmask in the router to 255.255.252.0 And the router will then happily talk to anything with: 192.168.0.x 192.168.1.x 192.168.2.x 192.168.3.x Alternatively, if you want a smaller net, you can use netmask 255.255.252.0 for addresses of either 192.168.0.x and 192.168.1.x or 192.168.2.x and 192.168.3.x You can't, however, have a single net combining just x.x.1.x and x.x.2.x, it's to do with powers of 2 and the way netmasks work. Basically, looking at the bit patterns for 0 .. 3 ab 0 => 00 1 => 01 2 => 10 3 => 11 Note that changing from 1 to 2, both a and b bits change values. This means that a net that has x.x.1.x and x.x.2.x has to allow 0 and 1 values in both of those bit positions for the network bitmask, which means x.x.0.x and x.x.3.x are also valid addresses in that network. However, if we only allow the b bit to change, we can have either x.x.0.x and x.x.1.x, or we can have x.x.2.x and x.x.3.x, in fact depending on the rest of the address we can have any [n, +1] pairing where n is a multiple of 2 (including 0). Likewise, if we allow the 2 bits to change, we can have any net of [n, +1, +2, +3] that begins on an integer multiple of 4 (including 0). If we allow 3 bits to change, we can have any net of [n, +1, ... +7] that begins on an integer multiple of 8 (including 0). Get hold of ipcalc or sipcalc or an equivalent and you might understand. As an aside, it's considered good practice by some to put the router at either the first or last ip address in the allocated range, bearing in mind that all 0's (network address) and all 1's (broadcast address) are special addresses, so, for example: network address: 192.168.0.0/23 netmask: 255.255.254.0 router: 192.168.0.1 or: 192.168.1.254 broadcast address: 192.168.1.255 network address: 192.168.2.0/23 netmask: 255.255.254.0 router: 192.168.2.1 or: 192.168.3.254 broadcast address: 192.168.3.255 network address: 192.168.0.0/22 netmask: 255.255.252.0 router: 192.168.0.1 or: 192.168.3.254 broadcast address: 192.168.3.255 Rgds Denis McMahon
From: terryc on 18 Jun 2010 20:13 On Sat, 19 Jun 2010 01:36:24 +0200, Ernst Schmidtmann wrote: > Hello together, > > I have a problem with my router. It's a daytrek vigor 2820. I have two > LAN networks with different IP's, 192.168.2.x and 192.168.1. x. > > The router has the ip 192.168.1.x and it is easy to connect with an > 192.168.1.x ip. But it doesn't work with the 2.x address. > > I can not find a way to change the router to accept 192.168.x.x > connections. Change netmask to 255.255.0.0 will cover that.
|
Pages: 1 Prev: non-unicast packets on Wan interface (cable modem) Next: Degraded network (protocol problems?) |