Successful bridge, but unable to connect to internet
-
Do I need to have seperate subnets for the wireless interface and the LAN interface? they are currently both 192.168.0.x
do I need to change the wireless to 192.168.1.x or something?
-
I figured it out. In the Interfaces/Wifi tab in the Gateway box it says:
If you have multiple WAN connections, enter the next hop gateway (router) IP address here. Otherwise, leave this option blank.
I only have one WAN connection, and this was left blank. I had to put in my pfsense gateway to give access to the internet. I'm not sure if anyone else has experienced this but maybe we should put in a request or something to have it fixed?
-
I figured it out. In the Interfaces/Wifi tab in the Gateway box it says:
If you have multiple WAN connections, enter the next hop gateway (router) IP address here. Otherwise, leave this option blank.
I only have one WAN connection, and this was left blank. I had to put in my pfsense gateway to give access to the internet. I'm not sure if anyone else has experienced this but maybe we should put in a request or something to have it fixed?
This is not necessary. I have configuration running where this is not required.
-
After a while I came back to the wireless client and it could no longer connect. I now have to set the LAN interface to bridge with the WiFi interface. This allows connection to the internet for the wireless clients, and when I unbridge it they can no longer connect. I don't understand what is happening here? Is bridging supposed to have anything to do with internet connection ?
-
Maybe something that is affecting your testing: All members of a bridge have to be up (link) for the bridge to pass traffic. So if LAN is down and your wireless nic is bridged to LAN you'll have some issues.
-
Also make sure you are not using the same IP address on multiple interfaces.
-
WAN: DHCP, 72.x ip
LAN: 192.168.0.1/24
WiFi: Bridged to LAN (so IP box greys out)
I have tried unbridging it and setting the IP manually to 192.168.0.2, but that results in wireless clients being unable to ping the pfsense box, 192.168.0.1 or 192.168.0.2. (No route to host). They can make a connection with the AP, they just cannot ping it.Also as I said before, the same thing happens if I only have the WiFi interface bridged to the LAN interface. Wireless clients can connect to the AP but cannot ping it. I must have both the WiFi bridged to the LAN and the LAN bridged to the WiFi
Is this proper to be bridging them both to one another?
-
does anyone have any insight as to why the wireless client will lose access to the internet at a random amount of time? It can still access the AP and ping the pfsense box, but I have to go to the LAN interface and unbridge it to the WiFi, and then rebridge it, and it can connect to the internet again. Thanks
-
So the client previously in question is a macbook (192.168.0.20). Now when trying to connect a PC wireless client (192.168.0.21), they can connect to the AP, ping the AP (pfsense box, 192.168.0.1), but cannot access the internet. They can ping google, an IP is resolved, but Request timed out. Does anyone have any ideas what is going on here? I'd really appreciate any input. Thanks.
-
I need a macbook donated to be able to reproduce ;D
-
ahahahhahaa :D
yea, i'll get right on that. i'm currently trying to steal the girl's since my only portable computer is a k6 450mhz
-
this is my states while pinging and trying to connect to google.com
I guess this means it isnt a NAT issue ?Proto Source -> Router -> Destination State
icmp 64.233.187.99:58624 <- 192.168.0.20 0:0
icmp 192.168.0.20:58624 -> 72.186.197.246:43117 -> 64.233.187.99 0:0
tcp 209.85.165.104:80 <- 192.168.0.20:49248 SYN_SENT:ESTABLISHED
tcp 192.168.0.20:49248 -> 72.186.197.246:57479 -> 209.85.165.104:80
ESTABLISHED:SYN_SENT