eth0 Link encap:Ethernet HWaddr 00:A0:24:51:3D:B3
inet addr:204.17.222.1 Bcast:204.17.222.255 Mask:255.255.255.0
EtherTalk Phase 2 addr:65280/136
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34432 errors:0 dropped:0 overruns:0 frame:0
TX packets:21252 errors:0 dropped:0 overruns:0 carrier:1 coll:37
Interrupt:11 Base address:0x6200
eth0:1 Link encap:Ethernet HWaddr 00:A0:24:51:3D:B3
inet addr:192.168.3.30 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:11 Base address:0x6200
Destination Gateway Genmask Flags MSS Window irtt
Iface
localnet * 255.255.255.0 U 0 0 0
eth0
192.168.3.0 * 255.255.255.0 U 0 0 0
eth0
default isdn.csihq.com 0.0.0.0 UG 0 0 0
eth0
While this works and allows the 204 clients to get to the 192 network, I get
some error messages about the clients ignoring redirects:
Dec 2 06:57:32 picard kernel: host 0fde11cc/eth0 ignores redirects for
0103a8c0 to 0103a8c0.
Dec 2 06:58:56 picard kernel: ipv4: (1 messages suppressed. Flood?)
Dec 2 06:58:56 picard kernel: host 0fde11cc/eth0 ignores redirects for
0103a8c0 to 0103a8c0.
Dec 2 08:55:45 picard kernel: ipv4: (1 messages suppressed. Flood?)
Dec 2 08:55:45 picard kernel: host 0fde11cc/eth0 ignores redirects for
0103a8c0 to 0103a8c0.
Dec 2 09:01:03 picard kernel: ipv4: (1 messages suppressed. Flood?)
Seems kinda' silly for Linux to send a redirect to itself on the 204
address. This happens when one of the 204 clients tries to access the 192
network.
Is there something I should fix or should Linux NOT be sending these
redirects?