Usb_modeswitch is a Linux utility. u3g is the bsd equivalent, though it doesn't support as many modems.
If you are seeing cua0 when you plug in the modem then it is correctly switched to modem type device. Try sending it some AT commands and see what happens. pfSense has a program for talking to modems terminal style, like minicom, but for the life of me I can't remember what it's called!  ::)

Steve

Edit: Found it: tip

Username: rcfa

Strange, because the system seems to find me, it sends me the password reset link just fine, when I give it my e-mail address, which should be the same that's used to send notifications when forum threads are updated. I can PM that e-mail address to you if that's any help, just don't want to post it where spam bots can harvest it…

Almost looks like I have a zombie account, that's visible to some parts of the software, but not to others.

??? ???
I also encountered the same problem! And ./update_git_repos.sh update the operating normally.

And confirmed the tools directory of the file for the latest file

cat bsdinstaller-supfile

*default host=cvs.bsdinstaller.org
*default base=.
*default tag=PRODUCTION_2_1
*default release=cvs
*default delete use-rel-suffix
installer

there an error TAG?

@stephenw10:

Looks like you're on a steep learning curve! But all learning is good.  :)

You need to be working on the source and not an installed machine.
Have a look here:

http://devwiki.pfsense.org/ReBrandingSupport

Steve

Thanks Steve but problem is in the Source file for example usr/ folder is empty… And yes im a learner and sorry for asking everything cuz im really confused :(

i managed to make iso. most of pptp patch is already implemented in other patches

It was only the disk full. Creation of dev-iso worked fine finally. Thanks for your help!

Setting up a builder is covered here:

http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso

As for adding the packages, that's up to you. There are mechanisms in the package system to overlay packages and other such things.

Ok Thank you.
I saw build_nano.sh and build_nano_wrap.sh
The firts amha prepare an image for VGA enable hardware that i did not saw in nano_wrap.sh

I suppose that I have to use nano_wrap for alix pc engines (with only serial console)
or  build_nano use VGA but it is serial console enable ??
Thx U for your help.

Ah okay.

It's added, but I changed ath to if_ath, that what the driver is named ;)
Now cleaning up previous build and then I'm gonna try this.

Hopefully this time something actually goes as planned.

edit: crap, it checks the name of the folder, not name of the module. So yet another attempt…

edit2: It now shows up as separate module, however, it is also still in the kernel...
(Deleted the driver, Atheros card still recognized and shown in list of interfaces.)

I moved back to 7.2 with clean system.
The kernel patch issues are gone but I still can not get clean build.
I will start another thread.

I don't think so, might happen sometime after FreeBSD 9 is released if it happens at all. I think someone said 9 is building clang by default now.

>>> Ports with failures:        0 >>> Building athstats...Done! >>> Building tools/crytpo...Done! ==> End of pfPorts... >>> Operation ./build_pfPorts.sh has ended at Mon Feb 21 21:19:43 EST 2011

All good now. Make sure you do a "portsnap fetch extract" after updating the git repos, or update your ports with csup. Also make sure you have a good and current version of autoconf and autoconf-wrapper installed.

The Developer ISO was discontinued, as none of the developers used it any longer. We all build things in a VM or jail based on the same OS as the pfSense install being worked on, and then move binaries over to the firewall.

Setup a VM for FreeBSD 7.2 and you can probably compile the driver fine there, and move over the resulting .ko file to the firewall.

If you have a driver issue, you're better off trying out 2.0 at this point to see if it behaves any better.

Ok, i managed to add it correctly i think…
It now shows up in the dyndns provider list, and checks return codes correctly. And noip is not fake anymore.

The only problem i had is that here at work we use 200.0.0.0/16 for lan (used as WAN in pfsense), and this ip is not correctly detected as private by is_private_ip(). are we incorrectly using this ip class or is the is_private_ip function wrong?

Sorry if i don't provide a diff against sources, but i'm not a developer i just have basic "change existing code" skills.
I copied back and forth the files using ssh and edited them.

The version the original files come from is 2.0-BETA5 (i386) built on Sun Jan 16 21:23:13 EST 2011:

/etc/inc/dyndns.class
/usr/local/www/services_dyndns.php
/usr/local/www/services_dyndns_edit.php

dyndns.class.txt
services_dyndns.php.txt
services_dyndns_edit.php.txt

You already asked a similar question in the captive portal forum. Please don't cross-post the same question to multiple boards.