On 02/22/03 09:26 AM, Aaron Burke sat at the `puter and typed: > (snip) > They dont block 80 on my box, allthough that might be a config setting > not set in my area.
Ok, mind if I ask you what your network setup looks like? Mine looks like this: xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=3<rxcsum,txcsum> inet6 fe80::2c0:4fff:fe40:d9a%xl0 prefixlen 64 scopeid 0x2 ether 00:c0:4f:40:0d:9a media: Ethernet autoselect (100baseTX <full-duplex>) status: active ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552 faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500 tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492 inet6 fe80::2a0:c9ff:fe74:12a3%tun0 prefixlen 64 scopeid 0x8 inet 184.108.40.206 --> 10.9.76.1 netmask 0xff000000 Opened by PID 56 I think these are the relevant interfaces. I'm not entirely sure if this isn't just a masking problem. Of course that would mean that no network connection would get through, wouldn't it? My system at work had a bad netmask, and any machine outside my subnet had trouble connecting to the webserver there until I fixed it. My /etc/ppp/ppp.conf contains the following: verizon: set server /var/run/internet Hidden set device PPPoE:xl0 set mru 1492 set mtu 1492 set authname hidden set authkey hidden set log Phase set dial set login set ifaddr 10.0.0.1/0 10.0.0.2/0 enable lqr add default HISADDR disable iface-alias iface clear It is possible that some change to my set ifaddr line could help, but I don't know what it should be. Then again, that could be the only right one there. Any pointers? - maybe this will help the originator of this thread as well :) TIA Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ When the weight of the paperwork equals the weight of the plane, the plane will fly. -- Donald Douglas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message