Some dual-wan issues I need help tracking down



  • If anyone can help me out here, I'd be very appreciative. I just can't figure out what is going wrong.

    I have two FiOS lines on the two properties we own on the street. My house has a 35/35 connection, and the other house has 25/25. I used two Ubiquiti Loco M5s to bridge the gap, and they get almost perfect throughput.

    I set up the dual wan in pfsense, and made the gateway groups + routing rules.

    My two issues are these:

    Does anyone have any idea where I should look to see what may be causing this?

    Only weird thing I can find is the system log being spammed by this:

    Mar 4 21:49:16 	inetd[48602]: 19027/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19027/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19026/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19026/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19026/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19026/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19025/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19025/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19025/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19025/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19024/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19024/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19024/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19024/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19023/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19023/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19023/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19023/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19022/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19022/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19022/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19022/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19021/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19021/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19021/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19021/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19020/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19020/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19020/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19020/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19019/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19019/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19019/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19019/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19018/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19018/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19018/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19018/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19017/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19017/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19017/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19017/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19016/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19016/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19016/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19016/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19015/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19015/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19015/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19015/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19014/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19014/udp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19014/tcp: bind: Address already in use
    Mar 4 21:49:16 	inetd[48602]: 19014/tcp: bind: Address already in use
    

    I assume there is some relation to at least the speedtest failures?

    Thanks again!



  • Who is the internet gateway from 35/35 and 25/25 datalinks? Ubiquit?



  • @marcelloc:

    Who is the internet gateway from 35/35 and 25/25 datalinks? Ubiquit?

    This is probably important information, sorry for leaving it out.

    The 35/35 link's gateway is the local FiOS gateway/router at the CO. Direct Ethernet from the ONT.
    The 25/25 link's gateway is the Verizon Actiontec router at the other house. This is sent over the UBNT PTP link. The pfSense box is set as the DMZ of that network.

    If I use both links thru pfSense separately, they work flawlessly. As soon as bonding happens, that's when things go awry.



  • Are you configuring a lan behind pfsense on this bridged lan?

    Hosts –-> pfsense ---> bridge---> gateway1
                                          |------> gateway2

    Also try to check if there is any other wan test on pfsense. During your test, error says That there os another process on ports it want to use.



  • @marcelloc:

    Are you configuring a lan behind pfsense on this bridged lan?

    Hosts –-> pfsense ---> bridge---> gateway1
                                           |------> gateway2

    Also try to check if there is any other wan test on pfsense. During your test, error says That there os another process on ports it want to use.

    Um, not sure what you mean, but here is a network diagram of what is running.

    Verizon CO (pub IP = .222) - > FiOS Actiontec (192.168.1.1) - > UBNT LOCO M5 PTP –- > (gateway is now 192.168.1.1) -----|
    Verizon CO (pub IP = .111) ----------- Ethernet --------------------------------------> (gateway is Verizon's .1 router) ----| pfSense box –---> LANs/Hosts



  • Ok.
    you will need to nat from lan to wan on pfsense or set a static route on gateways to reach the network That is behind your gateways.

    On pfsense, as well as I read on forum, if you set a gateway on interface it will nat with pfsense ip.

    If you removed the gateway from interface tab, then you may need to configure automatic outbound rules to get it working.



  • @marcelloc:

    Ok.
    you will need to nat from lan to wan on pfsense or set a static route on gateways to reach the network That is behind your gateways.

    On pfsense, as well as I read on forum, if you set a gateway on interface it will nat with pfsense ip.

    If you removed the gateway from interface tab, then you may need to configure automatic outbound rules to get it working.

    Well, I believe I have automatic NAT'ing enabled, I've never had an issue with anything before.

    Where should I look to see if this is the problem? Automatic NAT is enabled in Outbound Rules or whatever you call it on the NAT settings area.


Log in to reply