This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] troubleshooting a new probe configuration
- Previous message (by thread): [atlas] BOOTP/DHCP on a probe with static network configuration
- Next message (by thread): [atlas] Atlas probe - virtual appliance?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Allison, Jared M
jared.allison at verizon.com
Tue Jun 18 19:19:54 CEST 2013
Hello, I just got a new RIPE Atlas probe at NANOG in New Orleans, US and am trying to get it up and running. I configured a port for it on my firewall with IPv4 DHCP service and DNS. The firewall rules should permit just about all traffic. I confirmed that the port was operational by connecting a computer to it and could browse to external websites, etc. When I connect the probe to this port, I can see in the logs that it gets an IPv4 DHCP address, but doesn't seem to do anything else. The power light on the probe is solid, the second light appears to be off, and the third and fourth lights are blinking. It's been this way through several power-cycles and several days. Any idea what error condition this indicates? Thanks, -jared --- Jared Allison jared.allison at verizon.com
- Previous message (by thread): [atlas] BOOTP/DHCP on a probe with static network configuration
- Next message (by thread): [atlas] Atlas probe - virtual appliance?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]