Tag Info

Hot answers tagged

7

You must create a default vhost configuration file and include it before of others. For example you can save this default config to /etc/nginx/conf/default.conf: server { listen 80 default_server; return 444; } And include it in nginx.conf: http { .... include "/etc/nginx/conf/default.conf"; include "/etc/nginx/vhosts/*.conf"; } Be sure ...


3

No, you can't do this with DNS, IPtables or the hosts file. You'd need to point those domains to a proxy, or something that has knowledge of what you want done, which will in turn re-direct the clients to the "right" place.


2

To find out how it works try: ip route get ADDRESS [ from ADDRESS iif STRING ] [ oif STRING ] [ tos TOS ] [ mark NUMBER ] it will tell you where/how packet with such parameters gets routed


2

In your situation I would simply use the ASA as a DHCP that hands out its internal IP as the DNS server, use DNS proxy to the tunnel DNS and have several public DNS's listed in the config. EG. (these commands work on c3900 equipment ios15.1, you may have to make changes to be compatible to the ASA software) service dhcp ip domain nameserver "tunnel dns" ip ...


2

You will only get "failed login attempt" messages on accounts that you're actually logging into. Since SSH scanners typically try some common names of people, and also known system accounts like 'root', what that message tells me is that you're logging in as root directly over SSH. You should not do this. The first thing to do is create a regular user ...


2

Unicast flooding in and of itself isn't abnormal. A certain level of unicast flooding is going to happen as MAC addresses age out of the CAM (MAC address) tables on the switches. If you have excessive unicast flooding then I might posit that you have a problem with the Spanning Tree Topology of your switching infrastructure. The first thing I would suggest ...


1

Maybe I'm missing something from your setup but here's what I think is the issue. If the Modem is connected to one of the switch as pictured in your design via an access port, then that modem needs to have routes for all of your VLAN pointing back to your OpenBSD firewall. That would explain why the Modem seems to only "see" the Firewall since it's layer 2 ...


1

Changing metrics sure is better solution than deleting any of the default routes. It's also robust, since on disconnect you'd still be able to access the internet via the corporate LAN without modifications. However, since you have dynamic IP on this interface, it's frustrating to manually find the changing gateway IP every day. Therefore, you could use ...


1

How did you setup your assets path in this case? My assets path is <host>/assets/<asset_name>.css but the correct path is: <host>/<app_name>/assets/<asset_name>.css My config is mostly the same as the one above. upstream app1 { # Path to Unicorn SOCK file, as defined previously server ...


1

For each VLAN, I needed a default gateway subinterface


1

I found some very strange things going on with IAX2 and PFsense. I've got the latest PFsense (2.2.1 Mar 13 2015) and this has been consistent with all my experiences prior, as well: PFsense appears to be NOT applying NAT rules to IAX2 packets. If I set up a packet dump on pppoe0 (going to my DSL carrier) I see packets coming from 192.168.1.168 port 4569, ...


1

You just have to add a server block in your nginx configuration. The following code will return a 403 error to users accessing your server through the IP : server { listen 80; # IPv4 listen [::]:80; # IPv6 (if enabled) server_name ""; # no domain name return 403; }



Only top voted, non community-wiki answers of a minimum length are eligible