we have eth1; in the beginning it was proposed to create from eth1,
eth1.2500 and eth1.240. It did not worked cause vlan 1.2500 was not
tagged in the switch.
so they decided to leave eth1 like a physical interface with eth1.2500
config (removel vlan tag) and create eth1.240
but it did not work because when eth1.240 is up , the eth1 lose it´s
gateway using eth1.240 gateway. manually we get to assing its gateway
but its a temporal solution , cause if service network or server is
restarted it turns back. we need a permanent solution.
Destination Gateway Genmask Flags Metric Ref Use Iface
10.53.129.192 10.224.248.1 255.255.255.240 UG 0 0 0 eth1.240
10.53.129.0 10.224.248.1 255.255.255.240 UG 0 0 0 eth1.240
10.130.0.0 0.0.0.0 255.255.255.192 U 0 0 0 eth1
10.129.15.0 0.0.0.0 255.255.255.128 U 0 0
0 eth0.1020
10.224.248.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1.240
10.129.0.0 10.129.15.3 255.255.0.0 UG 0 0
0 eth0.1020
0.0.0.0 10.130.0.4 0.0.0.0 UG 0 0 0 eth1
last line you see above is the one which is not included in route
tables by default, even if GATEWAY is configured in
/etc/sysconfig/network
we looked for a file which could affect including a route by default
but we didnt find it.
i rebooted the server, and i´ve been thinking about using this command
/sbin/ip route flush table all
but i think if i already rebooted after erase all eth1.240 (route too)
files it would be useless
i would like anybody help me cause i´m in a hurry
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org