AT&T Metro E setup help needed
shanew last edited by
I have looked and searched and begged the AT&T folks. They do not want to support pfSense.
I have had a MetroE circuit up for some time thru Windstream. We are jumping ship and ATT has brought in a new fiber line. They hand off the connection with a Ciena 3930. I am plugged into port 0 as they instructed me to. On the WAN connection my settings were to be 12.52.65.x /255.255.255.252 When I bring it up with that info no problem I can surf although not at the speed we subscribed. I imagine it has to the be the full-duplex setting on the card that I cannot get to stick. I might swap the interfaces because it is a Realtek chip and I have heard of issues.
So that part is working until I get to the public IP addresses that were assigned to me. 220.127.116.11/27 ( made up the ip addresses but they are similar) I cannot figure out how or what I am doing at this point. I have met my match. When the IP addresses were in all the same subnet I just created CARPs but it will not work for me or I am doing something stupid
I do appreciate anyone looking at this to give me a hint in the right direction. I'm not looking for spoon-feeding just a general direction.
miloman last edited by
I cannot figure out how or what I am doing at this point.
Neither can we… Details dude. What have you tried? What exactly does not work?
kejianshi last edited by
You will have to bridge to their network and create VIPs and use VLANs, I'm pretty sure.
I am on verizon fios here but its DHCP assigned, so a bit different. In the past I set up a multi-IP fios pfsense and it wasn't so hard.
But yeah, you need to give details.
What guide di you try to use?
shanew last edited by
quote>–-So that part is working until I get to the public IP addresses that were assigned to me. 18.104.22.168/27 ( made up the ip addresses but they are similar) I cannot figure out how or what I am doing at this point.
this circuit I has a block of IP addresses in the class c range that are supposed to be routed to the other Public Ip in the A class that they gave me. I tried putting in the 12.x.x.x ip address as the DG and using the first IP address in the C class as the IP on the WAN interface. I then put the remaining IP addresses as IP Aliases under CARP settings. I can ping the public IP addresses from the LAN side but cannot ping from a different circuit on the WAN side. When I do trace route it is one hop.
In review. When I use the 12.x.x.x settings the circuit will start routing and work. Once I told the ATT rep that that was working he went ahead and assigned me the block of IP addresses in the class C range. So I assumed they use the 12.x.x.x to provision the circuit, test it out and then assign the real IP addresses but using the Class C settings as I have for many years results in no surfing. The only thing I could get from the tech was I need to put the 12.x.x.x IP address as the DG. The graphic below is a sample config from a Cisco
![10-4-2013 7-47-15 AM.png](/public/imported_attachments/1/10-4-2013 7-47-15 AM.png)
![10-4-2013 7-47-15 AM.png_thumb](/public/imported_attachments/1/10-4-2013 7-47-15 AM.png_thumb)