On 25/01/2025 14:17, Thomas Anderson wrote:
$ nmcli connection show
IP4.ADDRESS[1]: 192.168.1.6/24
IP4.GATEWAY: 192.168.1.1
IP4.ROUTE[1]: dst = 192.168.1.0/24, nh =
0.0.0.0, mt = 100
IP4.ROUTE[2
192.168.1.8
> ipv4.addresses: 192.168.1.6/24
> ipv4.gateway: 192.168.1.1
SO this all looks okay. I was wondering if it was going to show it
configured by DHCP which would have suggested maybe a DHCP lease was
changing the default gatew
dns-search: --
ipv4.dns-options: --
ipv4.dns-priority: 0
ipv4.addresses: 192.168.1.6/24
ipv4.gateway: 192.168.1.1
ipv4.routes: --
ipv4.route-metric: -1
or something.
As a workaround, if you know that your router should be 192.168.1.1 then
you can at each boot, as root, type:
# ip route add default via 192.168.1.1
and that will temporarily set the default gateway. But this should be
fixable in N-M settings.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
ines for network
#auto enp27s0
#iface enp27s0 inet static
# address 192.168.1.6 #static ip i want
# netmask 255.255.255.0 #netmask
# gateway 192.168.1.1 #my router
# dns-nameservers 192.168.1.8 #my dns server
In the past, I had used the above configuration -- but in truth, it also
didn&#x
On Fri, Jan 24, 2025 at 17:11:06 +0100, Thomas Anderson wrote:
> Here is updated version with
CR in this context means carriage returns. Which is actually not the
correct term -- they meant LF (line feed) or newlines.
But what they *really* meant was for you to send the message as plain
text, n
On Fri, 24 Jan 2025 16:14:05 +0100
Thomas Anderson wrote:
> Thanks for thorough reply.
>
> 1. I am talking about basic network connection. I have an ip, so I
> can ping local machines, including the gateway router itself.
>
> 'ip a' shows the following
>
> 1:
Here is updated version with
Thanks for thorough reply.
1. I am talking about basic network connection. I have an ip, so I can
ping local machines, including the gateway router itself.
'ip a'
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 0
On 2025-01-24, Thomas Anderson wrote:
> 'ip a' shows the following
> 'cat /etc/network/interfaces.d/*' shows
Could you give us the result with CR. It's unreadable without, especially
for commented lines.
Perhaps give also
ip r
Thanks for thorough reply.
1. I am talking about basic network connection. I have an ip, so I can
ping local machines, including the gateway router itself.
'ip a' shows the following
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00
Hi Thomas,
On Friday, 24 January 2025 08:35:44 GMT-4 Thomas Anderson wrote:
> Hello,
>
> I am using Debian 11, and no matter what I do, I repeated on each
> reboot, I will boot into a system with no gateway set (or rather, the
> "default route is 0.0.0.0," which natur
Hello,
I am using Debian 11, and no matter what I do, I repeated on each
reboot, I will boot into a system with no gateway set (or rather, the
"default route is 0.0.0.0," which naturally gives this device no
internet connectivity.
I am using the NetworkManager, and have a static I
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 bey
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 as
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}
> > {INTERFA
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 om
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
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
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 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
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 must
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
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 a /3
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
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 tw
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
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
up.
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?
Thanks.
Yong
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 t
ike 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 h
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 s
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
--
http://wiki.debian.org/FAQsFromDebian
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 remote
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 po
ddress "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 tu
n 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 s
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
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 remo
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
problematic
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
the
--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.
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
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
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 (+ maybe
>> get
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
ed any problems:
>> 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
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
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
>
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
work at home 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
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
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
that
> (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
lution 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 G
i.
I 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
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 c
> 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.
>
> Hi,
> this topic is PITA for me since many moons.
> I us
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
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
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.
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 s
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 advice ever.
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
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.
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 rout
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.
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
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
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
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
Descr
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/rout
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 ga
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
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.
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 of
liche_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
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
> lo fe80::5054:9cff:fe31:f1e0/128 :: Un 0 1
> 5 lo ff00::/8 :: U256 10
>0 eth0
>
> ::/0 :: !n -1 1 163
> ::lo
>
> root@netcup:~#
>
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 ver
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: mtu 65536
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qlen 1000
inet6 2a03:4000:6
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 modules
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
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
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
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 co
Hi,
>> On 2014-07-21, Sharon Kimble 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, correctl
> On Monday 21 July 2014 15:59:12 Curt wrote:
>> On 2014-07-21, Sharon Kimble wrote:
>>
>> http://www.tgmeds.org.uk/
>> http://www.sharons.org.uk/
>>
>> I get
>>
>> 502 Bad Gateway
>> nginx/1.2.1
>>
>> for both sites.
>
> I
On Monday 21 July 2014 15:59:12 Curt wrote:
> On 2014-07-21, Sharon Kimble 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
rome,
iceweasel, 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://
rome,
iceweasel, 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://downf
On 2014-07-21, Sharon Kimble 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...@lists.
rome,
> iceweasel, 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
rome,
> iceweasel, 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.
5xx errors are server errors, so the choice of clie
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 up and running
OK.
I've clea
On Sat, 24 May 2014 18:27:28 +0200
Pascal Hambourg wrote:
> Huh ? NAT does not make things simpler but more complicated !
> What would be the benefit of using NAT here ?
Security by obscurity. NAT is one more hassle the badguys have to get
through to get to your stuff. As botnets turn into brute
reservation for your MAC address ?
> In the latter case, revert to DHCP and you'll get all the required
> parameters (address, netmask, gateway, DNS) automatically.
The problem is solved now.
It is not really static but DHCP with a reservation for my MAC address.
I mentioned befor
On Sat, 24 May 2014 18:45:38 +0200
Pascal Hambourg wrote:
> Reco a écrit :
> > Pascal Hambourg wrote:
> >
> >>> Reco writes:
> >>>
> /24 net allows 256 addresses. You've tried one (and is using another
> one), so it's 254 to go.
> >> Less. .0 and .255 are reserved as network and broa
Hi.
On Sat, 24 May 2014 18:27:28 +0200
Pascal Hambourg wrote:
> Reco a écrit :
> >
> > To keep things simple. Two host can communicate with each other without
> > third party (router) only if they have their IPs from the same network.
>
> No. Only if they share the same broadcast domain (link
Reco a écrit :
> Pascal Hambourg wrote:
>
>>> Reco writes:
>>>
/24 net allows 256 addresses. You've tried one (and is using another
one), so it's 254 to go.
>> Less. .0 and .255 are reserved as network and broadcast addresses.
>
> I seen ISPs that advertise routes ending with 0. A vio
Reco a écrit :
>
> To keep things simple. Two host can communicate with each other without
> third party (router) only if they have their IPs from the same network.
No. Only if they share the same broadcast domain (link layer network),
regardless of IP addressing. Usually IP subnetting matches li
1 - 100 of 895 matches
Mail list logo
