How Do I Surf To My Server?
Norberto Meijome
freebsd at meijome.net
Mon Feb 19 23:32:06 UTC 2007
On Mon, 19 Feb 2007 07:26:07 -0800 (PST)
Drew Jenkins <drewjenkinsjr at yahoo.com> wrote:
> Yes, that is a start. I added the domain "mercury.com" (a site I never visit)
> and pointed it to 192.168.1.255, the IP address given from the above. I also
192.168.1.255 doesn't look right. in your server, run ifconfig and determine
the IP from *that* information.
For example, on my laptop:
[betom at ayiin] [Tue Feb 20 10:29:47 2007]
~
$ ifconfig
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
inet 192.168.2.129 netmask 0xffffff00 broadcast 192.168.2.255
ether 00:16:36:29:e1:36
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
the IP assigned to my network card (bge0) is 192.168.2.129 , with a netmask of
255.255.255.0 (0xffffff00 ), and a broadcast of 192.168.2.255.
The only thing you need to access your server from your workstation, if they
are in the same LAN (and subnet...;) ) is the IP address.
> updated pound to use that address, and was able to get the pound daemon
> running. However, I cannot surf to either mercury.com or the IP address. When
> I run this command: nmap localhost I discover that no Web ports are open:
> neither 80, nor 8080 (Zope), whose daemon is running. nmap 192.168.1.255
> doesn't return any ports, stating it seems the host is down. nmap
> 192.168.1.130 the other address returned from your ifconfig command, gives
> the same ports as above. Please advise.
since you are bothering with nmap...why dont you just scan all your IP space
(as in your LAN's IP subnet) and move on? :)
btw, you DO have apache running on your server, right?
Beto
_________________________
{Beto|Norberto|Numard} Meijome
It is better to remain silent and be thought a fool, than to speak, and remove
all doubt.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
More information about the freebsd-questions
mailing list