Considering,
i may have switches from different vendors in my network?
Also, how to ensure the target MAC will always exist in the MAC table of the switch
l2 traceroute is limited to a l3 domain. It is limited to an L2 broadcast domain. You cannot go across the subnet.
Related
sorry my poor title but I don't know how to express my intention.
In ipv4 there are 2**32 addresses right?
and then if I send 1024 packets per second I could check all the devices of the internet in 1165 hours to create map of the internet. with it I want to make a topology of the internet
it's not that bad, if I go with multiple computers like raspberry pie it would be more faster.
if it's not me but somewhat organization or people and they have enough time, it could even scanning all the ports of all the devices of the internet..!
is my thought a daydream? or somebody already did it? please let me know! I'm curious
If you are interested in the actual physical location of an IP address, then there are many sources compiled already available, like the one here for free. Some are more accurate(commercial ones) than others.
If you just want to know if an IP address is alive or what services are available then you are out of luck as many of these "public" IP addresses are only accessible from whitelisted sources and/or heavily protected from folks like you trying to sniff around for profiling reasons.
If you would like to map out the topology of the Internet, you could get a view of the Autonomous Systems (collection of IP network addresses typically owned by ISPs or larger corporations) by looking at publicly accessible BGP looking glasses. BGP is the protocol that controls the routing of packets on the Internet. Please note that this is very dynamic and changes frequently due to the dynamic nature of path selection algorythms.
I have a topology setup in GNS3 running a number of virtual machines (pictured below.) R1, R2, and R3 are routers (built in Ubuntu) that I am running tests on. 'Test' is another Ubuntu virtual machine that is controlling my tests.
I would like to be able to ping from the interface on 'Test' with address 10.0.4.3, through R2, then through R1, then back to 'Test' at the interface with IP 10.0.5.2
Ideally I would like to be able to treat each network interface on 'Test' as a separate logical computer, so I could simply say ping 10.0.5.2 from 10.0.4.3 and let the routing protocols forward the message through the route of their choosing.
The tests are automated, so splitting 'Test' into four separate virtual machines would be less than ideal.
Any ideas?
Well, in this particular scenario, i think the solution for what you want would be to virtualize machines over the "test" machine, with this approach each machine would be in a different subnet. BUT, i'm not sure how better it would be when comparing to multiple "test" machines...
Another option, since it's a simple scenario and you only showed interest in testing routing protocols is to build this scenario in a simulator called Packet Tracer, by Cisco. In this scenario, you would still need more "test" machines but you wouldn't have to worry about you computer processor. The downside is that you'd need to use Cisco devices instead of Linux Machines to configure your routing topology.
Arthur Passos.
I need an algorithm to find if there is a windows domain (AD service) set up in the network I am currently connected to. This should work for any network (a WiFi in McDonald's or a corporate network) meaning I do not know the name of the domain I am looking for (if there is any).
All I have ever found were ways to check for the domain my computer is in. That is not what I want.
I can perform simple queries (DNS, ...) and this algorithm shall work from any operating system (meaning no readings from windows registry).
Any ideas?
Thanks.
To get a DomainConntroller you must get the "domain" of the network first. And this can not be done, as far as I found, just by DNS reqests.
I am trying to create a setup for testing network equipment, and would like to use multiple (3) NICs in a single PC to produce traffic through an external device, i.e. a network switch. From one interface to another.
All of the tests are for IPv6 and ethernet. All NICs have link local and global IPv6 addresses with the same network/subnet prefix.
Atm. all packets are routed internally and never use the physical wire.
I see a lot of threads solving the problem for IPv4 using the net.ipv4.conf.all.accept_local parameter together with some routing table fixes. But I can't find a solution for IPv6.
Anyone know of a solution?
I know that the MsNLB can be configured to user mulitcast with IGMP. However, if the switch does not support IGMP what are the options?
If you can find an old "dumb" hub, you can run the node NIC's through it, or if your switch is managable you can set the ports up so that they do not remember the MAC address to IP address mappings.
I will say that I have had horrible experience with WLBS (the 2003+ version of NLB) in regards to port flooding. We have an existing load balanced system where we have the load balanced NIC's going into a VLAN to keep the traffic separate and we've turned off the MAC address to IP mapping in order to reduce the problem. We are migrating the load balancing off of WLBS; however, due to the reliability of this configuration.