Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

hypervisor and purchased > > > failover public IPv4 IPs routed to that server. > > > > > Of course not! Some host _on_your_subnet_ must be responsible for > > forwarding the packages. And a route has to be set so your machine knows > > where to send the packages

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

On 10/31/23 16:46, Dan Ritter wrote: Mihamina RKTMB wrote: On 10/31/23 01:18, Dan Ritter wrote: Mihamina RKTMB wrote: But isn't there a way to make the Debian installer accept that the gateway is not in the subnet of the set IP address? No. [OVH docs reference omitted] You asked

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

Hi. On Tue, Oct 31, 2023 at 11:13:04AM +0100, Marco M. wrote: > > Maybe you need to help the installer along, and set the default route > > for the machine? Perhaps using an alternate virtual terminal, like > > FN+F5. I believe the command is `route add default gw {IP-ADDRESS} > >

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

Mihamina RKTMB wrote: > > On 10/31/23 01:18, Dan Ritter wrote: > > Mihamina RKTMB wrote: > > > But isn't there a way to make the Debian installer accept that the gateway > > > is not in the subnet of the set IP address? > > No. [OVH docs reference omi

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

be responsible for forwarding the packages. And a route has to be set so your machine knows where to send the packages beyond your local subnet to. That is the gateway. It is just a shortcut to define the default route. What you describe is what happens on home or office network. On datacenter networks

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

addr add $IP/32 dev eth0" - set the traffic to the gateway to go through the NIC: "ip route add $GW dev eth0" - set the default route to go via the gateway: "ip route add default via $GW" As I set the IP address to a /32, the gateway is not (never) in the subnet of

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

Am 31.10.2023 um 08:35:48 Uhr schrieb Henning Follmann: > Of course not! Some host _on_your_subnet_ must be responsible for > forwarding the packages. It is possible to define another specific direct connected route to your router and use that with source addresses that are not on the same

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

ng the packages. And a route has to be set so your machine knows where to send the packages beyond your local subnet to. That is the gateway. It is just a shortcut to define the default route. So the installer is right. -H -- Henning Follmann | hfollm...@itcfollmann.com

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

Am 30.10.2023 um 18:07:20 Uhr schrieb Jeffrey Walton: > It should not matter, if I recall correctly. Anything the machine does > not know how to route goes out on the default interface. That should > be the 0.0.0.0 entry in the routing table. Although, that entry must be there and the via IP

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

t;ip addr add $IP/32 dev eth0" > > - set the traffic to the gateway to go through the NIC: "ip route add $GW > dev eth0" > > - set the default route to go via the gateway: "ip route add default via > $GW" > > As I set the IP address to a /32, th

Re: Debian installer refuses to setup IP address if gateway is no in the same subnet

to /32: "ip addr add $IP/32 dev eth0" > > - set the traffic to the gateway to go through the NIC: "ip route add > $GW dev eth0" > > - set the default route to go via the gateway: "ip route add default via > $GW" > > As I set the IP address to

Debian installer refuses to setup IP address if gateway is no in the same subnet

Hi all, I rent a dedicated server where I installed an hypervisor and purchased failover public IPv4 IPs routed to that server. When configuring the Debian VMs to use those failover IPs, I have to - set the address to /32: "ip addr add $IP/32 dev eth0" - set the traffic to the gat

Re: switch gateway automatically

Timothy M Butterworth wrote: You need a Router with two WAN ports! On a router I would configure two Static Routes one default router for the main DSL and one for the backup DSL that is weighted to a lower priority. This is known as surprisingly Weighted Static Routes. I currently have

Re: switch gateway automatically

Timothy M Butterworth writes: > what are you currently using as a WAN router? You can use Debian as a router! > You can configure two default > Gateway's with the primary using a metric of 600 and the backup with a metric > of 700. This will require two > NICs. For failover it's also possible

Re: switch gateway automatically

On Fri, Mar 10, 2023 at 8:12 PM wrote: > Hello, > > > I have two DSL in family. One is main, another is backup. > > When the main DSL get outage, can debian system choose backup DSL as > gateway and keep internet not disconnected? If so, how to deploy it? > You need a R

switch gateway automatically

the main DSL get outage, can debian system choose backup DSL as gateway and keep internet not disconnected? If so, how to deploy it? Thanks. Yong

Re: ping gateway ok, ping any other local network address fails

of some sort, I guess ... > It seems like trapped into a tunnel toward the gateway/router to get > out, but can't shake hands with a pal next door. If your netmask on both sides of the connection is OK, then the problem is at the Ethernet level. Your previous output showed a /24 on the de

Re: ping gateway ok, ping any other local network address fails

seems like trapped into a tunnel toward the gateway/router to get > out, but can't shake hands with a pal next door. > I first suspected a firewall rule of some sort, but there's none. > > I had to investigate remotely as I can't physically access the machine, > so until I can have another cha

Re: ping gateway ok, ping any other local network address fails

On 09.04.2021 21:37, deloptes wrote: Alexander V. Makartsev wrote: I don't see any reason why your computer could not ping the printer, since you can ping gateway IP and access the Internet from it. I suspect printer's IP address has changed somehow, or it is in powered off state (some

Re: ping gateway ok, ping any other local network address fails

On Vi, 09 apr 21, 11:41:56, rudu wrote: > > I paste here a few commands I passed when remotely connected to the > problematic machine (sorry for the french locale). You can always prepend 'LANG=C.UTF-8' to get the output in English. Kind regards, Andrei --

Re: ping gateway ok, ping any other local network address fails

On 2021-04-09 10:41, rudu wrote: Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine could nevertheless surf the web with no problem ... I paste here a few commands I passed when

Re: ping gateway ok, ping any other local network address fails

Alexander V. Makartsev wrote: > I don't see any reason why your computer could not ping the printer, > since you can ping gateway IP and access the Internet from it. > I suspect printer's IP address has changed somehow, or it is in powered > off state (some printers can power of

Re: ping gateway ok, ping any other local network address fails

ot;192.168.1.20" assigned initially to it? (Ex. Using physical screen and buttons on the printer itself, or it was configured automatically) And they can print all right, so this desktop must have some network misconfiguration of some sort, I guess ... It seems like trapped into a tunnel towar

Re: ping gateway ok, ping any other local network address fails

it on the local network, which every over computer can do. And they can print all right, so this desktop must have some network misconfiguration of some sort, I guess ... It seems like trapped into a tunnel toward the gateway/router to get out, but can't shake hands with a pal next door. I first suspected

Re: ping gateway ok, ping any other local network address fails

On Fri, Apr 09, 2021 at 11:41:56AM +0200, rudu wrote: > Hi, > > First, I tried to understand why a single machine among others couldn't > print on the local printer. > So I tried to ping the printer and it failed. > The machine could nevertheless surf the web with no problem ... > > I paste here

Re: ping gateway ok, ping any other local network address fails

On 09.04.2021 14:41, rudu wrote: Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine could nevertheless surf the web with no problem ... I paste here a few commands I passed when

ping gateway ok, ping any other local network address fails

Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine could nevertheless surf the web with no problem ... I paste here a few commands I passed when remotely connected to the

Re: Re: Debian 9, dhclient does not update gateway

Started behaving on its own. I installed gateway host on monday, on thursday the gateway was correct on client. I did not find any mention of the old gateway address, but maybe it had gone away by the time I checked. This may be because the new gateway host was Debian desktop, I just removed

Re: Debian 9, dhclient does not update gateway

--r-- 1 root root0 Aug 23 2018 /var/lib/dhcp/dhclient.leases So for me the valid lease is actually in /var/lib/dhcp/dhclient.eth0.leases and dhclient.leases is empty and dhclient.eth1.leases is a blast from the past. I'm not using NetworkManager though. NetworkManager might have its own idea about gateway address.

Re: Debian 9, dhclient does not update gateway

On Mi, 06 ian 21, 15:41:27, Tapio Lehtonen wrote: > Old gateway host broke down, so I made a new one. One host now does get > from DHCP server the new gateway IP -address, but continues to use the old. > I can fix it temporarily doing > > dhclient -r ; dhclient > > but aft

Debian 9, dhclient does not update gateway

Old gateway host broke down, so I made a new one. One host now does get from DHCP server the new gateway IP -address, but continues to use the old. I can fix it temporarily doing dhclient -r ; dhclient but after boot it again uses the old gateway address. Another host also running Debian 9

RE: Debian 9 - systemd-networkd gateway

Merci Fabien. Ce que je comprend pas est que la première conf ne marche pas, alors que la seconde si. Il me semblait avoir lu que l'on pouvait mettre la Gateway dans la section Address. D'ailleurs cela fonctionnait, sur l'interface que j'ai désactivé. La Gateway était dans la section Address

Re: Debian 9 - systemd-networkd gateway

Erwan RIGOLLOT a écrit : > Bonjour Joël, > > Sur mes serveurs importants c'est ce que je fais, car je n'avais le temps de > me pencher sur la nouvelle syntaxe. > Ce serveur ne faisant que du stockage, j'ai laissé la configuration native de > la distribution histoire de commencer à découvrir

RE: Debian 9 - systemd-networkd gateway

: BERTRAND Joël Envoyé : vendredi 8 novembre 2019 09:56 À : debian-user-french@lists.debian.org Objet : Re: Debian 9 - systemd-networkd gateway Erwan RIGOLLOT a écrit : > Bonjour à tous, > >   > > J’avoue débuter avec le réseau géré avec systemd. > > Je voulais désactiver

Re: Debian 9 - systemd-networkd gateway

Erwan RIGOLLOT a écrit : > Bonjour à tous, > >   > > J’avoue débuter avec le réseau géré avec systemd. > > Je voulais désactiver une interface réseau et ajouter une passerelle par > défaut sur un vlan. (Pour ne plus avoir d’ip publique sur mon serveur > pour tout vous dire) > > Pour la

Re: Debian 9 - systemd-networkd gateway

On 07/11/2019 19:03, Erwan RIGOLLOT wrote: Est-ce normal que dans la 1ere conf, tu as > [Address] > Gateway=172.18.2.1 alors que dans la 2eme, tu as > [Route] > Gateway=172.18.2.1 -- Fabien

Re: Debian 9 - systemd-networkd gateway

pour Android<https://aka.ms/ghei36> From: Bernard Schoenacker Sent: Friday, November 8, 2019 2:35:47 AM To: Erwan RIGOLLOT ; debian-user-french@lists.debian.org Subject: Re: Debian 9 - systemd-networkd gateway - Mail original - > De: "

Re: Debian 9 - systemd-networkd gateway

- Mail original - > De: "Erwan RIGOLLOT" > À: debian-user-french@lists.debian.org > Envoyé: Jeudi 7 Novembre 2019 19:03:25 > Objet: Debian 9 - systemd-networkd gateway > Bonjour à tous, > J’avoue débuter avec le réseau géré avec systemd. > Je voulais

Debian 9 - systemd-networkd gateway

.network.disable. Je ne sais pas si c'est la bonne méthode mais cela fonctionne. En revanche, pour la route par défaut j'ai eu plus de mal. Cette configuration configurait bien l'interface mais n'a jamais appliqué la Gateway : [Match] Name=eno4.11 [Network] DHCP=no [Address] Address=172.18.2.251/24

Re: Where did my gateway go?

On 9/1/19, deloptes wrote: > Lee wrote: > >> If I had something like 10.10.11.0/24 connected to the wireless router >> I can see adding a static route so the laptop goes directly to the >> wlan default gateway instead of the ethernet default gateway (+ may

Re: Where did my gateway go?

Lee wrote: > If I had something like 10.10.11.0/24 connected to the wireless router > I can see adding a static route so the laptop goes directly to the > wlan default gateway instead of the ethernet default gateway (+ maybe > getting a redirect) & then to the wlan router to

Re: Where did my gateway go?

: >> root@hpg60:~# route >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric RefUse >> Iface >> default 10.10.2.1 0.0.0.0 UG10000 >> enp1s0 >> default 10.10.10.1

Re: Where did my gateway go?

On 31.08.19 01:14, Charlie Gibbs wrote: > On 30/08/19 03:42 PM, to...@tuxteam.de wrote: >> Try "traceroute pop.surfnaked.ca", that might shed some light > > traceroute to pop.surfnaked.ca (216.113.192.36), 30 hops max, 60 byte > packets >  1  gateway (192.168.0.1

Re: Where did my gateway go?

Lee wrote: > On 8/31/19, deloptes wrote: >> Charlie Gibbs wrote: >> >>> Destination Gateway Genmask Flags Metric RefUse >>> Iface >>> default gateway 0.0.0.0 UG0 0 0 >>> wlp3s0 >

Re: Where did my gateway go?

On 8/31/19, deloptes wrote: > Charlie Gibbs wrote: > >> Destination Gateway Genmask Flags Metric RefUse >> Iface >> default gateway 0.0.0.0 UG0 00 >> wlp3s0 >> default gateway 0.0

Re: Where did my gateway go?

ome anymore either, > although I can still access my LAN by either Ethernet or wifi. > > I was wondering whether my routing table got borked: > > cjg@cjglap2:~$ sudo route > Kernel IP routing table > Destination Gateway Genmask     Flags Metric Ref    Use >

Re: Where did my gateway go?

Charlie Gibbs wrote: > Destination     Gateway         Genmask         Flags Metric Ref    Use > Iface > default         gateway         0.0.0.0         UG    0      0        0 > wlp3s0 > default         gateway         0.0.0.0         UG    0      0        0 > enp0s25 yo

Re: Where did my gateway go?

On 2019-08-30 21:45, Charlie Gibbs wrote: My laptop (a Lenovo T410 running Stretch) has suddenly lost the ability to access the Internet. What has happened to my routing and how can I restore it? Is it possible that networking has somehow got Gateway confused with a machine called "ga

Re: Where did my gateway go?

(perhaps your ISP has changed his mind while you were away?) > > Try "traceroute pop.surfnaked.ca", that might shed some light traceroute to pop.surfnaked.ca (216.113.192.36), 30 hops max, 60 byte packets 1 gateway (192.168.0.1) 95.588 ms 95.547 ms 95.517 ms 2 10.31.12.1 (10.

Re: Where did my gateway go?

esolution seems to work, somehow. Don't count on "ping" (ICMP) getting through, not all firewalls allow that (perhaps your ISP has changed his mind while you were away?) Try "traceroute pop.surfnaked.ca", that might shed some light [...] > Destination Gateway Genmas

Where did my gateway go?

was wondering whether my routing table got borked: cjg@cjglap2:~$ sudo route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default gateway 0.0.0.0 UG0 00 wlp3s0 default gateway 0.0.0.0

Re: Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

Martin wrote: > I guess, my description was a kind of misleading: I want to connect the > phone (Samsung A3) to the PC's audio system, which is Pulseaudio in this > case. Just like you would connect it to a headset or your car's hands free > bluetooth thing. > Hi, I understood that you want to

Re: Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

in the pulseaudio configuration window a Headset Audio Gateway >> (HSP/HFP) with is offered by an Android phone. But the Buetooth >> blueman-manager refuses to set this audio profile. A2DP works fine though. > > Hi, > this topic is PITA for me since many moons. > I use Sailfish

Re: Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

On 11/09, Martin wrote: Hi folks, I wonder if some of you uses pulseaudio with cell phone telephony. For me, I see in the pulseaudio configuration window a Headset Audio Gateway (HSP/HFP) with is offered by an Android phone. But the Buetooth blueman-manager refuses to set this audio profile

Re: Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

Martin wrote: > I wonder if some of you uses pulseaudio with cell phone telephony. For me, > I see in the pulseaudio configuration window a Headset Audio Gateway > (HSP/HFP) with is offered by an Android phone. But the Buetooth > blueman-manager refuses to set this audio profile. A2D

Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

Hi folks, I wonder if some of you uses pulseaudio with cell phone telephony. For me, I see in the pulseaudio configuration window a Headset Audio Gateway (HSP/HFP) with is offered by an Android phone. But the Buetooth blueman-manager refuses to set this audio profile. A2DP works fine though.

Re: hostname of the modem gateway

t; >> > > > >The OP has said that he want it to get the hostname of his > >upstream router/gateway. > >'ip -r r' will show the FQDN of his default route (192.168.1.1) in > >that case. > > > > Rereading the all conversation I should have said to

Re: hostname of the modem gateway

On Tue, Jan 02, 2018 at 02:59:41PM +, Glenn English wrote: > On Mon, Jan 1, 2018 at 11:12 PM, Max Power wrote: > > > with the new release of Debian 'Stretch', the route command has been > > replaced > > Wipe your disk and install Buster. You get route++ back. Worst

Re: hostname of the modem gateway

On Mon, Jan 1, 2018 at 11:12 PM, Max Power wrote: > with the new release of Debian 'Stretch', the route command has been replaced Wipe your disk and install Buster. You get route++ back. Or create some shell scripts... -- Glenn English

Re: hostname of the modem gateway

On Tue, Jan 02, 2018 at 12:12:47AM +0100, Max Power wrote: > Hi guys, > with the new release of Debian 'Stretch', the route command has been replaced > but what other command returns the hostname of the modem/router gateway...? > # route > gateway = home.telecomitalia.it > #

Re: hostname of the modem gateway

On Tue, Jan 02, 2018 at 12:12:47AM +0100, Max Power wrote: > with the new release of Debian 'Stretch', the route command has been replaced > but what other command returns the hostname of the modem/router gateway...? > # route > gateway = home.telecomitalia.it > # ip route > gat

Re: hostname of the modem gateway

address, in other words the IP address cannot be resolved to its hostname. It has nothing at all to do with routing. The OP has said that he want it to get the hostname of his upstream router/gateway. 'ip -r r' will show the FQDN of his default route (192.168.1.1) in that case. Rereading

Re: hostname of the modem gateway

address cannot be resolved to its hostname. It has nothing at all to do with routing. The OP has said that he want it to get the hostname of his upstream router/gateway. 'ip -r r' will show the FQDN of his default route (192.168.1.1) in that case. -- John Doe

Re: hostname of the modem gateway

On Tue, Jan 02, 2018 at 07:52:31AM +0100, john doe wrote: > My default route is not 192.168.1.1 and host(1) gives me that same error. What the error actually means is that there is no reverse DNS resolution for that IP address, in other words the IP address cannot be resolved to its hostname. It

Re: hostname of the modem gateway

On 1/2/2018 7:45 AM, Tom Furie wrote: On Tue, Jan 02, 2018 at 07:38:54AM +0100, john doe wrote: Looks like 192.168.1.1 is not your default route. What led you to that conclusion? My default route is not 192.168.1.1 and host(1) gives me that same error. -- John Doe

Re: hostname of the modem gateway

On Tue, Jan 02, 2018 at 07:38:54AM +0100, john doe wrote: > Looks like 192.168.1.1 is not your default route. What led you to that conclusion? Cheers, Tom -- A good scapegoat is hard to find. A guilty conscience is the mother of invention. -- Carolyn Wells signature.asc

Re: hostname of the modem gateway

On 1/2/2018 7:15 AM, David Wright wrote: On Tue 02 Jan 2018 at 06:25:29 (+0100), john doe wrote: On 1/2/2018 12:12 AM, Max Power wrote: Hi guys, with the new release of Debian 'Stretch', the route command has been replaced but what other command returns the hostname of the modem/router gateway

Re: hostname of the modem gateway

On Tue 02 Jan 2018 at 06:25:29 (+0100), john doe wrote: > On 1/2/2018 12:12 AM, Max Power wrote: > >Hi guys, > >with the new release of Debian 'Stretch', the route command has been replaced > >but what other command returns the hostname of the modem/router gateway...?

Re: hostname of the modem gateway

On 1/2/2018 12:12 AM, Max Power wrote: Hi guys, with the new release of Debian 'Stretch', the route command has been replaced but what other command returns the hostname of the modem/router gateway...? # route gateway = home.telecomitalia.it # ip route gateway = 192.168.1.1 Thanks for reply

hostname of the modem gateway

Hi guys, with the new release of Debian 'Stretch', the route command has been replaced but what other command returns the hostname of the modem/router gateway...? # route gateway = home.telecomitalia.it # ip route gateway = 192.168.1.1 Thanks for reply, Max Power.

Static IPv6 gateway not working on Buster

Hello, I have a serious issue with IPv6 after upgrading several hosts from Jessie to Stretch. Default gateway cannot be set using gateway kword in /etc/network/interfaces. After some research over Internet, I figured out this is probably related to router advertisement so I added a list

Re: Gateway disappears on IPv6

; %c3%a4tzliche_IP_Adresse_konfigurieren#IPv6%7C > > That should still work, but I see it uses the ancient interface alias > notation (like eth0:1). The example given there can be rewritten to a > more modern form: > > allow-hotplug eth0 > iface eth0 inet static > address

Re: Gateway disappears on IPv6

That should still work, but I see it uses the ancient interface alias notation (like eth0:1). The example given there can be rewritten to a more modern form: allow-hotplug eth0 iface eth0 inet static address 37.100.195.4/22 gateway 37.100.192.1 iface eth0 inet static ad

Re: Gateway disappears on IPv6

!n -1 1 163 > ::lo > > root@netcup:~# > > After some time (at least hours) the server is not reachable anymore on its > IPv6 address, when connecting on the IPv4 address it seems that the gateway > fe80::1 got lost: > > root@netcup:~# ip -6 addr show >

Gateway disappears on IPv6

Rainer Dorsch: > for me it looks a little weird that IPv4 gets configured via dhcp and IPv6 is > a static configuration It's not, though. Do not fall into the trap of thinking that because you've had ubiquitous NAT, stateful DHCP, and the like for IP version 4 that this carries over into IP

Gateway disappears on IPv6

root@netcup:~# After some time (at least hours) the server is not reachable anymore on its IPv6 address, when connecting on the IPv4 address it seems that the gateway fe80::1 got lost: root@netcup:~# ip -6 addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 inet6 ::1/128 scope host

Re: Debian Server (NAT Gateway) Periodically Crashing

with one of my virtual machines. I am > running a KVM host with several virtual machines provide internet > services to a small network. The gateway machine is a Debian 8 minimum > install that was updated to 8.5. > > user1@gateway:~# sudo lsb_release -da > No LSB modules are

Re: Debian Server (NAT Gateway) Periodically Crashing

On 07/06/2016 11:38 PM, Christian Harris wrote: I am hoping to get some help with one of my virtual machines. I am running a KVM host with several virtual machines provide internet services to a small network. The gateway machine is a Debian 8 minimum install that was updated to 8.5. ... I

Debian Server (NAT Gateway) Periodically Crashing

Hello All, I am hoping to get some help with one of my virtual machines. I am running a KVM host with several virtual machines provide internet services to a small network. The gateway machine is a Debian 8 minimum install that was updated to 8.5. user1@gateway:~# sudo lsb_release -da No LSB

Gateway problem: have to add it manually after booting

I "solved" this problem by deleting the wireless connection and then adding it again. > On Debian Jessie I have to add the gateway to be able to get internet > over a wireless connection. I do this by the command: "route add default gw > 192.168.0.1 wlan0&qu

Gateway problem: have to add it manually after booting

On Debian Jessie I have to add the gateway to be able to get internet over a wireless connection. I do this by the command: "route add default gw 192.168.0.1 wlan0" How to make the gateway available automatically on booting like it was before? Extra info: I managed to connect two

Shorewall (ers: Gateway Postfix para varios dominios)

: http://shorewall.net/GettingStarted.html Les ilustro un poco más mi escenario: Tengo el postfix en cuestion en un server que hace funcion de gateway en mi red hacia LAN, DMZ y WAN. Tengo en la DMZ dos servidores de correo que responden a dos dominios distintos del mismo nivel: dominio1.com y

Re: Gateway Postfix para varios dominios

podría darme una mano en esta parte, pues realmente no tengo idea de como lograrlo. Les ilustro un poco más mi escenario: Tengo el postfix en cuestion en un server que hace funcion de gateway en mi red hacia LAN, DMZ y WAN. Tengo en la DMZ dos servidores de correo que responden a dos dominios distintos

Re: Gateway Postfix para varios dominios

El Fri, 05 Dec 2014 16:00:17 -0500, Lic. Manuel Salgado escribió: Alguien me podria ayudar en mi proposito? Tengo una pasarela con postfix en mi red. Esta gestiona el correo del dominio dominio1.com. Necesito que esta pasarela sea capaz de gestionar el correo de otros dos dominios, por

Gateway Postfix para varios dominios

Saludos a todos: Alguien me podria ayudar en mi proposito? Tengo una pasarela con postfix en mi red. Esta gestiona el correo del dominio dominio1.com. Necesito que esta pasarela sea capaz de gestionar el correo de otros dos dominios, por ejemplo dominio2.com, dominio3.com Gracias por adelantado

RE: unable to access website, getting 502 Bad Gateway errors

Hi, On 2014-07-21, Sharon Kimble boudic...@skimble.plus.com wrote: http://www.tgmeds.org.uk/ http://www.sharons.org.uk/ I get 502 Bad Gateway nginx/1.2.1 for both sites. I see both, what seems to be, correctly. Lisi Same here from the Netherlands, I see 2 websites that seem

unable to access website, getting 502 Bad Gateway errors

502 Bad Gateway, or 504 Gateway Time-out. They are both wordpress sites, but I can't even access the home page. Both of these sites show as being up and running with http://downforeveryoneorjustme.com/ which shows both sites up and running OK. I've cleared the cache of each browser, I've

Re: unable to access website, getting 502 Bad Gateway errors

, opera, midori, qupzilla, conkeror, links, and in all of them I get 502 Bad Gateway, or 504 Gateway Time-out. They are both wordpress sites, but I can't even access the home page. 5xx errors are server errors, so the choice of client shouldn't affect them. Both of these sites show as being

Re: unable to access website, getting 502 Bad Gateway errors

, opera, midori, qupzilla, conkeror, links, and in all of them I get 502 Bad Gateway, or 504 Gateway Time-out. They are both wordpress sites, but I can't even access the home page. Both of these sites show as being up and running with http://downforeveryoneorjustme.com/ which shows both sites

Re: unable to access website, getting 502 Bad Gateway errors

On 2014-07-21, Sharon Kimble boudic...@skimble.plus.com wrote: http://www.tgmeds.org.uk/ http://www.sharons.org.uk/ I get 502 Bad Gateway nginx/1.2.1 for both sites. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Re: unable to access website, getting 502 Bad Gateway errors

, konqueror, opera, midori, qupzilla, conkeror, links, and in all of them I get 502 Bad Gateway, or 504 Gateway Time-out. They are both wordpress sites, but I can't even access the home page. Both of these sites show as being up and running with http://downforeveryoneorjustme.com/ which shows both sites

Re: unable to access website, getting 502 Bad Gateway errors

, konqueror, opera, midori, qupzilla, conkeror, links, and in all of them I get 502 Bad Gateway, or 504 Gateway Time-out. They are both wordpress sites, but I can't even access the home page. Both of these sites show as being up and running with http://downforeveryoneorjustme.com/ which shows both

Re: unable to access website, getting 502 Bad Gateway errors

On Monday 21 July 2014 15:59:12 Curt wrote: On 2014-07-21, Sharon Kimble boudic...@skimble.plus.com wrote: http://www.tgmeds.org.uk/ http://www.sharons.org.uk/ I get 502 Bad Gateway nginx/1.2.1 for both sites. I see both, what seems to be, correctly. Lisi -- To UNSUBSCRIBE, email

SOLVED [Re: unable to access website, getting 502 Bad Gateway errors]

...@gmail.com writes: On Monday 21 July 2014 15:59:12 Curt wrote: On 2014-07-21, Sharon Kimble boudic...@skimble.plus.com wrote: http://www.tgmeds.org.uk/ http://www.sharons.org.uk/ I get 502 Bad Gateway nginx/1.2.1 for both sites. I see both, what seems to be, correctly. Lisi

Re: Setting up a home gateway/router

built a gateway / router / vpn / firewall at work using Debian Squeeze. The first thing I noticed is that you did not define a gateway for eth0. That could be your problem. This is normally defined for you by the dhcp server, so you would have not needed it before, but you probably need it now

Re: Setting up a home gateway/router

Hi. On Sat, 24 May 2014 12:21:05 +0200 csanyi...@gmail.com wrote: Yes, I thought as much, but don't know which IP address to add as a default gateway in my case? The command should look like this: # route add -net 10.0.0.0 netmask 255.0.0.0 gw 192.168.0.1 dev eth0

Re: Setting up a home gateway/router

Reco recovery...@gmail.com writes: On Sat, 24 May 2014 12:21:05 +0200 csanyi...@gmail.com wrote: Yes, I thought as much, but don't know which IP address to add as a default gateway in my case? The command should look like this: # route add -net 10.0.0.0 netmask 255.0.0.0 gw 192.168.0.1

Re: Setting up a home gateway/router

On 25/05/14 01:06, csanyi...@gmail.com wrote: Assuming that your 217.17.111.173/24 address on eth0 is correct, you probably need to set up default gateway as 217.17.111.1 (and you really should check it with your ISP, they are the only ones who know this). I just mail to my ISP and admins

Re: Setting up a home gateway/router

Hi. On Sat, 24 May 2014 15:06:52 +0200 csanyi...@gmail.com wrote: Well, I just tried that, but without success. /24 net allows 256 addresses. You've tried one (and is using another one), so it's 254 to go. As I wrote, if you don't want to guess - check with your ISP. Reco -- To

Re: Setting up a home gateway/router

On 25/05/14 02:04, Reco wrote: Hi. On Sat, 24 May 2014 15:06:52 +0200 csanyi...@gmail.com wrote: Well, I just tried that, but without success. /24 net allows 256 addresses. You've tried one (and is using another one), so it's 254 to go. As I wrote, if you don't want to guess -

  1   2   3   4   5   6   7   8   9   10   >