Re: need to make an eth0:1 net interface
On Monday 16 May 2016 15:55:33 Brian wrote:
> On Mon 16 May 2016 at 14:45:12 -0400, Gene Heskett wrote:
> > On Monday 16 May 2016 00:48:11 Andy Smith wrote:
> > > More details first, I think.
> > >
> > > Cheers,
> > > Andy
> >
> > Thanks for the interest Andy, but I got it working and its been
> > re-installed in place of the router that wasn't properly blocking
> > stuff.
> >
> > Seems to be working.
>
> So what was the ":1" about? And did it play any part in your solution?
> It was, after all, a feature of your of your original message.
>
> Glad you got it working in some unknown way.
That was an attempt to make use of the eth0 interface by adding the :1
that responded to the usual 192.168.1.X block of addresses.
That of course did NOT work.
So, I wound up with this in /etc/network/interfaces:
iface eth0 inet static
address 192.168.71.3
netmask 255.255.255.0
gateway 192.168.71.1
iface eth1 inet static
address 192.168.1.3
netmask 255.255.255.0
gateway 192.168.1.1
But the networking script in /etc/init.d, true to its word, would not
bring up eth1 on a restart, so that required an "sudo ifconfig eth1 up",
followed by a 'sudo ifconfig -a' which then returned:
eth0 Link encap:Ethernet HWaddr 00:1f:c6:62:fc:bb
inet addr:192.168.71.3 Bcast:192.168.71.255
Mask:255.255.255.0
inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11871853 errors:244 dropped:0 overruns:244 frame:0
TX packets:6354903 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15084069538 (14.0 GiB) TX bytes:1569246577 (1.4 GiB)
eth1 Link encap:Ethernet HWaddr 00:1f:c6:63:07:97
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:38903 (37.9 KiB)
At that point I could send FF to 192.168.1.1 and see the router, but it
acted as if it had not been reset, so thinking I had damaged the reset
switch, I started to open it up, which required I locate the teeniest
torx drivers I had in my quite extensive kit. While in the process of
removing its base stand, I found a hole in the bottom labeled reset. But
the base stand except for a teeny hole to match that on IF the base is
installed correctly. Murphy says its my fault for putting it on
bass-ackwards years ago. But except for that hole, it is absolutely
symmetrical. Duh, no wonder it didn't act reset, it hadn't been, so I
went thru the 30-30-30 thing again, and on the first access after it had
rebooted it from that, it forced me to reset the default username and
password to something a wee tad more secure. So I spent an hour
wandering thru its menu's restoring the options I wanted, then changed
its address to 71.1 and swapped the netgear out, putting this in
circuit. And it is doing its job precisely as I wanted it to do.
Everything but ARP is happy. It doesn't seem to me as if ARP has to
query and refresh the whole network every 30 seconds with a new batch of
who-has #.#.#.#, tell 192.168.71.1 queries. But I have yet, since 1998
and my first linux install, ever grokked how to setup the ARP system.
Probably my fault :) The netgear was doing it too FWIW.
But this worked, and the how is now in the archives.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: