Issue Accessing Emulab Website from Specific IP Address

[Andria Trigeorgi]

I have an issue: I am unable to access the Emulab website from a specific IP address.

Thank you in advance, 

Andria 

username: andria

[Eric Eide]

Andria Trigeorgi <an.tri...@gmail.com> writes:

> I have an issue: I am unable to access the Emulab website from a specific IP
> address.

Hi. You'll need to provide more information in order for us to try to
investigate this issue. I.e.,

* what source IP
* what destination IP
* when do you notice the problem
* what if anything you have done to investigate the issue (e.g., traceroute)

Thanks ---

Eric.

--
-------------------------------------------------------------------------------
Eric Eide <ee...@cs.utah.edu> . University of Utah Kahlert School of Computing
https://www.cs.utah.edu/~eeide/ . +1 801-585-5512 . Salt Lake City, Utah, USA

[Andria Trigeorgi]

source IP: 83.168.4.85

destination IP:

% nslookup emulab.net

Server: 10.200.200.1

Address: 10.200.200.1#53

Non-authoritative answer:

Name: emulab.net

Address: 155.98.32.70

when do you notice the problem: 4 Dec

andriatrigeorgi@Andrias-MacBook-Pro-2 src % traceroute emulab.net 

traceroute to emulab.net (155.98.32.70), 64 hops max, 52 byte packets

 1  nic.algolysis.arpa (10.200.200.1)  22.174 ms  3.027 ms  4.134 ms

 2  192.168.219.247 (192.168.219.247)  5.671 ms  4.498 ms  4.318 ms

 3  hu0-3-0-8.400-iag1.lat.cyta-ip.net (195.14.136.128)  5.097 ms  4.345 ms  4.570 ms

 4  be19.4-icr1.lat.cyta-ip.net (195.14.136.234)  6.499 ms

    be14.4-icr1.lyk.cyta-ip.net (195.14.136.244)  6.114 ms

    be19.4-icr1.lat.cyta-ip.net (195.14.136.234)  6.351 ms

 5  be18.4-ipr1.lat.cyta-ip.net (195.14.136.48)  5.651 ms

    be16.4-ipr1.lat.cyta-ip.net (195.14.136.241)  6.087 ms  5.266 ms

 6  * 2-1-c25-1.ear1.marseille3.level3.net (212.133.120.245)  47.986 ms  42.573 ms

 7  * * *

 8  ae15.540.dcx4-edge-01.sp.lumen.tech (4.68.110.182)  136.205 ms  131.765 ms  134.158 ms

 9  slc2-edge-05.inet.qwest.net (67.14.134.70)  178.760 ms  175.985 ms  178.182 ms

10  67.128.147.214 (67.128.147.214)  179.193 ms  178.820 ms  179.430 ms

11  ddc-p-a-140-int.uen.net (140.197.251.34)  198.382 ms  197.718 ms  199.792 ms

12  ebc-pep-b-179-int.uen.net (140.197.252.76)  196.520 ms  197.864 ms  196.572 ms

13  ebc-pep-a-178-int.uen.net (140.197.252.84)  195.926 ms  195.417 ms  196.503 ms

14  140.197.246.177 (140.197.246.177)  196.040 ms  194.966 ms  194.732 ms

15  * * *

16  * * *

17  155.98.127.82 (155.98.127.82)  199.867 ms  196.020 ms  196.515 ms

18  * * *

--
You received this message because you are subscribed to the Google Groups "emulab-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emulab-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/emulab-users/m1jzceukov.fsf%40noir.uconnect.utah.edu.

[Leigh Stoller]

> source IP: 83.168.4.85
> destination IP:
> % nslookup emulab.net
> Server: 10.200.200.1
> Address: 10.200.200.1#53
>
> Non-authoritative answer:
> Name: emulab.net
> Address: 155.98.32.70
> when do you notice the problem: 4 Dec

Thanks for the info. What was the ssh command you were using?
Please provide the output of `ssh -v` as well as the actual
command (but be sure not to include passwords)

Thanks
Leigh

[Andria Trigeorgi]

the connection can not be established 

% ssh -v <username>@emulab.net

OpenSSH_9.4p1, LibreSSL 3.3.6

debug1: Reading configuration data /Users/<username>/.ssh/config

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files

debug1: /etc/ssh/ssh_config line 54: Applying options for *

debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling

debug1: Connecting to emulab.net port 22.

--
You received this message because you are subscribed to the Google Groups "emulab-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emulab-users...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/emulab-users/FBD34C9F-CC95-4C3A-B918-8AAEF8596641%40gmail.com.

[Leigh Stoller]

> % ssh -v <username>@emulab.net
> OpenSSH_9.4p1, LibreSSL 3.3.6
> debug1: Reading configuration data /Users/<username>/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files
> debug1: /etc/ssh/ssh_config line 54: Applying options for *
> debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
> debug1: Connecting to emulab.net port 22.

So you cannot ssh into @emulab.net. You can only ssh into nodes
in your experiments. If you have an experiment running, look on
the list tab for the the proper ssh commands to use.

So what has happened, is that the failed ssh attempts put your IP
on our firewall block list. I will take your IP off, check back in
a couple of hours (the firewall updates its block lists every
two hours).

Leigh

[Andria Trigeorgi]

Thank you very much for your help!

> On 6 Dec 2024, at 6:47 PM, Leigh Stoller <lbst...@gmail.com> wrote:
>
> 

> To view this discussion visit https://groups.google.com/d/msgid/emulab-users/0ED5B6DA-06B1-4BF5-BD79-875BB477111B%40gmail.com.