*NEWB* After Install it won't boot !
-
Bob: I have started to use PuTTY as WinSCP could not connect properly, about the ifconfig | grep ral do you need me to do that ?
The error about PuTTY was in Windows, you had said to include detail so I was trying to get it again,
Thanks.
Linksys wmp54g is the wireless card,
3.0.1-RELEASE(i386) is the build I believe"3.0.1" probably should be "2.0.1"
From there I can use the console so I think it was when I messed with the LAN interface, I was using WAN to connect, Well I have done everything you have said, but I got a different message
I presume "you" means Steve since my instructions didn't involve messing with the LAN interface.
on the console it's telling me : ral0: need multicast update callback x2
Don't worry about that message.
EDIT : I found the type field in general configuration and set it to DHCP
Why set the type to DHCP?
then on the console I saw the "ral0: need multicast update callback" again, then a crap load of the weird text that no one can understand then the system rebooted,
I suspect the "weird text" was a crash report. Crash reports can be deciphered by suitably skilled people.
EDIT : It now says "ral0: device timeout" and keeps sending the message
What message - "ral0: device timeout"? "ral0: need multicast update callback"? something else?
EDIT : I can not connect to it again, I'm sorry, I'm gonna smash this piece of **** soon if I can't get it to work
I understand your sense of frustration. However attempting to relieve the frustration in that way will likely only add to the frustration.
I presume you didn't follow my suggestion of keeping the pfSense LAN interface tied to a "wired" interface so you could continue to access the web GUI while you tinkered with the wireless interface. Correct?
I have a device supported by the ral driver in my test pfSense. I have never needed to activate it. I have just attempted to do so. The console contains a number of additional reports of
ral0: only 1 vap supported
I have actually managed to configure two APs on the interface (presumably one "real" AP and one Virtual AP) and seen the two corresponding SSIDs recognized on my laptop. This pfSense box is running a snapshot build of pfSense 2.1. Unfortunately there have been reports that recent snapshot builds of pfSense 2.1 are broken so I suggest you stick with your current software, at least for the time being. Your report of what I suspect was a crash report leads me to suspect you might have encountered a bug in the ral driver in pfSense 2.0.1. pfSense 2.1 (not yet officially released) uses more up to date device drivers but there have been problems in recent snapshot builds.
It is probably confusing being new to pfSense and getting different suggestions from me and the very capable stephenw10. I certainly find it difficult to guess what you have done to the system to get where you are.
-
It is probably confusing being new to pfSense and getting different suggestions
I agree. I'll hold back unless I see something obvious. :)
Steve
-
Bob, I do mean it to be 2.0.1 not 3.0.1, The part where I said "I have done everything you said was to you,
@wallabybob: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?
Edit: A couple of further bits of information might be useful:
1. What build of pfSense are you using? (Its on the home page of your pfSense box.)
2. What is the brand and model of your wireless card?I did follow that, I had the cards all setup asyou wrote there, but I lost connection still, I'm not sure if I am doing something wrong, it could be me just not seeing some obvious setting that I might have to change but I'll try it again and add results, here:, Well I didn't have to do it all again, I got access after 2 or 3 reboots, I recorded the output of the screen, It doesn't look like much but I thought it would help place why the errors are occurring,http://www.youtube.com/watch?v=RRwgjpBlnXY&feature=youtu.be, When I got in to the GUI the first thing I was confronted with was a crash report, so Ill paste that in here now,http://www.mediafire.com/view/?4wao8amophe5oo5
-
http://www.mediafire.com/view/?4wao8amophe5oo5 is not very informative: All it shows me is an an almost blank page with "Sheet1" near the top, "Page 1" near the bottom and something like "ypC" below "Sheet1".
I get the impression your system might be crashing soon after you enable the WiFi interface. Does that seem to fit what you are seeing?
If you still have the crash report file you could paste it into a reply or attach it to a reply by clicking on the Additional Options link below the textbox in which you compose a forum post.
The report at http://forum.pfsense.org/index.php/topic,54979.0.html suggests the problems with the snapshot builds of pfSense 2.1 dated 23-Oct-2012 are OK so I suggest you try one of those. Ask if you are not sure what to do.
-
I need to retract my earlier report which suggested I had two APs concurrently active on ral0. My laptop has for some time reported only one of the two SSIDs I configured on ral0. I suspect ral0 transmitted one briefly and that was superseded by the other and my laptop reported both because it hadn't yet timed out the first.
-
The link I gave was supposed to have the crash report in it, I don't know why it's not working, I put it there because It could not be pasted here, It was simply to long, also the system crashes when I change the Type, in the Interface Configuration. I think I got the "crashreport.txt" attached, I should have done that in the first place, I now have the 2.1 version, It was a pain in the arse to find but I got it so I'll try that, I think burning this stupid DVD is the most time consuming part for me, always takes a while, oh well.
Results,
Well I'll be damned, I can see the network on my iPod but I cannot connect to it, It simply says "Unable to join the network "Test""
I am also getting the "ral0: device timeout" message on the console which is the reason I can't connect I presume,
It appears my crash report file is about 279KB to big, Do you really need to see it ? I could find a way but if you don't want to see it, I won't bother with it.
-
Well I'm not sure what has changed, I haven't changed a thing but I can nolonger see the network,
-
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,
