Another chance for me to display my ignorance :-) All that follows is based on SuSE 7.0. I am changing our ip address range from 172.19.50.x (255.255.255.0) to 172.16.y.x (255.255.252.0) - reason - more numbers. However, while moving over I need to let machines on both ranges communicate eg. clients printing to print servers etc. Is this possible? If I set up 2 interfaces on the server (derby) with ifconfig eth0:0 172.19.50.2 netmask 255.255.255.0 ifconfig eth0:1 172.16.0.2 netmask 255.255.252.0 and turn ip forwarding on with yast, should machines on the 2 ip ranges be able to communicate. eg. ping each other I've tried it and they don't. Am I trying something silly and if not what other steps do I need? Dave Williams
On Mon, 29 Jan 2001, Dave Williams wrote:
All that follows is based on SuSE 7.0. I am changing our ip address range from 172.19.50.x (255.255.255.0) to 172.16.y.x (255.255.252.0) - reason - more numbers. However, while moving over I need to let machines on both ranges communicate eg. clients printing to print servers etc.
Is this possible?
Presumably, yes. But why can't you keep using 172.19.50.x, but with a subnet mask of 255.255.252.0? This will allow you to have 172.19.48.0 -> 172.19.51.255 And it'll be easier for you as all you'd have to change is the subnet mask on the machines.
If I set up 2 interfaces on the server (derby) with
ifconfig eth0:0 172.19.50.2 netmask 255.255.255.0 ifconfig eth0:1 172.16.0.2 netmask 255.255.252.0
and turn ip forwarding on with yast, should machines on the 2 ip ranges be able to communicate. eg. ping each other
I've tried it and they don't.
What does "route -n" give? And then I'd presume you'd have to set up the clients to say that if the need to access 172.19.50.0/255.255.255.0, they should route to 172.19.50.2, otherwise go to your default gateway (whatever that may be; usually an Internet gateway).
Am I trying something silly and if not what other steps do I need?
How about "route add 172.16.0.2 netmask 255.255.252.0 dev eth0:1". Or something similar? Dan -- dankolb@ox.compsoc.net Oxford University Computer Society Secretary --I reserve the right to be completely wrong about any comments or opinions expressed; don't trust everything you read above--
Dan Thanks for your help On 29 Jan, Dan Kolb <dankolb@ox.compsoc.net> wrote:
On Mon, 29 Jan 2001, Dave Williams wrote:
All that follows is based on SuSE 7.0. I am changing our ip address range from 172.19.50.x (255.255.255.0) to 172.16.y.x (255.255.252.0) - reason - more numbers. However, while moving over I need to let machines on both ranges communicate eg. clients printing to print servers etc.
Is this possible?
Presumably, yes. But why can't you keep using 172.19.50.x, but with a subnet mask of 255.255.252.0? The LEA allocated this range and the others in 172.19.x.y are used by other local schools. We all access an LEA proxy so I'd rather use something different.
This will allow you to have 172.19.48.0 -> 172.19.51.255
I'm confused here - I thought 255.255.252.0 would leave 172.19.0.0 to 172.19.3.255
And it'll be easier for you as all you'd have to change is the subnet mask on the machines.
If I set up 2 interfaces on the server (derby) with
ifconfig eth0:0 172.19.50.2 netmask 255.255.255.0 ifconfig eth0:1 172.16.0.2 netmask 255.255.252.0
and turn ip forwarding on with yast, should machines on the 2 ip ranges be able to communicate. eg. ping each other
I've tried it and they don't.
What does "route -n" give?
root@derby:/home/dw > route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.19.50.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 172.16.0.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
And then I'd presume you'd have to set up the clients to say that if the need to access 172.19.50.0/255.255.255.0, they should route to 172.19.50.2,
How would I do this?
otherwise go to your default gateway (whatever that may be; usually an Internet gateway).
The gateway on each client is set to the relevant IP on Derby.
Am I trying something silly and if not what other steps do I need?
How about "route add 172.16.0.2 netmask 255.255.252.0 dev eth0:1". Or something similar? This gives the error "netmask doesn't make sense with host route"
Thanks again Dave
On Wed, 31 Jan 2001, Dave Williams wrote:
Dan
Is this possible?
Presumably, yes. But why can't you keep using 172.19.50.x, but with a subnet mask of 255.255.252.0?
The LEA allocated this range and the others in 172.19.x.y are used by other local schools. We all access an LEA proxy so I'd rather use something different.
Ah. Okay.
This will allow you to have 172.19.48.0 -> 172.19.51.255
I'm confused here - I thought 255.255.252.0 would leave 172.19.0.0 to 172.19.3.255
It *could* do, but not necessarily :-) Okay, beginners' guide to Subnet Masking, even though it's late and I should be in bed. Put simply, the Subnet mask placed a restriction on the range of IP addresses available. It defines the "unchangeable" portion of an IP address. So, using binary numbers: Your IP address was 172.19.50.0, which in binary would become: 10101100.00010011.00110010.00000000 Your proposed subnet mask would be in binary: 11111111.11111111.11111100.00000000 The 1s here define the unchangeable part of the IP address, so it'll become: 10101100.00010011.001100xy.* Now the .* you know can be any number between 0 and 255. The interesting bit will be the x & y. This can take the values of 00, 01, 10 and 11. If they're both 0, that bit of the IP address become 00110000, or 48 in decimal (hence, 172.19.48.*). If they're both one, it become 51 decimal (hence, 172.19.51.*). Making sense so far? Now, of course, you could put any values into that 3rd byte of the IP address, so you'll end up with a range of addresses, going like: 172.19.0.* -> 172.19.3.* 172.19.4.* -> 172.19.7.* 172.19.8.* -> 172.19.11.* and so on. Does that make any sense, or should I try explaining slightly better when I'm more awake?
What does "route -n" give?
root@derby:/home/dw > route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.19.50.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 172.16.0.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
Seems okay if you've only got one network card. Would it be possible to put a second network card in? It might work better, possibly, or be easier to set up? (Just a suggestion).
And then I'd presume you'd have to set up the clients to say that if the need to access 172.19.50.0/255.255.255.0, they should route to 172.19.50.2,
How would I do this?
If you're using Linux, something fairly similar to "route add -net 172.19.50.0 netmask 255.255.255.0 gw 172.19.50.2". Under Windows, I'm not so sure; I haven't played with it.
otherwise go to your default gateway (whatever that may be; usually an Internet gateway).
The gateway on each client is set to the relevant IP on Derby.
Good. Sounds fair enough.
Am I trying something silly and if not what other steps do I need?
How about "route add 172.16.0.2 netmask 255.255.252.0 dev eth0:1". Or something similar?
This gives the error "netmask doesn't make sense with host route"
Ah, yes. Whoopsy. It should have been "172.16.0.0", otherwise it'll treat it as an IP address, rather than a network address.
Thanks again
No problem :) It's what I'm (usually lurking) on this list for. Dan -- dankolb@ox.compsoc.net Oxford University Computer Society Secretary --I reserve the right to be completely wrong about any comments or opinions expressed; don't trust everything you read above--
On 1 Feb 2001, at 0:54, Dan Kolb wrote:
On Wed, 31 Jan 2001, Dave Williams wrote: <snip>
How would I do this?
If you're using Linux, something fairly similar to "route add -net 172.19.50.0 netmask 255.255.255.0 gw 172.19.50.2". Under Windows, I'm not so sure; I haven't played with it.
On Windows 2000 ( same for NT IIRC ) if you go into the Networking GUI: Start | Settings | Control Panel | Network and Dial-up Connections | Local Area Connections | Internet Protocol ( TCP/IP ) | Properties there's nowhere to add specific routes. Hmm, not very impressed. There is a command line version of ROUTE, best to look at that. ( I'm offline at the time of writing so I can't play ). Always a good idea to do: c:\temp> route 2> route.txt c:\temp> more route.txt So you can look at the command help without having to scroll up and down the DOS window. I.E. not the -p ( persistent across reboots ) flag. ( no, I didn't know dos had a notion of standard out either until I tried it ) <snip>
Thanks again
No problem :) It's what I'm (usually lurking) on this list for.
Excellent explanation of subnet masking, you should lurk less :) -- Written on the train, so all typos and mistakes are the responsibility of Railtrack.
On Fri, 02 Feb 2001, Nick Drage wrote:
On 1 Feb 2001, at 0:54, Dan Kolb wrote:
On Wed, 31 Jan 2001, Dave Williams wrote:
<snip>
How would I do this?
If you're using Linux, something fairly similar to "route add -net 172.19.50.0 netmask 255.255.255.0 gw 172.19.50.2". Under Windows, I'm not so sure; I haven't played with it.
On Windows 2000 ( same for NT IIRC ) if you go into the Networking GUI:
<snip NT> Under Win95, I've just had a look. Right click Network Neighbourhood, and go to Properties. Select TCP/IP and go to properties. Go to the Gateway tab. The first gateway listed is the default gateway. Then, type the other machine's IP address in - i.e. 172.19.50.2. OTOH, I'm not sure if that's really going to help. Darn.
Thanks again
No problem :) It's what I'm (usually lurking) on this list for.
Excellent explanation of subnet masking, you should lurk less :)
Thanks :-) But most questions are on Squid, and I haven't played with it, other than "install it and it works". I tend to answer questions which I know the answer to :) Dan -- dankolb@ox.compsoc.net Oxford University Computer Society Secretary --I reserve the right to be completely wrong about any comments or opinions expressed; don't trust everything you read above--
participants (3)
-
Dan Kolb -
Dave Williams -
Nick Drage