this does seem to be the accepted work around , but seems like it really sucks to me. here is what i would like to try,, getting uverse in a few days , ask the rep if i can bridge and was told yes. then got home as search and saw you cant. it seem like the ip pass would be dubble NAting 1. according to the book from moto bride mode exist and works http://www.ron-berman.com/wp-content/uploads/2011/11/nvg510manual.pdf "This guide describes the wide variety of features and functionality of the Motorola Gateway, when used in Router mode. The Motorola Gateway may also be delivered in Bridge mode. In Bridge mode, the Gateway acts as a pass-through device and allows the workstations on your LAN to have public addresses directly on the Internet" there is tel net   we need to poke that, if not maby we can find the OG firmware from moto 2 there is the moto 2247-N8 ADSL2 802.11n Wi-Fi Gateway this looks to be very close to the NVG510 sans the phone spliter i wonder if the 2247 firmware can be loaded on the nvg510 to allow bridge mode. the command line looks to be the same. does anyone have a 2247 so that we can compare chipsets.

Pretty much every network in the world has a good deal of broadcast noise. Until you get up to hundreds or thousands of hosts it's not enough to impact anything short of a host gone nuts spewing huge amounts of broadcast traffic (thousands of pps, which I've only seen happen a couple times that can be classified as just "host gone nuts", it's very rare). That's the reason you generally don't want more than a /24 per broadcast domain, more than 254 active devices on a network and you may have enough broadcast noise that it becomes an issue (though usually not until you get to several times that many hosts).

I've been looking into the sweeping after bootup issue. It seems that when a startup service fails, it keeps the leds sweeping. I had a look at the beastie while it was starting up over the serial port, and noticed that I was having cron die immediately after starting up. I looked into the crontab. There was an entry for squid that didn't get removed when I uninstalled the package. After removing it, it seems to have cleared up the problem.

Nice. Comprehensive set of screenshots there!  :) Steve

Time To Crack: 1306628104 centuries Total Passwords in Pattern: 4 Septillion

on firewall -> nat -> outbound nat change mode to manual and add mapping rule with: interface: outbound interface you want to force the ip(wan2 for example) source: smtp server ip address source port: any destination: any destination port: any or 25 nat address: interface address or virtual ip

it is crazy. At the morning, rrd catches some data…. [image: status_rrd_graph_img.png] [image: status_rrd_graph_img.png_thumb]

Finally, I got it work. My network is behind pfsense and untangle where untangle act as bridge. I did some research on untangle forum and the problem was the antivirus. Untangle scan every single file that I downloaded through IDM. Because of that scanning process, it prohibit me to have multiple connection. What I did, I just simply turned off the antivirus and now I get no problem with my IDM. Thanks for your answer guys, I really appreciate it.

If you had non-functional DNS on the host and tried doing those lookups at that point, at times PHP has a nasty habit of hanging onto failed responses and refusing to issue new queries. Running 'killall php' at the console should resolve, or at worst, reboot.

The RRD traffic graphs are generated from PF counters. If you're not filtering on bridge member interfaces, rather only the bridge itself, the graphs of the member interfaces will be blank because there is no data for them.

For Windows you can use the shutdown.exe tool that was on IIRC the Win2K resource kit and is freely downloadable from MS. It also works with all newer versions of Windows. You could also pkg_add samba on the firewall and use a "net rpc" command to power down from there. Probably easier to do it from a Windows server if you have one with shutdown.exe.

after doing some further research i found out that the wrong password attemps happen near the time of the periodic reset. manual reconnects do not cause this behaviour. i will now try to capture a periodic rest with wireshark.

arnoldg, personally i think the only real secure way to do this is using VPN.  Follow the instructions on this video and it will work nicely.  This is the video that i used way back when i set mine up, works a charm: http://www.youtube.com/watch?v=odjviG-KDq8

Killing from the console/ssh is fine if it's going nuts. I've seen rate do that before myself, but not in a repeatable way. The usual way I see it is if I click on the traffic graph page accidentally and then navigate away from it really fast, but even that's not perfectly repeatable.

@miles267: Thanks - that worked.  Is a pass phrase necessary for the key? Well, technically it's not required, but it's a good practice security-wise to keep keys password protected. If you do a lot of logins/logouts throughout the day, then you could use Pagent (in case of putty).

macraig you can see in console or system.log Watchdog timeouts on network interfaces ? I have a similar problem using Intel PRO 1000 MT Dual port PCI after minutes system hang

Stephen, thanks SO much for your patience and help.  In the end, I was able to restore libgcrypt from the FreeBSD archive site and install the appropriate version of freeipmi.  This restored both my bmc-watchdog functionality as well as added the ipmi-sensors function.  I too was able to add the IPMI Sensor entry to pfsense Diagnostics drop-down so I can access from within the web UI.  Much appreciated.

I have just tried this and It works, thanks to everyone who contributed. I set this up on my BT UK service. I have a business account and have used the supplied username and password they email when you sign up. I think the following is default for domestic installs on BT, homehub@btinternet.com as the username and no password (set to 1234). I should add this is a FTTC install and I replaced the BThub3 with my pfsense box

remember that some ISP's block ports under 1024 to "SCREW" their customers …. Fixed that for ya!    ;D