Gordon Messmer writes:
> On 10/08/2015 11:21 PM, Wolfgang S. Rupprecht wrote:
>> Hacking routes as one of the other replies suggested will only solve
>> half the problem. The packet gets flung in the right direction. The
>> problem is that the return packet won't be accepted. In fact the arp
>
On 10/08/2015 11:21 PM, Wolfgang S. Rupprecht wrote:
Hacking routes as one of the other replies suggested will only solve
half the problem. The packet gets flung in the right direction. The
problem is that the return packet won't be accepted. In fact the arp
reply won't even happen.
That's n
Bob Goodwin writes:
> I have a device that when reset requires I set my Fedora-22 computer
> to the address 1.1.1.2 in order that I can access it at 1.1.1.1. with
> my Firefox browser.
# allow us to talk to our zoom modem at 192.168.100.1/24
/usr/sbin/ip addr add 192.168.100.2/24 dev eth0.2
Hac
On 06Oct2015 22:27, Gordon Messmer wrote:
On 10/06/2015 05:06 PM, Cameron Simpson wrote:
Rick gave a nightmarishly complex answer, as did several others. It might
work, but I'm not sure I'd call it reasonable. Bob only needed a temporary
config, so the reasonable thing to do is to add an "eth0
On 10/06/2015 05:06 PM, Cameron Simpson wrote:
Rick gave a nightmarishly complex answer, as did several others. It
might work, but I'm not sure I'd call it reasonable. Bob only needed a
temporary config, so the reasonable thing to do is to add an "eth0:0"
with the right addressing as already
On 06Oct2015 12:05, Gordon Messmer wrote:
On 10/06/2015 08:42 AM, Bob Goodwin wrote:
I've saved this for future use, too bad you weren't here yesterday
...
Rick gave a reasonable response. Could have been improved to not
interfere with regular network access, but I thought it was good enoug
On 10/06/2015 12:36 PM, Bob Goodwin wrote:
On 10/06/15 15:05, Gordon Messmer wrote:
too bad you weren't here yesterday ...
Rick gave a reasonable response. Could have been improved to not
interfere with regular network access, but I thought it was good enough.
.
Yes. Initially I could not g
On 10/06/2015 12:15 PM, Gordon Messmer wrote:
On 10/06/2015 09:13 AM, Robert Nichols wrote:
It's highly likely that it will simply use its only interface as
a default route, at least that's the way it worked for the two IP
cameras I set up that also had an initial IP address of 1.1.1.1.
That's
On 10/06/15 15:05, Gordon Messmer wrote:
too bad you weren't here yesterday ...
Rick gave a reasonable response. Could have been improved to not
interfere with regular network access, but I thought it was good enough.
.
Yes. Initially I could not get the NM GUI to respond to my entries.
A
On 10/06/2015 09:13 AM, Robert Nichols wrote:
It's highly likely that it will simply use its only interface as
a default route, at least that's the way it worked for the two IP
cameras I set up that also had an initial IP address of 1.1.1.1.
That's not generally how IPv4 works. In the simple,
On 10/06/2015 08:42 AM, Bob Goodwin wrote:
I've saved this for future use, too bad you weren't here yesterday ...
Rick gave a reasonable response. Could have been improved to not
interfere with regular network access, but I thought it was good enough.
--
users mailing list
users@lists.fedora
On 10/06/2015 09:39 AM, Gordon Messmer wrote:
On 10/06/2015 05:24 AM, Robert Nichols wrote:
ip route add to 1.1.1.1 dev enp0s25
That's all there is to it. Your system now knows that address 1.1.1.1
can be reached directly (no gateway) on that interface.
And how does that destination re
On 10/06/15 10:39, Gordon Messmer wrote:
The right way to do this was always to add 1.1.1.2 to Bob's
interface. Either, as was suggested, using the older (deprecated)
ifconfig command:
ifconfig eth0:0 1.1.1.2 netmask 255.255.255.0
or using ip:
ip addr add 1.1.1.2/24 dev eth0
.
I've
On 10/06/2015 05:24 AM, Robert Nichols wrote:
ip route add to 1.1.1.1 dev enp0s25
That's all there is to it. Your system now knows that address 1.1.1.1
can be reached directly (no gateway) on that interface.
And how does that destination respond?
It's not as simple as you suggest. The
On 10/06/2015 03:19 AM, Bob Goodwin wrote:
On 10/05/15 21:18, Robert Nichols wrote:
All you needed to do was add a routing table entry to direct packets for
1.1.1.1 out the appropriate interface. No need to mess up the rest of
your networking.
.
I was able to accomplish what I needed to do an
On 10/05/15 21:18, Robert Nichols wrote:
All you needed to do was add a routing table entry to direct packets for
1.1.1.1 out the appropriate interface. No need to mess up the rest of
your networking.
.
I was able to accomplish what I needed to do and the system was returned
to normal withou
On 10/05/2015 03:12 PM, Bob Goodwin wrote:
On 10/05/15 15:50, Rick Stevens wrote:
The instruction says the reset device is now 1.1.1.1
I need to access it at that address in order to configure it.
To change the config on F22 via the NM GUI, just right click on the
icon, select "Edit connecti
On 10/05/15 15:50, Rick Stevens wrote:
The instruction says the reset device is now 1.1.1.1
I need to access it at that address in order to configure it.
To change the config on F22 via the NM GUI, just right click on the
icon, select "Edit connections", select the connection you want to
chan
On 10/05/2015 12:16 PM, Bob Goodwin wrote:
On 10/05/15 15:08, Rick Stevens wrote:
Do you want to change the computer's IP via the GUI or the "device"?
.
The F-22 computer.
If it's the computer, what desktop are you using and are you using
Network Manager or ye oldie network scripts?
.
On 10/05/15 15:08, Rick Stevens wrote:
Do you want to change the computer's IP via the GUI or the "device"?
.
The F-22 computer.
If it's the computer, what desktop are you using and are you using
Network Manager or ye oldie network scripts?
.
I was trying with the NM GUI since there is
On 10/05/2015 11:56 AM, Bob Goodwin wrote:
I have a device that when reset requires I set my Fedora-22 computer to
the address 1.1.1.2 in order that I can access it at 1.1.1.1. with my
Firefox browser.
I only need to do this long enough to change it's address to 191.168.1.200.
My attempts at us
vi /etc/sysconfig/network-scripts/ifcfg-
UUID="3b09ebdf-057f-4ead-ab74-7bd90cdc4980"
NM_CONTROLLED=yes
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
IPADDR0=108.220.213.121
NETMASK=255.255.255.248
save a copy of file, then edit above file, restart network...
hth, ...
On Mon, Oct 5, 2015 at 11:56 A
I have a device that when reset requires I set my Fedora-22 computer to
the address 1.1.1.2 in order that I can access it at 1.1.1.1. with my
Firefox browser.
I only need to do this long enough to change it's address to 191.168.1.200.
My attempts at using the network GUI have not been successf
23 matches
Mail list logo
