On 3/12/23 12:17, Roger Heflin wrote:
I cannot log in, but the menu offered by the modem does not show any relevant
settings.
You might also test a device on wifi and/or login to the router and
send a test ping from inside the router with a large size.
WiFi is turned off on the modem, but
>
> I cannot log in, but the menu offered by the modem does not show any relevant
> settings.
>
> > You might also test a device on wifi and/or login to the router and
> > send a test ping from inside the router with a large size.
>
> WiFi is turned off on the modem, but I might give it a try.
>
>
On 3/12/23 11:30, Roger Heflin wrote:
On Sat, Dec 2, 2023 at 3:16 PM wrote:
On 3/12/23 00:43, Roger Heflin wrote:
My experience with the MTU being wrong is that often nothing works to
inform the sending end that the MTU is wrong.
The MTU being wrong (and below 1500) is not an expected/handle
On 3/12/23 03:47, Markus Schönhaber wrote:
02.12.23, 14:27 +0100, fed...@eyal.emu.id.au:
I did not do any change to the firewall, which is probably the only place
I could break things (like dropping ICMP).
The modem has a feature "IPv4 SPI Firewall" and turning it off did not
help here.
Well,
On Sat, Dec 2, 2023 at 3:16 PM wrote:
>
> On 3/12/23 00:43, Roger Heflin wrote:
> > My experience with the MTU being wrong is that often nothing works to
> > inform the sending end that the MTU is wrong.
> >
> > The MTU being wrong (and below 1500) is not an expected/handled
> > condition for the
On 3/12/23 00:43, Roger Heflin wrote:
My experience with the MTU being wrong is that often nothing works to
inform the sending end that the MTU is wrong.
The MTU being wrong (and below 1500) is not an expected/handled
condition for the TCP stack. meaning it will break for anything that
uses a M
02.12.23, 14:27 +0100, fed...@eyal.emu.id.au:
> I did not do any change to the firewall, which is probably the only place
> I could break things (like dropping ICMP).
> The modem has a feature "IPv4 SPI Firewall" and turning it off did not
> help here.
Well, I'm out of ideas, then.
> Anyway, if
a few
> byte(or more) than any advertised MTU in the path.
>
> So what does your network diagram look like?
>
>
> On Sat, Dec 2, 2023 at 7:28 AM wrote:
> >
> > On 2/12/23 23:01, Markus Schönhaber wrote:
> > > 02.12.23, 11:33 +0100, fed...@eyal.emu.id.au:
> > >
st few weeks I am trying to pinpoint the source of a network
> >> problem.
> >>
> >> The short story: using the standard mtu of 1500 caused sending to stall
> >> (and fail).
> >> This is seen when uploading a file (e.g. ftp) or when sending email.
> >
ey are trained monkeys that
know process, but don't have the slightest idea what the magic process
does, and often have extra useless steps in their process that they
don't understand that they think are doing something.
On Sat, Dec 2, 2023 at 4:34 AM wrote:
>
> For the last f
On 2/12/23 23:01, Markus Schönhaber wrote:
02.12.23, 11:33 +0100, fed...@eyal.emu.id.au:
For the last few weeks I am trying to pinpoint the source of a network
problem.
The short story: using the standard mtu of 1500 caused sending to stall
(and fail).
This is seen when uploading a file (e.g
02.12.23, 11:33 +0100, fed...@eyal.emu.id.au:
> For the last few weeks I am trying to pinpoint the source of a network
> problem.
>
> The short story: using the standard mtu of 1500 caused sending to stall
> (and fail).
> This is seen when uploading a file (e.g. ftp) or
For the last few weeks I am trying to pinpoint the source of a network problem.
The short story: using the standard mtu of 1500 caused sending to stall (and
fail).
This is seen when uploading a file (e.g. ftp) or when sending email.
With an mtu of 1456 everything works.
Everything worked unto
> On 5. Nov 2020, at 03:17, Jonathan Billings wrote:
>
> On Nov 4, 2020, at 18:39, Roger Heflin wrote:
>>
>> Typically if you want put 3 ip addresses in the same subnet on a
>> network usually you use a single network adaptor and add extra VIPs on
>> it.
>>
>> see:
>> https://www.jamescoyle
On Nov 4, 2020, at 18:39, Roger Heflin wrote:
>
> Typically if you want put 3 ip addresses in the same subnet on a
> network usually you use a single network adaptor and add extra VIPs on
> it.
>
> see:
> https://www.jamescoyle.net/how-to/307-create-a-virtual-ip-address-in-linux
>
> eth0:1 fo
Typically if you want put 3 ip addresses in the same subnet on a
network usually you use a single network adaptor and add extra VIPs on
it.
see: https://www.jamescoyle.net/how-to/307-create-a-virtual-ip-address-in-linux
eth0:1 for the device names it the 1st vip, :1 as the 2nd vip and so
on. Th
On 11/4/20 6:16 AM, Scott van Looy via users wrote:
So on startup, all 3 appear to be working and have IPs assigned according to
ifconfig, but...
.215 accepts pings, .216 and .217 do not
https://access.redhat.com/solutions/53031
reverse path filtering is on by default, and in that configur
On Wed, 4 Nov 2020 15:16:02 +0100
Scott van Looy via users wrote:
> It’s super frustrating. Does anyone have any ideas why this might happen or
> what could be causing it or any suggestions for what I can investigate?
I have absolutely no idea if this is the problem, but I know
when I setup an e
Hi,
I’ve managed to do something accidentally to my network config and I’m not sure
what.
I’m running a server inside of an ESXi host
It’s running using NetworkManager with 3x fixed IP addresses manually
configured, .215, .216 and .217
There are 3 virtual adaptors attached to the VM in questi
My problem is this --- on Fedora 23 I was managing my network interface
my self since Network Manager was causing problems. Now in F24, I
noticed that my nic now has the SLAVE flag on. I do not have any
network access at all. I tried allowing Network Manager to control the
device but still had th
On Thu, 17 Dec 2015 17:25:21 -0500
Fred Smith wrote:
> I always use NAT, I've never figured out how to make a bridged
> network function in a VM on VBox.
You have to have a physical interface attached to the bridge as well
as virtual ones. God alone only knows how you do that with
NetworkManager,
On Thu, Dec 17, 2015 at 07:55:53PM +, Patrick O'Callaghan wrote:
> I have the Oracle version of VBox (VirtualBox-5.0-
> 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any
> issues, but now (under F23) my Windows 7 guest has no network access. I
> have the appropriate VBox extensio
On Thu, 2015-12-17 at 13:43 -0700, jd1008 wrote:
>
> On 12/17/2015 01:15 PM, Patrick O'Callaghan wrote:
> > On Thu, 2015-12-17 at 13:08 -0700, jd1008 wrote:
> > > On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
> > > > I have the Oracle version of VBox (VirtualBox-5.0-
> > > > 5.0.10_104061_fed
On Thu, 2015-12-17 at 15:51 -0500, Tom Horsley wrote:
> On Thu, 17 Dec 2015 20:22:47 +
> Patrick O'Callaghan wrote:
>
> > Of course if the whole iptables thing has changed after some
> > update,
> > how would I know?
>
> Well, somewhere in there the iptables stuff was "replaced" with
> firewa
On Thu, 17 Dec 2015 20:22:47 +
Patrick O'Callaghan wrote:
> Of course if the whole iptables thing has changed after some update,
> how would I know?
Well, somewhere in there the iptables stuff was "replaced" with
firewalld. You might want to make sure firewalld is disabled
and iptables is ena
On 12/17/2015 01:15 PM, Patrick O'Callaghan wrote:
On Thu, 2015-12-17 at 13:08 -0700, jd1008 wrote:
On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0-
5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any
issues, but now (under F23
On Thu, 2015-12-17 at 14:15 -0600, kevin martin wrote:
> ip forwarding on? did you disable netfilter on bridging in
> /etc/sysctl.conf?
I haven't touched either of these, ever, and my current F23 was updated
from F22, which came from F21 etc. so any changes should have been
visible in rpmnew file
On Thu, 2015-12-17 at 13:08 -0700, jd1008 wrote:
>
> On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
> > I have the Oracle version of VBox (VirtualBox-5.0-
> > 5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any
> > issues, but now (under F23) my Windows 7 guest has no network
> >
ip forwarding on? did you disable netfilter on bridging in
/etc/sysctl.conf?
---
Regards,
Kevin Martin
On Thu, Dec 17, 2015 at 2:08 PM, jd1008 wrote:
>
>
> On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
>
>> I have the Oracle version of VBox (VirtualBox-5.0-
>> 5.0.10_104061_fedora22-
On 12/17/2015 12:55 PM, Patrick O'Callaghan wrote:
I have the Oracle version of VBox (VirtualBox-5.0-
5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any
issues, but now (under F23) my Windows 7 guest has no network access. I
have the appropriate VBox extension installed, and have
I have the Oracle version of VBox (VirtualBox-5.0-
5.0.10_104061_fedora22-1.x86_64) and it usually doesn't give any
issues, but now (under F23) my Windows 7 guest has no network access. I
have the appropriate VBox extension installed, and have shutdown and
restarted the guest VM, but to no avail.
On Thu, 2015-12-10 at 16:49 -0800, Gordon Messmer wrote:
> On 12/09/2015 11:36 PM, Cristian Sava wrote:
> > We are in stable stage so I do not expect NIC name changes without
> > consistent reason.
>
> I've never noticed it before, but this does look like a bug in
> Fedora.
>
> On my workstation,
On 12/09/2015 11:36 PM, Cristian Sava wrote:
We are in stable stage so I do not expect NIC name changes without
consistent reason.
I've never noticed it before, but this does look like a bug in Fedora.
On my workstation, for instance, /var/log/anaconda/anaconda.journal.log
contains:
Jul 21 2
On Thu, 2015-12-10 at 09:36 +0200, Cristian Sava wrote:
> On Wed, 2015-12-09 at 12:39 -0800, Gordon Messmer wrote:
> > On 12/09/2015 12:41 AM, Cristian Sava wrote:
> > > I Installed F23 Server with static address but after updating
> > > that
> > > it
> > > got an automatic one. Why that?
> > ...
>
On Wed, 2015-12-09 at 12:39 -0800, Gordon Messmer wrote:
> On 12/09/2015 12:41 AM, Cristian Sava wrote:
> > I Installed F23 Server with static address but after updating that
> > it
> > got an automatic one. Why that?
> ...
> > [root@s217 network-scripts]# cat ifcfg-eno1
> > HWADDR=00:1E:67:8B:B9:3
On Wed, 2015-12-09 at 13:52 +, Kseniya Blashchuk wrote:
> Yeah, strange a bit, but it seems you have some udev rules
> configured. It can cause interface naming mess maybe.
>
No, nothing configured.
That happen on F23 server & workstation installs on real hardware.
Steps to reproduce:
Install
On 12/09/2015 12:41 AM, Cristian Sava wrote:
I Installed F23 Server with static address but after updating that it
got an automatic one. Why that?
...
[root@s217 network-scripts]# cat ifcfg-eno1
HWADDR=00:1E:67:8B:B9:31
...
[root@s217 network-scripts]# cat ifcfg-eth1
HWADDR=00:1E:67:8B:B9:30
Yeah, strange a bit, but it seems you have some udev rules configured. It
can cause interface naming mess maybe.
ср, 9 дек. 2015 г. в 16:02, Cristian Sava :
> On Wed, 2015-12-09 at 12:02 +, Kseniya Blashchuk wrote:
> > Yep, sorry. So you restarted after changing BOOTPROTO? Try looking
> > int
On Wed, 2015-12-09 at 12:02 +, Kseniya Blashchuk wrote:
> Yep, sorry. So you restarted after changing BOOTPROTO? Try looking
> into dmesg or journalctl -n1000 | egrep "eno|eth", or something like
> that.
Yes, I allways rebooted.
Again, that config was working well until recent updates.
For now
Yep, sorry. So you restarted after changing BOOTPROTO? Try looking into
dmesg or journalctl -n1000 | egrep "eno|eth", or something like that.
ср, 9 дек. 2015 г. в 14:52, Cristian Sava :
> On Wed, 2015-12-09 at 11:47 +, Kseniya Blashchuk wrote:
> > But BOOTPROTO=dhcp is set for eth1. For which
On Wed, 2015-12-09 at 11:47 +, Kseniya Blashchuk wrote:
> But BOOTPROTO=dhcp is set for eth1. For which interface do you want
> static config? Did you restart the networking after you made config
> changes?
Read again, eth1 is not connected!
Only eno1 is in use!
C.S.
--
users mailing list
use
But BOOTPROTO=dhcp is set for eth1. For which interface do you want static
config? Did you restart the networking after you made config changes?
ср, 9 дек. 2015 г. в 14:39, Cristian Sava :
>
> >
> > Might
> > BOOTPROTO=static
> > help?
> >
> > suomi
>
> No, it does not help
>
> C.S.
>
> --
> user
>
> Might
> BOOTPROTO=static
> help?
>
> suomi
No, it does not help
C.S.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On 12/09/2015 09:51 AM, Cristian Sava wrote:
On Wed, 2015-12-09 at 10:41 +0200, Cristian Sava wrote:
I Installed F23 Server with static address but after updating that it
got an automatic one. Why that? I consider that extremely dangerous.
That was verified and happened on different hardware b
On Wed, 2015-12-09 at 10:41 +0200, Cristian Sava wrote:
> I Installed F23 Server with static address but after updating that it
> got an automatic one. Why that? I consider that extremely dangerous.
> That was verified and happened on different hardware boxes.
> Do I miss something? Does anyone els
I Installed F23 Server with static address but after updating that it
got an automatic one. Why that? I consider that extremely dangerous.
That was verified and happened on different hardware boxes.
Do I miss something? Does anyone else saw that?
This is what I have (eno1 wired, eth1 not connected)
On 12/11/2014 10:56 AM, Bill Oliver wrote:
> On Thu, 11 Dec 2014, Tim wrote:
>
>> On Wed, 2014-12-10 at 15:06 +, Bill Oliver wrote:
>>> Over the past few weeks, basically since I moved to Fedora21, there
>>> are extended periods where I simply cannot get to web pages using
>>> http. Things wil
On Thu, 11 Dec 2014, Tim wrote:
On Wed, 2014-12-10 at 15:06 +, Bill Oliver wrote:
Over the past few weeks, basically since I moved to Fedora21, there
are extended periods where I simply cannot get to web pages using
http. Things will work fine for hours, and then stop for hours, and
then c
On Wed, 2014-12-10 at 15:06 +, Bill Oliver wrote:
> Over the past few weeks, basically since I moved to Fedora21, there
> are extended periods where I simply cannot get to web pages using
> http. Things will work fine for hours, and then stop for hours, and
> then come back up.
>
> During th
I'm trying to figure out a networking issue, and I can't tell if it is a fedora
thing or not. Here's the issue:
I work at a place where the wired network has very strict security. One can go
to very few web pages, one has very limited access to applications, every box
has a keystroke logger
On 26/05/13 02:00, Phil Dobbin wrote:
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
always the same addresses from a dynamic IP.
A couple of days ago the IP changed & since then, one of the machines
running Fedora 17 always fails first time to connect to the netwo
Am 29.05.2013 22:14, schrieb Timothy Murphy:
> Patrick O'Callaghan wrote:
>
Timothy Murphy:
> Sorry, I mis-read the query.
> I was thinking of a DHCP server
The same basic answer still stands: A DHCP server, by default, doles
out dynamic IPs.
>>>
>>> I agree that dhc
Am 29.05.2013 19:34, schrieb Timothy Murphy:
> Tim wrote:
But are you talking about configuring a DHCP client or server?
>>
>> Timothy Murphy:
>>> Sorry, I mis-read the query.
>>> I was thinking of a DHCP server
>>
>> The same basic answer still stands: A DHCP server, by default, doles
>> o
On 30.05.2013 05:30, staticsafe wrote:
> Er, why are we disabling IPv6?
Er, for that very reason we are using 'dig'. ;)
…
> dig mirrors.fedoraproject.org
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/m
On 30.05.2013 04:55, Patrick O'Callaghan wrote:
…
> I used to use ddclient but actually I've found that the least effort
> solution is just to let my router do it. Many home routers now support
> DynDNS (and similar services) directly, so I just configure it once and
> forget about it. Make sure to
On Thu, May 30, 2013 at 05:19:39AM +0200, poma wrote:
> On 26.05.2013 17:35, Phil Dobbin wrote:
> …
> > 'Could not get metalink
> > https://mirrors.fedoraproject.org/metalink?repo=updates-released-f17&arch=x86_64
> > error was
> > 14: curl#6 - "Could not resolve host: mirrors.fedoraproject.org; Nam
On 26.05.2013 17:35, Phil Dobbin wrote:
…
> 'Could not get metalink
> https://mirrors.fedoraproject.org/metalink?repo=updates-released-f17&arch=x86_64
> error was
> 14: curl#6 - "Could not resolve host: mirrors.fedoraproject.org; Name or
> service not known"'
curl -4
"https://mirrors.fedoraproject
On Thu, 2013-05-30 at 09:45 +0930, Tim wrote:
> If you felt like a lot of hard work, you could probably write
> something
> that was triggered by your DHCP client to talk to dyndns, if DHCP was
> responsible for your address changes. Less work would be to use
> NetworkManager's despatch scripts to
Allegedly, on or about 29 May 2013, Timothy Murphy sent:
> You all seem to be finding it difficult to follow my meaning.
> I'm saying that the term "dynamic IP" is normally used
> to refer to an ISP giving the same client different IP addresses
> at different times, in order to to limit the number
On Wed, 2013-05-29 at 21:14 +0100, Timothy Murphy wrote:
> Patrick O'Callaghan wrote:
>
> >> > Timothy Murphy:
> >> >> Sorry, I mis-read the query.
> >> >> I was thinking of a DHCP server
> >> >
> >> > The same basic answer still stands: A DHCP server, by default, doles
> >> > out dynamic IPs.
>
On 05/29/2013 01:14 PM, Timothy Murphy wrote:
You all seem to be finding it difficult to follow my meaning.
I'm saying that the term "dynamic IP" is normally used
to refer to an ISP giving the same client different IP addresses
at different times, in order to to limit the number of address requir
Patrick O'Callaghan wrote:
>> > Timothy Murphy:
>> >> Sorry, I mis-read the query.
>> >> I was thinking of a DHCP server
>> >
>> > The same basic answer still stands: A DHCP server, by default, doles
>> > out dynamic IPs.
>>
>> I agree that dhcp by default gives an IP address in a given range o
On Wed, 2013-05-29 at 18:34 +0100, Timothy Murphy wrote:
> Tim wrote:
>
> > Tim:
> >>> But are you talking about configuring a DHCP client or server?
> >
> > Timothy Murphy:
> >> Sorry, I mis-read the query.
> >> I was thinking of a DHCP server
> >
> > The same basic answer still stands: A DHCP
Tim wrote:
> Tim:
>>> But are you talking about configuring a DHCP client or server?
>
> Timothy Murphy:
>> Sorry, I mis-read the query.
>> I was thinking of a DHCP server
>
> The same basic answer still stands: A DHCP server, by default, doles
> out dynamic IPs.
I agree that dhcp by default g
Tim:
>> But are you talking about configuring a DHCP client or server?
Timothy Murphy:
> Sorry, I mis-read the query.
> I was thinking of a DHCP server
The same basic answer still stands: A DHCP server, by default, doles
out dynamic IPs.
In other words, until an administrator customises the
Tim wrote:
> Allegedly, on or about 27 May 2013, Timothy Murphy sent:
>> As a matter of interest, how do you configure DHCP
>> to work with a dynamic IP?
> But are you talking about configuring a DHCP client or server?
Sorry, I mis-read the query.
I was thinking of a DHCP server
--
Timothy M
about configuring a DHCP client or server?
Right. Computer asks server for address & it's done by automatic lease.
The state of the play at the moment is the network problem still occurs.
I restored (via Clonezilla) from a known good backup that was taken
before all this nonsense started
Allegedly, on or about 27 May 2013, Timothy Murphy sent:
> As a matter of interest, how do you configure DHCP
> to work with a dynamic IP?
Um, generally you don't... It does that by default. Your DHCP client
(your usual personal computer) asks a DHCP server for an address, and
the DHCP server t
Phil Dobbin wrote:
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
As a matter of interest, how do you configure DHCP
to work with a dynamic IP?
I use ddclient with dyndns,
but are you saying one doesn't need to do something l
On 05/26/2013 05:11 AM, Phil Dobbin wrote:
The same address assigned is in the 192.168.1.xxx range & is, obviously,
internal. The dynamic IP is external & this is the one that changes & I
have no control over it (& I can't get a static IP unfortunately).
Sorry, I'd been under the impression tha
On Sun, 2013-05-26 at 02:00 +0100, Phil Dobbin wrote:
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
>
> A couple of days ago the IP changed & since then, one of the machines
> running Fedora 17 always fails first time to conne
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote:
[...]
> Dumb question - have you checked the network connection? See if
> changing the cable or the port on the switch helps. It seams strange
> that the external IP address changing would cause this, but for some
> strange reason hardware probl
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote:
> On 05/26/2013 07:18 AM, Phil Dobbin wrote:
>> On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
>>> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
alwa
On 05/26/2013 07:18 AM, Phil Dobbin wrote:
> On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
>> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
>>> Hi, all.
>>>
>>> I've got several machines on a LAN behind a NAT with DHCP assigning
>>> always the same addresses from a dynamic IP.
>>>
>>> A couple of
On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
>> Hi, all.
>>
>> I've got several machines on a LAN behind a NAT with DHCP assigning
>> always the same addresses from a dynamic IP.
>>
>> A couple of days ago the IP changed & since then, one of the ma
On 05/26/2013 02:21 AM, Joe Zeff wrote:
> On 05/25/2013 06:00 PM, Phil Dobbin wrote:
>> I've got several machines on a LAN behind a NAT with DHCP assigning
>> always the same addresses from a dynamic IP.
>>
>> A couple of days ago the IP changed & since then, one of the machines
>> running Fedora
On 05/25/2013 08:00 PM, Phil Dobbin wrote:
> Hi, all.
>
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
>
> A couple of days ago the IP changed & since then, one of the machines
> running Fedora 17 always fails first time to conne
On 05/25/2013 06:00 PM, Phil Dobbin wrote:
I've got several machines on a LAN behind a NAT with DHCP assigning
always the same addresses from a dynamic IP.
A couple of days ago the IP changed & since then, one of the machines
running Fedora 17 always fails first time to connect to the network:
l
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
always the same addresses from a dynamic IP.
A couple of days ago the IP changed & since then, one of the machines
running Fedora 17 always fails first time to connect to the network:
launch Thunderbird, no start screen,
192.168.114.1 is gateway? it should have at least static route for
193.204.165.0/24 network over 192.168.114.60 interface.
On 4 July 2012 14:04, Tiziana Manfroni wrote:
>
>> For the system with IP address 192.168.114.30 what is the output of
>> netstat -nr ?
>>
>
> Kernel IP routing table
> Dest
I forward network packets to the same network interface from where it came from
using utility ip.
Thanks a lot.
Tiziana
/ / \ Tiziana Manfroni
/ / /\ \ Dipartimento di Matematica
/ / /\ \ \
On 07/04/2012 08:04 PM, Tiziana Manfroni wrote:
>> For the system with IP address 192.168.114.30 what is the output of netstat
>> -nr ?
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse Iface
> 192.168.114.0 0.0.0.0 255.255.255.0 U
On 04. juli 2012 14:04, Tiziana Manfroni wrote:
For the system with IP address 192.168.114.30 what is the output of
netstat -nr ?
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.114.0 0.0.0.0 255.255.255.0 U 0 0
For the system with IP address 192.168.114.30 what is the output of netstat -nr
?
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.114.0 0.0.0.0 255.255.255.0 U 0 00
eth0
169.254.0.0 0.0.0.0
vv www@192.168.114.60' I see "www@192.168.114.60's password:" I have
> this
> network problem for all services on server (http, https, mail) and not for
> only
> ssh. This server works on RHEL6.3. The service NetworkManager is disable, only
> service network is
host with IP address 192.168.114.30 in 'ssh -vvv www@193.204.165.224' the output is "ssh:
connect to 193.204.165.224 port 22: no route to host". When I connect with 'ssh
-vvv www@192.168.114.60' I see "www@192.168.114.60's password:" I have this
netwo
2011/8/22 Lázaro Morales :
>
> After a fresh install of libvirt in a box with one physical interface
> (eth0), I tried to set up a bridged network in br0:
>
> [ifcfg-eth0:]
>
> DEVICE=eth0
> HWADDR=48:5b:39:ba:f9:2a
> NM_CONTROLLED=no
> BRIDGE="br0"
> ONBOOT=yes
> NETMASK=255.255.255.0
> IPADDR=192
Hello,
After a fresh install of libvirt in a box with one physical interface
(eth0), I tried to set up a bridged network in br0:
[ifcfg-eth0:]
DEVICE=eth0
HWADDR=48:5b:39:ba:f9:2a
NM_CONTROLLED=no
BRIDGE="br0"
ONBOOT=yes
NETMASK=255.255.255.0
IPADDR=192.168.0.10
GATEWAY=192.168.0.2
DNS2=192.16
88 matches
Mail list logo
