*NEWB* After Install it won't boot !
-
I can nolonger see the network,
Which network? - the WiFi network?
Can you still access the web GUI through the wired interface?
Does the pfSense uptime suggest it hasn't crashed?
Please retain the crash report a little longer. But there probably won't be any point looking at it if pfSense 2.1 doesn't crash.
-
Yes I can nolonger see the Wifi network on the Available network list, I can still use the GUI yes, The uptime clearly shows that its hasn't crashed the system has been running for about an hour or so 55 minutes to be exact, I still have the crash report saved, honestly unless I go through my 1.5 TB of junk I'll probably always have it, I am getting the error or warning, "ral0: device timeout"
-
There have been some posts about problems with ral interfaces and some users have swapped them for other devices.
On one of my pfSense boxes I use a TP-Link WN651GD PCI card with Atheros chipset. This is no longer available and I have seen at leat one report of trouble with its apparent successor, the WN350GD.
On my other pfSense box I have had good results from a Tenda W311U USB WiFi NIC but this seems to be no longer available in retail shops in Australia. The TP-Link WN321G reportedly uses the same chipset as the W311U and costs around the local equivalent of US$12 at my local retail computer parts shop.
It might be better use of your time to abandon your current WiFi NIC and try another.
The W311U and WN321G (and other devices using the Ralink RT3020 chipset or similar) require a small tweak to work correctly if present at system startup: add the line
runfw_load="YES"
to /boot/loader.conf.local.
-
I have a D-Link AirPlus G (DWL-G510) I am going to try, I'm not 100% sure on the chipset I have read it is an atheros chipset or a ralink, I am going to try it though results down below.
Well it is an atheros 2413, I have followed the previous steps,
Quote,
"I suggest you put back the Gigabit interface and on reboot, from the console reset to factory defaults (in case your previous changes will cause ongoing problems), re-assign interfaces assigning the onboard and Gigabit interfaces to WAN and LAN respectively and reboot. (This should mean you can access the pfSense GUI while messing with the wireless interface. Once the wireless interface is working the interface assignments can be changed if desired.)Then access the pfSense GUI and do what you did previously EXCEPT assign the wireless interface to OPT1 rather than LAN, DON'T go through the Interfaces -> (assign), Wireless tab, fill in your Wireless details on the Interfaces -> OPTx page, Save and Apply. Does the web GUI still respond? Are you able to detect the wireless network you configured?"
I got a little further, I am able to see it, I can still use the GUI connected to the PCI Nic, but when I connect to it, the loading wheel just spins, until it gives up, There is no sign's what so ever on the console, so here I am stuck,
ask for any more info, I cannot think of anything else to add, I can't think to much really, I'm extremely tired, I hope I gave enough,
Thanks
Nathan
-
I got a little further, I am able to see it, I can still use the GUI connected to the PCI Nic, but when I connect to it, the loading wheel just spins, until it gives up,
ts not clear what you mean by "connect to it" - get your laptop to use its WiFi interface then point a browser to the IP address of the pfSense WiFi interface?
There is no sign's what so ever on the console, so here I am stuck,
What were you expecting to see on the console? No news can be good news!
I think I mentioned earlier that there would still be some tweaks to perform once you could see the the WiFi network name you had configured.
Did you laptop successfully receive an IP address, and IP address for default gateway and DNS from pfSense over the WiFi link? If so, as Stephenw10 suggested earlier you probably need to add a firewall rule to allow "open access" on the WiFi interface. After adding the rule you will need to reset firewall states (see web GUI Diagnostics -> States, click on Reset states tab then click Reset States button). Then check you should be able to access the Internet over the WiFi link. (Default configuration for the firewall is LAN can access everything, access through other interfaces is blocked.)
-
I'm using, an iPod , I ment that my iPod touch could not connect to the Wifi it will just sit there trying but it gives up, as for the console I thought it would have shown me similar errors as to before, about the tweaks, I could have read it wrong but it seemed like you had to do that only if you had the 2 adapters,
It might be better use of your time to abandon your current WiFi NIC and try another.
The W311U and WN321G (and other devices using the Ralink RT3020 chipset or similar) require a small tweak to work correctly if present at system startup: add the linerunfw_load="YES"
to /boot/loader.conf.local.
Correct me if I'm wrong, I could have misunderstood the sentence as I am very tired,
I have found the Firewall Rules, but it is unclear to me as to what I should choose for the settings, could you give me a generic setting so that it will have "open access"
Thanks
Nathan
-
Forget the loader.conf.local tweak. It applies only to USB devices with particular Ralink chipsets.
I'm using, an iPod , I ment that my iPod touch could not connect to the Wifi
OK step by step:
1. Is DHCP server enabled on the WiFi interface?
2. Do you see a DHCPDISCOVER from your iPod (did you mean iPad? I though iPods were portable music players) in the DHCP server log - see Status -> System Logs, click on DHCP tab. -
IPod touch is like an iPhone with no phone. It has wifi. ;)
Steve
-
Right is what you are steve, Bob, I have now enabled the DHCP server after a hunt for it, the only thing is,
is that I can't think the appropriate I.P addresses for the range, I chose 192.168.1.132 > 192.168.1.134
but I get an error saying "The specified range lies outside of the current subnet." The subnet is 192.168.1.135 -
I have now enabled the DHCP server after a hunt for it, the only thing is,
is that I can't think the appropriate I.P addresses for the range, I chose 192.168.1.132 > 192.168.1.134
but I get an error saying "The specified range lies outside of the current subnet." The subnet is 192.168.1.135Please provide the output from pfSense shell command```
/etc/rc.banner
-
WAN (wan) -> fxp0 -> v4/DHCP4: 192.168.1.121/24
LAN (lan) -> xl0 -> v4: 192.168.1.126/32
WIFI (opt1) -> ath0_wlan0 -> v4: 192.168.1.135/32Well by looking at that I think the bottom two are on the same subnet, is that the problem ?
-
WAN (wan) -> fxp0 -> v4/DHCP4: 192.168.1.121/24
LAN (lan) -> xl0 -> v4: 192.168.1.126/32
WIFI (opt1) -> ath0_wlan0 -> v4: 192.168.1.135/32Well by looking at that I think the bottom two are on the same subnet, is that the problem ?
You are catching on.
It is a problem that all three interfaces are on the same subnet.
It is a problem that LAN and WIFI interfaces have 32 bit network masks.
I suggest you reassign LAN to be 192.168.4.1/24 and WIFI to be 192.168.8.1/24 then on WiFi you could enable DHCP with a range of (say) 192.168.8.65 to 192.168.8.126.
With the change in LAN IP address you will need to make a corresponding change in the IP address of the system you use to access the pfSense web GUI, say change it to 192.168.4.2.
-
What you have suggested worked fine, I'm sure you thought it would to, if I didn't screw it up lol,
I have connected fine with my iPod Touch, I just can't access anything, Should I try the firewall rule ? that's the only other thing that has been spoken of so I think I need to try that, I'm just not sure how I'm going to accomplish that, as in I have no idea what to choose for the settings, -
What you have suggested worked fine,
Great.
I have connected fine with my iPod Touch, I just can't access anything, Should I try the firewall rule ?
Yes. Stephenw10 posted details in an earlier reply:
@stephenw10:Your rule should be something like:
Protocol: any
Source: any
Destination: any
Port: anyAfter adding the rule you will need to reset firewall states (see web GUI Diagnostics -> States, click on Reset states tab then click Reset States button). Then check you can access the Internet over the WiFi link. (Default configuration for the firewall is LAN can access everything, access through other interfaces is blocked.)
-
Well, It works, after a hard fight, we won, lol,
Thanks to Bob and Steve, You guys were a great help,
Nathan
-
-
Good result, persistence pays off. ;)
I suggested that very open firewall rule for testing. You may want to replace it with a more restrictive rule later.Steve
-
I don't think I'll need to all I am using this for is taking a wired connection and making it wireless, the only thing that is on that network is my iPod, the rest of the house is separate networks and my dad's got it all figured out, so security isn't a big deal for me, well not for the specific project,
Thanks
NathanI'm glad I didn't kick the piece of **** lol
