Re: Trying to get apache to run on two interfaces.. But get errors. Probable doing something wrong? or impossible. Thanks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On 29 Oct 2022, at 08:41, Michael D. Setzer II via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> 
> Was trying to get the apache to run on two interfaces, 
> and thought it was work on both,
> but checked and it wasn't running on either?
> 
> The two networks. One a wired on motherboard 
> connection, and another being a USB wireless 5G
> 
> enp2s0: 
> flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  
> mtu 1500
>        inet 192.168.16.104  netmask 255.255.255.0  
> broadcast 192.168.16.255
> 
> wlp0s18f2u3: 
> flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  
> mtu 1500
>        inet 192.168.24.14  netmask 255.255.255.0  
> broadcast 192.168.24.255
> 
> The error message in messages was.
> Oct 29 17:13:56 setzco setroubleshoot[1438]: SELinux is 
> preventing httpd from name_bind access on the 
> tcp_socket port 8081.

that says the problem is selinux policy. You need to fix that i assume.
I would run with selinux not enforcing to see if that is the only issue.

Barry

> 
> Had two Listen lines in httpd.conf but commented the 
> second one and it is working on that ip/port.
> Listen 192.168.16.104:8081
> #Listen 192.168.24.104:8081
> 
> Have a cable modem, and each port on it gets a different 
> public IP.
> 
> The public IPs of two wireless/wired routers
> xxx.xxx.234.251 (Netgear 2.4/5 newer)
> xxx.xxx.233.11  (BLINK 2.5 older)
> 
> Was trying to get both options working before moving 
> things to the newer router.
> Have a dyndns name setup for each router mapped so 
> accessing the public IP on port 8081 would map to port 
> on machine.
> Has worked fine for many years, and public IP on old 
> router has not changed for many years, though it isn't 
> static?
> 
> Seems ISP blocks many ports on non-static IPs, but port 
> 8081 worked fine and still does.
> 
> So questions: 
> Can apache work with 2 different IPs or can it only listen 
> to one? Is doing it with two Listen lines wrong, is syntax 
> wrong.
> The USB 5G wireless doesn't work with default kernels, 
> had to download git source code, and build modual for 
> each kernel update.
> 
> Regular customer support of ISP doesn't have tech info. 
> Probable need to get ahold of real tech at ISP, and 
> probable get static IPs.
> 
> Use to have a Linux machine that had 9 ethernet ports 
> long ago. One connected to College Backbone, and 8 
> other ports connected to 8 different classrooms.
> Back then the college backbone as 100M and clasroom 
> were 100M as well (long ago). So classrooms ran on 
> private IP blocks for each, and used a squid server that 
> was seeing a 40% cache hit ratio.
> Retired after 36+ years at college. 
> Had another server on backbone that was running all the 
> web and ftp stuff..
> 
> 
> 
> +------------------------------------------------------------+
> Michael D. Setzer II - Computer Science Instructor 
> (Retired)     
> mailto:mikes@xxxxxxxx                            
> mailto:msetzerii@xxxxxxxxx
> Guam - Where America's Day Begins                        
> G4L Disk Imaging Project maintainer 
> http://sourceforge.net/projects/g4l/
> +------------------------------------------------------------+
> 
> 
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux