6 replies
What you need to do is "subnet" your public IP space. If the remote subnet only needs a few addresses, the solution will be different from mine. However, the concept is the same. I'll assume your public addresses are a class C, 254 addresses. at 127.127.127.x
Net A: 10.0.0.x (subnet: 255.255.255.0)
Also a device at 127.127.127.1 (router to internet)
and a device at 127.127.127.2 (the PC or Web server)
Net B: 10.0.1.x (subnet: 255.255.255.0)
a device at 127.127.127.3 (won't work)
But if you subnet the public space on each network to 255.255.255.192, then you can have up to 2 networks with 62 devices each.
The last part of the IP address in binary will determine the network & workstation id because of the subnet mask. With a mask of .192, you will have:
00xxxxxx (invalid)
01xxxxxx (1st net: 65-126)
10xxxxxx (2nd net: 129-191)
11xxxxxx (invalid)
And program your internal routers for the 56k link to forward packets accordingly.
by wpatrey
by curlergirl
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending