Re: [Fwbuilder-discussion] How to add a 'host' on the internet?

[Vadim K. <va...@vk...>]

On Sunday, November 2, 2003, at 01:35  PM, Carlo Wood wrote:

> On Sun, Nov 02, 2003 at 12:46:58PM -0800, Vadim Kurland wrote:
>> I'd like to try to reproduce this bug. Could you give me a step by 
>> step
>> scenario?
>
> Ok - I managed to reproduce it... You will be suprised :p
>

indeed, I am surprised. I was able to reproduce it here. It scanned my 
home network, created host objects for computers and a switch, and 
interfaces of the switch got "Policy" for some odd reason just like in 
your case. It seems to add this bogus policy object only for nodes that 
answer to SNMP.

thanks!

I'll file a bug report myself :-)

--vk


> $ fwbuilder
>
> Tools -> Discover Objects
> Next
> Perform network discovery using SNMP
> 'Seed' host: jolan   [this is my firewall, fwbuilder runs on 'ansset']
> Next
> Next
> Next
>
> [scan log:
>
> SNMPCrawler started at Sun Nov  2 22:29:11 2003
> . Seed host: 192.168.2.1
> Processing 192.168.2.1
> ARP table
> Connecting to 192.168.2.1
> Connected...
> Pulling atNetAddress table...
> Pulling atPhysAddress table...
> Learned: 62.195.88.129 at 00:02:4B:16:14:70
> Learned: 192.168.2.2 at 00:01:02:B8:15:CA
> Done fetching ARP table
> Got 2 entries
> Adding 2 hosts to results
> Connecting to 192.168.2.1
> Index of interface addresses.
> interface #1: 127.0.0.1
> interface #2: 192.168.1.2
> interface #4: 192.168.2.1
> interface #3: 62.195.88.134
> Full interfaces info.
> Adding interface #1: 127.0.0.1/255.0.0.0
> Adding interface #2: 192.168.1.2/255.255.255.0
> Adding interface #3: 62.195.88.134/255.255.255.128
> Adding interface #4: 192.168.2.1/255.255.255.0
> Interface #5 has no IP address.
> Done fetching interfaces
> Network 192.168.1.0/255.255.255.0 found.
> Network 62.195.88.128/255.255.255.128 found.
> Network 192.168.2.0/255.255.255.0 found.
> Connecting to 192.168.2.1
> Getting System name
> Getting Description
> Getting Location
> Getting Contact Info
> Done fetching sysinfo
> Routing table
> Connecting to 192.168.2.1
> route: 0.0.0.0/0  gw 62.195.88.129  eth2(Ext)
> route: 127.0.0.0/8  gw 0.0.0.0  sit0
> route: 192.168.1.0/24  gw 0.0.0.0  eth0
> route: 192.168.2.0/24  gw 0.0.0.0  eth1
> route: 62.195.88.128/25  gw 0.0.0.0  eth2(Ext)
> Done fetching routing table
> Network 192.168.1.0/255.255.255.0 found (via direct route).
> Network 192.168.2.0/255.255.255.0 found (via direct route).
> Network 62.195.88.128/255.255.255.128 found (via direct route).
> Adding 3 networks to results
> Removing virtual IPs.
> Resolving names
>   Creating worker thread
>   Creating worker thread
>   Creating worker thread
>   Creating worker thread
>   Creating worker thread
> Trying 62.195.88.129;   2 more in the queue
> Trying 192.168.2.1;   1 more in the queue
> Trying 192.168.2.2;   0 more in the queue
>  Worker thread exiting
>  Worker thread exiting
> Resolved  62.195.88.129: node-d-5881.a2000.nl
>  Worker thread exiting
> Resolved  192.168.2.1: jolan.jolan-alinoe
>  Worker thread exiting
> Resolved  192.168.2.2: ansset.ansset-jolan
>  Worker thread exiting
> Finished.
> SNMPCrawler - done at Sun Nov  2 22:29:11 2003
>
> ]
>
> Next
> Next
> Next
> Finish
>
> [At this point there is a:
>
> User -> Objects -> Hosts -> alinoe.com
>
> with 5 interfaces (there are more hosts, but
> those do not have the bug)
>
> EACH of these interfaces look like:
>
> - eth0			192.168.1.2
>   |- address		192.168.1.2
>   `- Policy
>
> That is: they have all a 'Policy' under the interface.
> When clicking on any of these 'Policy' lines, I get
> the mentioned assertion.
>
> The reason that this happened frequently is because I
> am curious ;).
>
> -- 
> Carlo Wood <ca...@al...>