Thank you indeed Chris I understand the modem is largely bridging, as I think you are suggesting, given the Internet IP address appears on the pfSense WAN NIC.
This is the sort of approach I was looking for. Given my ISP is declared on my email address here I won't comment about New Zealand ISP's here. I might however point out that I have not disagreed with you in any way. My presumption is that it is either coming from pfSense or indeed, as you suggest, the ISP. There are some TiVo's on the LAN here that also are intermittently having issues downloading data for no apparent reason when everything is connected, also using a proxy. (VOIP and Skype also running) I'll install 1.2b1 on another CF card and see what transpires. I am pretty sure the unplug / plug in has been tried in the past, without success, will try again to be sure. Kind regards David Hingston. ----- Original Message ----- From: "Chris Buechler" <[EMAIL PROTECTED]> To: <support@pfsense.com> Sent: Tuesday, June 05, 2007 2:10 PM Subject: Re: [pfSense Support] pfSense Hanging... First, if you're not running 1.2b1, you should try it. I'm going to assume cable service in .nz works the same as it does in .us, though that could be a wildly incorrect assumption. If it does, your modem does nothing but bridge between your cable provider's network and whatever you have plugged into the Ethernet port. There is no connection like PPPoE, no username or password, etc. As long as you have sync, it's good. If your cable Internet service uses the DOCSIS standard, it's the same as here, and as I describe. Next time this happens, SSH in and run 'tcpdump -i fxp0 -s 1500 -w capture.pcap' replacing fxp0 with whatever your WAN NIC is. Then run a constant ping to your WAN gateway from your LAN, try to access websites, etc. Wait about 5 minutes and ctrl-c to break out of the tcpdump. Then you can use the webGUI to download that 'capture.pcap' file, or scp it off to another host. Send it to me via email and I should be able to see what's happening on the wire. At this point, without that, it's anybody's guess as to what's happening. If your cable company is twice as competent as our local cable company here, they'd still be completely inept. In other words, I wouldn't rule out a weird network issue on their end. Scott and I spent countless hours tracking down a really screwy issue that turned out to be something they screwed up on their network, when they claimed repeatedly they hadn't changed anything and it was a firewall problem. One other thing to try after getting the tcpdump - if you unplug the WAN NIC from the cable modem and plug it back in, without rebooting, does that bring it up? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
