On 08/21/2018 03:29 PM, Bob Goodwin wrote:
> On 08/21/18 10:53, Gary Hodder wrote:
>> You can temporarily give your lan interface another class C and
>> configure that device to give it a ip in your range.
>> Say your device reset to 192.168.0.1 and your ethernet interface is
>> eth0 you can
>> ifconfig eth0:0 192.168.0.2 netmask 255.255.255.0
>> Config device plugged into your switch to your class C then
>> ifconfig eth0:0 down
>>
>> Gary.
> +
>
> I can do:
> # ifconfig enp2s0:0 192.168.11.1 netmask 255.255.255.0
>
> And it does appear to work:
>
> # ping -c 3 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.301 ms
> 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.280 ms
> 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.310 ms
>
> --- 192.168.1.1 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2062ms
> rtt min/avg/max/mdev = 0.280/0.297/0.310/0.012 ms
>
>
> # ip a shows:
>
> 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
> state UP group default qlen 1000
> link/ether 4c:cc:6a:62:e9:85 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.10/24 brd 192.168.1.255 scope global dynamic enp2s0
> valid_lft 80281sec preferred_lft 80281sec
> inet 192.168.11.1/24 brd 192.168.11.255 scope global enp2s0:0
> valid_lft forever preferred_lft forever
> inet6 fe80::4323:323b:592f:3d9b/64 scope link
>
>
> However: Firefox can’t establish a connection to the server at
> 192.168.11.1
Can you ping anything on the 192.168.11/0 network? I don't think you
have a route for the 192.168.11.0/24 network. While you added an alias
to your NIC (enp2s0:0) and an IP address for that alias (192.168.11.1),
you have not added a route for that network so it's using your default
route (which goes out 192.168.1.1). You'd need to add a route via:
ip route add 192.168.11.0/24 dev enp2s0:0
to force it.
You should also be aware that if the web server you're trying to hit
is on THIS machine, simply adding an alias/IP to the NIC and adding a
route won't work if that network manipulation was done after the web
server was started. The web server typically starts listening on the IP
addresses that are up at the time the webserver starts, and you have to
make sure it uses something like
Apache's "httpd.conf" file:
Listen *:80 OR
Listen 80
Ngnix's "nginx.conf" file:
listen 80;
to make sure it listens on port 80 for ALL of the IPs on the machine.
You can see which IPs the server is listening on by using:
netstat -lpnt OR
ss -lpnt
and looking at the local address parts of the display. If the local
address is "0.0.0.0:<some-port-number>", then it's listening on all
IPs on the machine.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- "Celibacy is not hereditary." -
- -- Guy Goden -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/VVT4KQMB7UHN5YMDBUNUOW6KWZ2KF6OM/
