Hello! I have replied to you inline!
I thought of taking the chance to remove some
"technical debt" and make everything from
This is a rookie mistake. Every in-place system encodes business
knowledge, most of it forgotten and much of it still relevant. From
your comments I infer that you haven't been doing the job long enough
to know where the skeletons are buried.
Indeed, I do not have the experience of the previous person who set it up, but I have seen many things that appear not to be good and cause "friction" to the employees.
1. Currently we do not have IPv6 in our network but I
have seen the ISP is giving us a "/56 Block" which
from what I understand is a couple hundred "/64 Subnets".
Good for you! We've been urging folks to deploy IPv6 for years and
you're taking the advice to heart.
Now stop. IPv6 has enough inherent issues and problems that you'll
want to deploy it when your configuration is otherwise quiescent. If
you do it while also making other large changes, you're begging to get
I know, but I think the time I have is more than enough for IPv4 and "if I don't do it now, I may never do it"..
2. The previous administrator did some bad
job in some parts of the network. We have
an internal router protocol to move traffic between
routers, but in some cases he used NAT instead
of adding these subnets to the router protocol.
I urge you to tread lightly. You don't know what business knowledge
was encoded in this configuration. Maybe the servers respond
differently depending on whether the source is internal or external
and some of the origins should be treated to the external rules.
No, this is the same behavior and currently employees have access to routers so they can port forward so other departments can reach their computers. We also use "UPnP" in these routers because some applications need direct host to host communication. Both subnets are trusted in the current design. I wouldn't claim this if I wasn't sure. Currently I have not found a single legitimate use and I have asked users, server administrators, etc.
I have found two protocols in our router that are
good and support IPv6 and they are OSPF
OSPF is an interior gateway protocol. Use between routers within your
network. BGP is an exterior gateway protocol. Use it when you want to
talk to multiple ISPs at the same time.
I was talking about BGP with private "ASNs" to be used internally and if we ever make a BGP connection to the Internet in the future, use a different router table and a route aggregate.
3. In our old network we use "VRRP" which from
what I know is a system for routers to shae IPs
and load balance or "failover" the traffic. I have
seen that IPv6 has a built-in system which is similar
and has something like priorities, etc. What
happens if I have two routers with same priority?
If the guy who wrote the stack wasn't asleep at the switch, the host
will pick one and use it as long as the router keeps advertising it.
But it's not a good idea to tempt fate - set each router at a
I know, but one team is responsible for marketing and is doing video editing from a file server, so we have a lot of workstations moving at Gigabit speeds. I thought of two solutions:
Buy a switch with a 10 Gb/s port to connect to the file server subnet, which seems overkill because the cheapest I can find has 48 ports and we'll need 7. The second solution was to add a 16-port Gigabit switch and then have 2-3 routers move traffic to the file servers and give each client a different gw. This ensures redundancy and possibly more bandwidth.