1 |
On Sat, Feb 21, 2015 at 11:52 PM, Walter Dnes <waltdnes@××××××××.org> wrote: |
2 |
|
3 |
|
4 |
> My DSL router modem is at 192.168.123.254. I have an HDHomerun |
5 |
> network TV tuner that insists on coming up somewhere in the 169.254.X.Y |
6 |
> block. Up until upgrading from 32 to 64 bits, I was able to see a 2nd |
7 |
> eth0 (i.e. eth0:1) using the following /etc/conf.d/net setup... |
8 |
> |
9 |
> config_eth0=" |
10 |
> 192.168.123.251/29 broadcast 192.168.123.255 |
11 |
> 169.254.1.1/16 broadcast 169.254.255.255" |
12 |
> routes_eth0=" |
13 |
> default via 192.168.123.254 metric 20 |
14 |
> 192.168.123.248/29 via 192.168.123.254 metric 0 |
15 |
> 169.254.0.0/16 via 169.254.1.1 metric 0" |
16 |
> |
17 |
> The 2nd interface is no longer being set up. As amatter of fact, it |
18 |
> appears to be totally unavailable. E.g.... |
19 |
> |
20 |
> [d531][root][~] /etc/init.d/net.eth0 stop |
21 |
> * Unmounting network filesystems ... [ ok ] |
22 |
> * Bringing down interface eth0 |
23 |
> [d531][root][~] ifconfig eth0:0 192.168.123.251/29 broadcast 192.168.123.255 |
24 |
> SIOCSIFNETMASK: Cannot assign requested address |
25 |
|
26 |
You cannot bring up an ip alias if the "base" ip address isn't set. |
27 |
|
28 |
|
29 |
> [d531][root][~] ifconfig eth0 192.168.123.251/29 broadcast 192.168.123.255 |
30 |
> [d531][root][~] |
31 |
> |
32 |
> So my system doesn't support even the concept of an alias for eth0. |
33 |
> Looking at the ifconfig manpage... |
34 |
> |
35 |
> interface |
36 |
> The name of the interface. This is usually a driver name fol- |
37 |
> lowed by a unit number, for example eth0 for the first Ethernet |
38 |
> interface. If your kernel supports alias interfaces, you can |
39 |
> specify them with eth0:0 for the first alias of eth0. You can |
40 |
> use them to assign a second address. To delete an alias inter- |
41 |
> face use ifconfig eth0:0 down. Note: for every scope (i.e. same |
42 |
> net with address/netmask combination) all aliases are deleted, |
43 |
> if you delete the first (primary). |
44 |
> |
45 |
> I see "If your kernel supports alias interfaces". During the |
46 |
> upgrade, I built the kernel from square 1. I already ran into problems |
47 |
> with not enabling FUSE in the new kernel, which killed MTP until I |
48 |
> enabled it. I wouldn't be surprised if I've disabled some kernel |
49 |
> parameter which is required to enable interface aliases. I didn't see |
50 |
> anything obvious in "make menuconfig". A Google search turned up a |
51 |
> gazillion examples of "how to create an alias using ifconfig". That's |
52 |
> not what I want. I want the kernel setting that allows creating alias |
53 |
> interfaces. |
54 |
|
55 |
CONFIG_IP_ALIAS was dropped with v2.4 |
56 |
|
57 |
From 2.2 alias.txt: |
58 |
|
59 |
For IP aliasing you must have IP_ALIAS support included by static |
60 |
linking. |
61 |
|
62 |
From 2.4 alias.txt: |
63 |
|
64 |
IP-aliases are additional IP-adresses/masks hooked up to a base |
65 |
interface by adding a colon and a string when running ifconfig. |
66 |
This string is usually numeric, but this is not a must. |
67 |
|
68 |
IP-Aliases are avail if CONFIG_INET (`standard' IPv4 networking) |
69 |
is configured in the kernel. |
70 |
|
71 |
From 3.19 alias.txt: |
72 |
|
73 |
IP-aliases are an obsolete way to manage multiple IP-addresses/masks |
74 |
per interface. Newer tools such as iproute2 support multiple |
75 |
address/prefixes per interface, but aliases are still supported |
76 |
for backwards compatibility. |