So, you view your graph (consisting of your sites and connections) as an undirected graph. If you use the data model from Chris's answer, where each connection appears exactly once and in only one direction, the first step will need to be to union (all) the connections table with its "reverse", to get all the connections in both directions.
I also assume that you have no interest in routes that visit the same site more than once (something like A,B,C,A,E,F,J - the trip from A to itself passing through B and C, only to then go to J via E and F, is not needed). So, you must pay attention to cycles - either in the graph itself, or caused by the bi-directional connections. The bi-directional connections can by themselves cause cycles: A,B,A,C,D,E,F,J, even if the undirected graph has no cycles.
In a CONNECT BY query, cycles are detected based on the columns that appear with the operator PRIOR in the CONNECT BY clause. In the query below, we use column CONNECTED_SITE_ID in that way; we will avoid all cycles, except perhaps returning to the origin (since the origin is not a CONNECTED_SITE_ID when we start) - so we need to pay attention to that.
Two modifications to Chris's query are the simpler way to build the paths in SELECT, and the condition PRIOR CONNECTED_SITE_ID != :DESTINATION. The latter is a trivial optimization: we should not continue the depth-first traversal after we already reached the desired destination.
I also show the origin and destination as bind variables.
Be prepared to get horrible performance on anything of non-trivial size; if this is a homework problem, the solution might be accepted, but if you want to use this to find flights from Beijing to Las Vegas in a production environment, your CPU will melt down. What will work is to add a condition on maximum number of stopovers - something like 2 or 3 is probably reasonable.
select :origin || sys_connect_by_path(connected_site_id, ',') as paths
from ( select site_id, connected_site_id from connections union all
select connected_site_id, site_id from connections )
where connected_site_id = :destination
start with site_id = :origin
connect by nocycle site_id = prior connected_site_id
and connected_site_id != :origin
and prior connected_site_id != :destination
;