TheGreenButton - Windows Media Center Forums

They canceled my order due to being out of stock. Ticks me off. They were $100 bucks cheaper than everyone else.

Bummer

It took me long enough, but I think I figured out what the problem is. When I ran the Wan+2Lan2 wizard the subnets were created and assigned to separate ports of the ERL (Eth1 and Eth2). Even though the switch was configured correctly (well mostly), the router refused to accept the devices intended for the 192.168.2.1/24 subnet through Eth1. This necessitated enabling switch port 23 as an egress for 192.168.2.1/24 and cabling 23 to Eth2.

Haven't quite figured out how to change the router yet. Sounds easy enough to just add Lan2 to Eth1 but, not sure of the ramifications, and I'm sure there are lots of them.

Does this make any sense or am I still in the same nightmare?

I'm pretty backed up with work at the moment but give me a few days and I'll tell you exactly how to do it. I just got my EdgeRouter Pro in yesterday and got my load balancing setup running. Not bad so far. Terminology is not far off. Methodology is different though so it will take a little time to know what I need to know.

So you need to build a VLAN interface for the second VLAN.

Do the following. Go to the dashboard and select add interface and select VLAN.


Assign a VLAN ID and an IP address for the interface. In this case it would be the 192.168.2.1/24 interface. You'll likely need to remove that from the eth2 interface before trying to add it to the VLAN interface.



Now plug your trunk link from the switch into eth1 on the ERL and you should be good to go.

Lastly you should update the firmware on the router. 1.7.0 is out and has a nice traffic analyzer that will give you quick view into what's passing through the router.

Just a short not to let you know I received your message.

You are so cool. Thanks.

Busy with out of state guests until Aug 4-5. I'll get on it next week.

Venom51 wrote: ↑Fri Jun 15, 2012 1:22 am Nope. You just need a simple DB9 crossover cable to manage the switch and you only need it long enough to set the IP on the switch. After that you only need the cable in an emergency scenario if you screw up the config.

http://www.ebay.com/itm/New-RS232-Seria ... 414fc5a96b

Don't pay 29 bucks for one though. You can get them from Cables Direct for 6 bucks.

Venom, do you have any guide on how we can connect one end of the DB9 crossover cable to the console port on the switch if I have this kind of switches https://www.tp-link.com/ph/service-prov ... accessory/ ?

If the console port looks like an ethernet port then any of these should work.

https://www.amazon.com/cisco-console-ca ... sole+cable

Your link took me to a TP-Link accessory page for SFP modules. If that was intended to go to a switch then the link failed. If your swtich has no console port then it is either unmanaged or web managed. In that case the only way to get in is to factory default the switch, find the manual for that model switch online and set you NIC interface on the PC you are using to an IP in the range of the default IP for that model switch.