Re: [IPCop-user] Can't ping IPCop

[Andrew M. <And...@Af...>]

How about trying
  ping ipcop.
Note the dot at the end of the name ipcop!

Regards

AndrewM

Andrew McGlashan
Mobile: 04 2574 1827 Fax: 03 8790 1224

Affinity Vision Australia Pty Ltd ABN 91 099 273 855
www.affinityvision.com.au -- Retail discounts for existing and new
consultancy clients!

----- Original Message -----
From: "Mike Morrett" <fli...@fa...>
To: "User, IPCop" <ipc...@li...>
Sent: Thursday, January 16, 2003 10:23 AM
Subject: [IPCop-user] Can't ping IPCop


My home network.

IP
address
-------
DHCP    PC1 (W2K or BSWare)            ---\
DHCP    PC2 (W2K)                           ----\
DHCP    PC3 (W98se)                        -----> [HUB] -> IPCOP -> Modem
-> Al Gore's Internet
Static  SRV (RH 7.3 running Samba)     ----/
Static  HP4MV Printer w/JetDirect card ---/

The address for IPCop (v1.2) is 192.168.1.1

I can not "ping ipcop", but "nslookup ipcop" does work.

C:\TEMP>ping ipcop
Unknown host ipcop.

C:\TEMP>nslookup
Default Server:  ipcop
Address:  192.168.1.1

> ipcop
Server:  ipcop
Address:  192.168.1.1

*** No address (A) records available for ipcop
> exit

Why does the name of the IPCop firewall box not get entered into its own
DNS? Is there a way round this?

IPCop is using DNSMASQ and according to
http://thekelleys.org.uk/dnsmasq/doc.html ...

"Dnsmasq will serve names from the /etc/hosts file on the firewall
machine: If the names of local machines are there, then they can all be
addressed without having to maintain /etc/hosts on each machine."

Well, "192.168.1.1 ipcop" is in the /etc/hosts file.

Also, "Dnsmasq caches internet addresses (A records and AAAA records) and
address-to-name mappings (PTR records), reducing the load..."

So, why does nslookup work, but ping does not?

I thought the advantage of DHCP was to automagically assign the IP
Address and DNS Server, and not have to edit the "hosts" file??

C:\TEMP>ipconfig /all

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : rusty
        Primary DNS Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : mydomain.org

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : mydomain.org
        Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
        Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
        DHCP Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.12
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.1.1
        Lease Obtained. . . . . . . . . . : Wednesday, January 15, 2003
        3:57:24 PM
        Lease Expires . . . . . . . . . . : Wednesday, January 22, 2003
        3:57:24 PM
--
cat /dev/coffee | /dev/cup | /dev/mouth | /dev/nose > /dev/keyboard


-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate
is essential in establishing user confidence by providing assurance of
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
IPCop-user mailing list
IPC...@li...
https://lists.sourceforge.net/lists/listinfo/ipcop-user