Pfsense with 2 modems as multiwan : cannot access webGUI of the secondary modem
trap16 last edited by
Another test today , I tried to check why pfsense can ping the tv receiver and why a computer on the LAN cannot …
I used diagnostics on WAN1 interface to capture the packets for 192.168.1.10 and found that when i'm pinging from :
- pfsense box (192.168.1.100) : the destination MAC is the MAC address of the tv receiver (the ping work in this case)
- a computer on LAN (10.0.2.1) : the destination MAC is the MAC address of the fiber modem-router (and i get no reply)
trap16 last edited by
I sorted out half of the issue, it was due to bad settings.
- I removed the gateway from the WAN1 (to fiber modem) and WAN2 (to 4G modem) interface
- I added several LAN firewall rules to pass :
1) LAN net to WAN1 net with no gateway
2) LAN net to WAN2 net with no gateway
3) LAN net to any with my failover gateway group (192.168.1.1 tier 1 and 192.168.5.1 tier 2)
And now I can ping and access the tv receiver (192.168.1.10) from my LAN
So I can now ping correctly my fiber box modem, my tv receiver from my LAN, but the 4G modem is still failing (can access it from a shell on pfsense but not from my LAN)
riccio99 last edited by
hi, i had a similar problem with another firewall (Dlink).
i added a protocol binding rule:
Local Gateway: the wan of the 4g modem
Source Networks: Any
Destination network: ip adress of the wan port of the 4g modem.
I hope it help you
Have almost the exact situation as this. Only difference my internal LAN is 192.168.1.1/24 and the address pfSense is usng for the Netgear LB1120 4G modem is 192.168.5.2 (gateway 192.168.5.1).
Failover works works great to the 4G modem if my primary FIOS gateway goes down for whatever reason.
I like the original poster cannot get to the 4G modem configuration web page from a computer on my LAN. I can ping the default web page address @ 192.168.5.1 and that works just fine. I have read all the posts I can find on this starting with the common one https://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall. That and others I found are either not exactly the same situation or are not specific enough instructions for a noob like me to translate the shorthand used into actual settings in pfSense. Using latest 2.4.2_1 version by the way.
Any help would be appreciated.
Is the 4G modem webgui address the same address as the default gateway on that interface when it's up? Is it in the same subnet as the default gateway on that interface?
Attached is what my Dashboard says . . .
Let me know if that is not the info you want.
Yes the default 4G modem web page is at 192.168.5.1. Same as the Gateway.
Hmm. Seems like that should work. Do you have good outbound NAT on the WAN_CELL interface? If connections to 192.168.5.1 are source-NAT to 192.168.5.2 and it isn't working the next thing to look at would probably be a packet capture on that interface filtered on 192.168.5.1 during a connection attempt.
Sorry for my ignorance how do I tell if I "have good outbound NAT on the WAN_CELL interface"? I have not set up any special NAT, routing, or firewall rules to make this work yet. Mostly because I don't know what I am doing. The instructions I find searching Google are too generic like "create a new outbound NAT rule". Until I have done a few of them I will need detailed instructions on how to do things like that in the pfSense settings.
On a computer on the LAN when I put 192.168.5.2 in the browser URL field I get the pfSense box log in page. If I put 192.168.5.1 I eventually get "Problem loading page" and "The connection has timed out" warnings.
Then just post a screenshot of your outbound NAT.
And having a LAN subnet of 10.0.0.0/8 is going to cause you nothing but grief. Why did you choose to do that?
Here is my Firewall/NAT/Outbound page. (If that is what you were asking for.)
By the way I think you are getting postings from trap16 mixed up with mine. I don't have the 10.0.0.0/8 deal. Maybe I should have started a different thread but I have the same problem as trap16. Just a slightly different set up.
In my setup I think the 10.3.201.0/24 network rules in the Firewall were automatically set up when I tried to configure OpenVpn. I have deleted my attempts to set it up for now so if you think I should delete those rules let me know.
Yeah, you're right. I was confused. Your NAT rules look fine.
So what you want to do is start a packet capture on WAN_CELL for all traffic for host 192.168.5.1 then try to connect to the modem then stop the capture.
It would probably be best if you attached the capture since MAC addresses might be important. Or at least set the detail to Full, View Capture again and post that.
Is this the settings you want me to try for packet capture?
How long do I run the capture? Until the browser times out?
Here is the capture with the settings I posted. Ran it until the browser timed out.
Your modem is not accepting the ARP Reply for whatever reason. You'll need to ask them. pfSense is doing everything it is supposed to there.
11:31:58.374001 0a:40:06:d2:5d:5d > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.5.2 tell 192.168.5.1, length 46
11:31:58.374014 00:08:a2:0b:8e:0e > 0a:40:06:d2:5d:5d, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Reply 192.168.5.2 is-at 00:08:a2:0b:8e:0e, length 28
11:32:14.614066 0a:40:06:d2:5d:5d > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.5.2 tell 192.168.5.1, length 46
11:32:14.614083 00:08:a2:0b:8e:0e > 0a:40:06:d2:5d:5d, ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Reply 192.168.5.2 is-at 00:08:a2:0b:8e:0e, length 28
and on and on.
Thanks Derelict for your help on this.
Tell me this, Why if I unplug the 4G modem from our pfSense box and plug it into a computer I can get the configuration web page at 192.168.5.1? No changes at all to the modem required to do this. Did not even power down or reset the modem. Does that mean my Linux computer talks to the modem differently then the pfSense box does?
No idea. Would need to see a PCAP from that computer port in that situation to see what is different.
Does that mean my Linux computer talks to the modem differently then the pfSense box does?
ARP is ARP.
OK I did a tcpdump with the Linux machine connected directly to the 4G modem. Started it then went to 184.108.40.206 and stopped it as soon as the log in page for the modem came up. Not sure I was doing it correctly but here it is.
Yeah that doesn't even try to ARP - it seems to have already accepted that MAC address into it's ARP table based on received traffic (as it should).
You are going to have to ask the modem manufacturer/provider why it refuses to acknowledge the ARP Reply the WAN port is sending.
Sorry. It's really as simple as that. pfSense is doing nothing wrong.
I have some questions.
What does not even try ARP? The modem or my Linux computer tied to the modem?
What has already accepted what MAC address into it's ARP table?
I am just wondering if either in the modem or pfSense can we put th MAC manually to get this to work.
Sorry if these are dumb questions but I am new to all this.
The modem doesn't try ARP because it has accepted the MAC address for that computer based on other traffic.
Or at least the ARP was not included in your capture.
You MIGHT be able to make it work by spoofing the MAC address on the WAN but I would CALL THE ISP AND MAKE THEM FIX IT PROPERLY.
Why are people so reluctant to call the people they are actually PAYING?!?
(Please tell me you have rebooted the modem.)
Derelict, While I am flattered that you refer to me a famous historical figure I can claim no such celebrity.
Anyway so you answered my questions. It is the 4G modem that would have to have the computers MAC preapproved so to speak so it would work. Unfortunately the modem interface has no way to manually set that. As you said I may be able to have pfSense spoof the computers MAC address but either way would limit what computer on my LAN I could access the web page from.
Sorry to frustrate you on this but the ISP (Ting) is no help on this as they did not supply the modem. It's not their recommended device. On top of that Netgear has about the worst support policies on the planet. They often take several months just to start looking at a support ticket.
Anyway thanks again for all the help.
So you're rolling your own and this is what you get.