I am just about to cross the 50 customer mark. I promised myself at 50 I would learn how to route and convert my bridged and switched network. Everything is running smoothly but I want to plan to lose the bridged setup.
Currently my core router is the PPPoE server. All clients are ubnt M radios in router mode. Broadcast storms etc are not really a problem as all customer traffic runs through the pppoe tunnels but I still want to upgrade. I have a tik at every tower base but they are currently just switching or bridging.
What would be the best solution for my network. Can I get away with just static routing or should I go OSPF? I want to be set up for growth and not have to mess with this again the next time I hit a certain mark. I would also like to eventually close my network on each end for redundancy, so that means OSPF right? Should I just run one area if I go OSPF?
I would still like to keep the pppoe server at the core as some clients need a public IP and currently I only have a /28 to give out so I cannot route blocks of publics all over just yet.
EOIP Tunnels back to the core pppoe server seems to be the best thing until I get a larger block of addresses.
How do I access clients radios to do maintenance? Do all the customers become accessible once I enable ospf?
Oh ya Happy New Year everyone. Hope it is prosperous!
Can i ask as you appear to be using the same ip range for all client sectors 192.168.88.XX can your clients ping to each other and will other CPE’s appear with network shares (shared printer,drives,?) if clients do a network scan,
I have a routed network using 10.152.0.x and OSPF, at each AP which assigns it’s own wireless PPPOE to the clients radio using 10.100.x.x then the eth side of the CPE assigns DHCP pool using 192.168.1.X, I disabled “default forward” on wireless so clients remain isolated to each other, I am very happy with the stabilty of the network of course you have minor and annoying glitches when MK introduces software upgrades but none that effect the total network
All of the clients cpe get a 10.0.0.x address via pppoe. They are set in router mode. All clients are basically tunneling to the core router via the pppoe. I have rules in place so that no one can see each other. The 192.168.88.x network is just to access the radios and routers. It has been working well so far. I can torch a port on the main bh and only see management traffic my pigs etc. All client traffic is encapsulated in pppoe. It works but I know it’s not the best solution and will eventually need to be changed.
Yes, use OSPF. How many areas you want to use depends on the physical and logical topology of your network. All areas must connect to the backbone area 0. Keep things simple initially and do not use virtual links and sham links, and remember that OSPF OS expensive to converge but cheap to keep running. Link failures within an area don’t usually affect other areas as they only see summary routes. Segment into areas so that important towers become area border routers so that anything happening behind them doesn’t affect the rest of the network.
Cisco’s general OSPF information is very good if you don’t have any books dedicated to the topic and want design information. Your network is small at the moment so you could just run everything as area 0 to start with, but once you introduce towers coming off existing towers you would introduce new areas.
All of the clients cpe get a 10.0.0.x address via pppoe
I didn’t see that - Ok why not just route the ports of the 750’s with /30 of the 192.168.88.x for both PTP links and client AP,
On the 750’s setup PPPOE for the Client AP’s, each 750 having it’s own 10.0.x.x PPPOE
Are you using Dude its great for monitoring the network.
Thanks for the reply, In my network the other towers are connected off of the main tower (mountain top), so should they be in different areas? Or should I wait until I have more towers before adding areas beyond backbone?
Are you suggesting I just do static routing? I will probably do pppoe servers on each router but I have a few customers that need static public IP’s. I only have a /28 of publics available so I am thinking EOIP tunnels back to the core for now once I get OSPF running.
I have a bunch of hardware at the office so I will definitely set this up on the bench first before I start messing with the running network
We offer it as an extra charge. One is a radio station up on one of the towers, they monitor their station over the web and also can use the connection for a backup stl audio link if their primary audio fails. That and the tower company we colocate on has camera systems and requested public ip at each site as part of the lease agreement. Other than that, for now we usually just sell residential connections and no one has asked for a public ip there. I would like to give every client a public eventually but for now, routing small subnets to each tower is too wasteful of our limited ips.
I set up a small static routed network on the bench with EOIP tunnels back to the core and it seemed to be working. Its just tricky to manage the client radios with all the different ip ranges. I was hoping to just skip it and learn OSPF. Plus I would like to eventually close up the network ends and have OSPF to handle the redundancy of one link fails.
