On 7/11/08, Lanny Marcus <lmmailinglists@xxxxxxxxx> wrote:
> On 7/11/08, William L. Maltby <CentOS4Bill@xxxxxxxxxxxx> wrote:
> <snip>
>>> I cannot dig +trace from my Desktop, as me or as root and I also
>>> cannot dig +trace from the ipcop box as of this time.
>>
>> Must be either firewall on your desktop or IPCop has some blocked
>> resources. Try to dig something from your desktop that is on your local
>> lan. Your IPCop box(es) should make good targets *if* nothing blocks the
>> needed responses.
>>
>> If you can get dig +trace to any other box on the lan, with trace
>> information shown, that means your desktop should be fine.
I disabled the Firewall in my Desktop. I can dig to my daughters box,
but I cannot dig +trace to it. Same results as with the Firewall in my
Desktop enabled.
I have SELinux running in Permissive Mode in my box and am not
receiving Warnings, so I do not believe that is causing the problem. I
will look at the web interface for the IPCop box, to see if I can find
something I think might cause this problem.
[lanny@dell2400 ~]$ dig dell1602.homelan
; <<>> DiG 9.3.4-P1 <<>> dell1602.homelan
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28804
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;dell1602.homelan. IN A
;; ANSWER SECTION:
dell1602.homelan. 0 IN A 192.168.10.57
;; Query time: 2 msec
;; SERVER: 192.168.10.1#53(192.168.10.1)
;; WHEN: Fri Jul 11 16:35:11 2008
;; MSG SIZE rcvd: 50
[lanny@dell2400 ~]$ dig +trace dell1602.homelan
; <<>> DiG 9.3.4-P1 <<>> +trace dell1602.homelan
;; global options: printcmd
;; connection timed out; no servers could be reached
[lanny@dell2400 ~]$ dig dell1602.homelan
; <<>> DiG 9.3.4-P1 <<>> dell1602.homelan
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55631
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;dell1602.homelan. IN A
;; ANSWER SECTION:
dell1602.homelan. 0 IN A 192.168.10.57
;; Query time: 2 msec
;; SERVER: 192.168.10.1#53(192.168.10.1)
;; WHEN: Fri Jul 11 16:36:38 2008
;; MSG SIZE rcvd: 50
[lanny@dell2400 ~]$ dig +trace dell1602.homelan
; <<>> DiG 9.3.4-P1 <<>> +trace dell1602.homelan
;; global options: printcmd
;; connection timed out; no servers could be reached
[lanny@dell2400 ~]$
I then Disabled the Firewall on my daughters box:
[lanny@dell2400 ~]$ dig +trace dell1602.homelan
; <<>> DiG 9.3.4-P1 <<>> +trace dell1602.homelan
;; global options: printcmd
. 0 IN A 192.168.1.1
;; Received 33 bytes from 192.168.10.1#53(192.168.10.1) in 2 ms
[lanny@dell2400 ~]$
That is the FIRST time I have been able to use the dig +trace
successfully! :-)
The Firewall is off in my Desktop and also in my Daughter's Desktop.
[lanny@dell2400 ~]$ dig +trace gmail.com
; <<>> DiG 9.3.4-P1 <<>> +trace gmail.com
;; global options: printcmd
. 0 IN A 192.168.1.1
;; Received 33 bytes from 192.168.10.1#53(192.168.10.1) in 2 ms
[lanny@dell2400 ~]$
The dig +trace to gmail.com does not look at all correct to me, but I
only know about 1% of what I would like to know about Linux or
Networking.
Probably that is caused by settings in the IPCop box?
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
