[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Trouble with internal network



On Mon, 26 Jun 2000, Mostly Harmless wrote:

> I'm trying to get an internal network working so that I can set up IP
> masquerading for a few Windows boxen (side question: anyone know what
> IPs to block to prevent @home from probing for home networks?).
>  
> Here's the output of /sbin/ifconfig -a:
> cc492523-a:/usr/doc/alsa-base$ /sbin/ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:10:4B:79:B5:4A  
>           inet addr:24.3.147.215  Bcast:24.3.147.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:32157 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:22053 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:521 txqueuelen:100 
>           Interrupt:5 Base address:0xe000 
> 
> eth0:0    Link encap:Ethernet  HWaddr 00:10:4B:79:B5:4A  
>           inet addr:192.168.0.1  Bcast:192.168.255.255  Mask:255.255.0.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           Interrupt:5 Base address:0xe000 
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:75 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
> 
> And route -n:
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 24.3.147.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 192.168.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
> 0.0.0.0         24.3.147.1      0.0.0.0         UG    0      0        0 eth0
> 
> If anyone is able to help me out I'd appreciate it immensely.
> 

Just a theory, never done this:
The documentation for network-aliasing, or, setting up several ip-s on one
network card, says you have to use eth0:0, eth0:1 etc. 
It seems using just using eth0 when network-aliasing is enabled in the
kernel works OK (you *have* enabled network-aliasing in the kernel?), but
I'm not as sure about mixing eth0 and eth0:0.
Perhaps you should replace eth0 and eth0:0 with eth0:0 and eth0:1?
/etc/init.d/network should be the right place to set the defaults.

Harald

--
Philosophy, law, medicine and even theology, alas! I studied everything with 
an ardent will and here I am, poor fool, just as far behind as ever. 
No more advanced than before.
    Goethe - Faust



Reply to: