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? -
@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.
-
@johnpoz said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
@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.
Thank you
-
@hanssolo said in Difficulty reaching Opt1 via LAN WiFi - Internet is not an issue here:
I meant the network settings on the wifi connected device, laptop or whatever.
-
I don't expect to see a gateway field on the LAN side config of a SOHO device like that.
Is that actually the LAN side?Normally you can only set a gateway, and hence a default route, on the WAN. That means that when you use it as an AP like this is has no default route and hence cannot itself access anything outside it's own subnet. That also means it cannot reply to anything from outside it's own subnet so you should expect to not be able to ping it from OPT without an outbound NAT rule.
That should not prevent connected wifi clients connecting to OPT though since they are using it only as a layer 2 device.
Steve
