Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here
-
@jarhead said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo So clearly not a pfSense issue since wired works.
Look at the AP config.
Is it actually an AP or is it a router being used as an AP?
How is it connected? Does it have a WAN and LAN port?The Mode is choice 1).
Standard Wireless Router
It is connected to the LAN, not a modem. Yes, it has one WAN port and 4 LAN ports. I am unly using LAN ports on it.
-
I just tried to PING and TRACEROUTE from logged into the wireless router to the Opt1 interface and both failed.
Then I tried to ping from Opt1 to 192.168.0.5 (WiFi Router) and that also failed.
However, the firewall logs show an entry for the ICMP as if it succeeded.
Nov 12 18:48:03 ► LAN let out anything IPv4 from firewall host itself (1000004765) 192.168.4.1 192.168.0.5 ICMP -
When I use the pfsense DIAGNOSTICS......
I can successfully ping from the LAN to Opt1 and from Opt1 to LAN.
However, the problem is from LAN Wifi to Opt1
-
@hanssolo Is the AP's IP static?
Did you set the correct gateway? -
@jarhead said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo Is the AP's IP static?
Did you set the correct gateway?Hi Jarhead.
Yes, the AP's IP address is static and set to 192.168.0.5The Gateway is set to the LAN IP Address of 192.168.0.2
Wifi Seems to work great other than this WiFi connection attempt to the server on Opt1
Since the connection from the LAN works fine on ethernet, I'm thinking it must be a WiFi routing issue but that's a guess.I tried to set up a static route from 192.168.4.1 to LAN Gateway 192.168.0.2 but the WiFi router will not allow it regardless of the subnet mask. (bummer)
-
@hanssolo The gateway should be .1, not 2.
-
@jarhead said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo The gateway should be .1, not 2.
It is (was) 192.168.0.1
The 192.168.0.2 above was simply a typo on my part. Sry.
This is definitely a WiFi issue since it works perfectly over ethernet.
-
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
The Mode is choice 1).
Standard Wireless Router
It is connected to the LAN, not a modem. Yes, it has one WAN port and 4 LAN ports. I am unly using LAN ports on it.So it's a wifi router wrongly used as as an AP.
If it has no real AP mode replace it with a real one.
You may also consider to install OpenWRT on it if you want to take the challenge, but it's only supported by elder versions.I just tried to PING and TRACEROUTE from logged into the wireless router to the Opt1 interface and both failed.
At least this should work, since you said communication between wifi and LAN devices is working.
Run a packet capture on pfSense, while you try to ping its LAN IP, and see if the packets are arriving in the interface.I tried to set up a static route from 192.168.4.1 to LAN Gateway 192.168.0.2 but the WiFi router will not allow it regardless of the subnet mask.
Don't add additional static routes. It is sufficient if the pfSense LAN IP is set as default gateway on all LAN devices.
But you can recheck the network settings, especially the mask on all involved interfaces. Maybe there is something wrong. -
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@jarhead said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo The gateway should be .1, not 2.
It is (was) 192.168.0.1
The 192.168.0.2 above was simply a typo on my part. Sry.
This is definitely a WiFi issue since it works perfectly over ethernet.
Well, it isn't a "wifi" issue, it's an issue with the AP itself.
You said you can't ping from the AP to OPT1, that would use the wired part of the AP. That's why I suggested checking the gateway.
You need to go over the config on the AP. Has to be something wrong there. -
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
I am unly using LAN ports on it.
Did you turn off its dhcp sever? If you want to use wifi router as AP that does not have AP mode. Then yes you connect it to the network via lan port, but you also need to disable its dhcp server. or wifi clients will get the wifi routers IP as its gateway.
Also what wifi router are you using.. It rare that they allow for setting a gateway on lan unless your using 3rd party firmware on it. Setting the gateway on the wifi router wan, that you are not using would be not work.
edit: But the AP not being able set a gateway is not really an issue for using it, since its wifi clients would be using pfsense as the gateway. If you need/want to admin the AP from another network, the easy solution if you can not run 3rd party or actually set gateway on the lan interface - I don't recall ever seeing native wifi router firmware supporting that.
You can do a source nat on pfsense, so traffic from another network looks like its coming from the pfsense IP when going to the AP IP address. So then you can access its web gui from your other networks.
-
@viragomann said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
So it's a wifi router wrongly used as as an AP.
Yes
If it has no real AP mode replace it with a real one.
You may also consider to install OpenWRT on it if you want to take the challenge, but it's only supported by elder versions.OK.
At least this should work, since you said communication between wifi and LAN devices is working.
Run a packet capture on pfSense, while you try to ping its LAN IP, and see if the packets are arriving in the interface.I did and they do not seem to be. I need to check to make sure ICMP is allowed.
Don't add additional static routes. It is sufficient if the pfSense LAN IP is set as default gateway on all LAN devices.
But you can recheck the network settings, especially the mask on all involved interfaces. Maybe there is something wrong.OK. will do and thanks. Since it works perfectly over ethernet to the same destinations, it seems it may be the wifi router? What do you think? I have installed a different WiFi router and set it up in AP mode. I have the same problem.
-
@jarhead said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@jarhead said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo The gateway should be .1, not 2.
It is (was) 192.168.0.1
The 192.168.0.2 above was simply a typo on my part. Sry.
This is definitely a WiFi issue since it works perfectly over ethernet.
Well, it isn't a "wifi" issue, it's an issue with the AP itself.
You said you can't ping from the AP to OPT1, that would use the wired part of the AP. That's why I suggested checking the gateway.
You need to go over the config on the AP. Has to be something wrong there.It's a TP-Link WR940N.
I can't set a Gateway for the Network. There's no place for that in the Router in question.
But I would think you must be correct. Something with the AP not playing nice with the gateway or something like that (maybe, I don't know) -
@johnpoz said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
I am unly using LAN ports on it.
Did you turn off its dhcp sever? If you want to use wifi router as AP that does not have AP mode. Then yes you connect it to the network via lan port, but you also need to disable its dhcp server. or wifi clients will get the wifi routers IP as its gateway.
Also what wifi router are you using.. It rare that they allow for setting a gateway on lan unless your using 3rd party firmware on it. Setting the gateway on the wifi router wan, that you are not using would be not work.
edit: But the AP not being able set a gateway is not really an issue for using it, since its wifi clients would be using pfsense as the gateway. If you need/want to admin the AP from another network, the easy solution if you can not run 3rd party or actually set gateway on the lan interface - I don't recall ever seeing native wifi router firmware supporting that.
You can do a source nat on pfsense, so traffic from another network looks like its coming from the pfsense IP when going to the AP IP address. So then you can access its web gui from your other networks.
Hello,
DHCP is off. I use static IPsI'm using a TP-Link WR940N
I'll have to read and study the Source Nat suggestion a while. It's above my network pay grade so I have to really think about it.
Thanks much. -
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
Since it works perfectly over ethernet to the same destinations, it seems it may be the wifi router? What do you think?
The reason could also be wrong network settings on the wifi device. Therefore I asked you to check it.
So what is the network mask?
What is the gateway set to? -
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
DHCP is off. I use static IPs
Are you still having issues with connectivity - you don't have a conflict? Your AP lan IP is set different than pfsense IP?
I really never understand why not just use dhcp - that for starters validates connectivity. Unless there is no dhcp server to use, its better to use dhcp.
I have gone over source natting multiple times - if that is your only problem left is getting to the AP gui, I can link to multiple threads where I go over it. Its a simple outbound nat on the interface for the network your AP is on.
But again not being able to set a gateway on your AP has nothing to with clients working or not.
-
@viragomann said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
Since it works perfectly over ethernet to the same destinations, it seems it may be the wifi router? What do you think?
The reason could also be wrong network settings on the wifi device. Therefore I asked you to check it.
So what is the network mask?
What is the gateway set to?
-
Wrong mask shouldn't stop from talking to pfsense - unless it was really wrong and internet, but sure wrong mask would prevent a client on the wifi network from talking to say a different network of yours - if the mask included that other network IP space.
Setting manual can lead to typo's wrong gateway, wrong mask - creating a duplicate, etc.
Manual should really only be set on some device that doesn't support dhcp (that would be rare) Or there is no dhcp server available - which is not the case since you have pfsense. Or its a san or other network that is not used to access anything else - for example I set static on the interface on my nas and my pc - because this is a 2.5ge network just between them. There are no gateways set, there is no dns set, and there is no dhcp server on this 2 device network.
dhcp also allows you at a future time to change up somethiing, or all of it IP range, dns they point to, etc. mask even.. And if you get an IP via dhcp - you know for sure your device has connectivity to the dhcp server..
-
@johnpoz said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
DHCP is off. I use static IPs
Are you still having issues with connectivity - you don't have a conflict? Your AP lan IP is set different than pfsense IP?
I really never understand why not just use dhcp - that for starters validates connectivity. Unless there is no dhcp server to use, its better to use dhcp.
I have gone over source natting multiple times - if that is your only problem left is getting to the AP gui, I can link to multiple threads where I go over it. Its a simple outbound nat on the interface for the network your AP is on.
But again not being able to set a gateway on your AP has nothing to with clients working or not.
If you would be so kind as to give me a link I would be glad to read it.
Thanks -
@johnpoz said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
Wrong mask shouldn't stop from talking to pfsense - unless it was really wrong and internet, but sure wrong mask would prevent a client on the wifi network from talking to say a different network of yours - if the mask included that other network IP space.
Setting manual can lead to typo's wrong gateway, wrong mask - creating a duplicate, etc.
Manual should really only be set on some device that doesn't support dhcp (that would be rare) Or there is no dhcp server available - which is not the case since you have pfsense. Or its a san or other network that is not used to access anything else - for example I set static on the interface on my nas and my pc - because this is a 2.5ge network just between them. There are no gateways set, there is no dns set, and there is no dhcp server on this 2 device network.
dhcp also allows you at a future time to change up somethiing, or all of it IP range, dns they point to, etc. mask even.. And if you get an IP via dhcp - you know for sure your device has connectivity to the dhcp server..
Yes,
I recall some time ago you advised against Static IP assignment.
I have to reassess my reasons for still using it.I could have DHCP and use IP Binding (I think)
-
@hanssolo yeah you can easy set a reservation if you want devices to have a specific IP.
here is link to where I gave pictures and examples of a source nat for something that doesn't have a gateway
https://forum.netgate.com/post/868337
You could be more specific in the rule, so only say specific client and only to your AP ip would be source natted.
