Re: Buggered up my router somehow.
I see you have both 192.* nets using the same broadcast...
255.255.255.0
Can you do that ?
Adam Scriven - Lore wrote:
>
> Ok, by some great and wonderful streak of stupidity, I seem to have somehow
> completely fscked up my router.
>
> It's hooked up to an ADSL modem, running PPPoE (Roaring Penguin), and that part
> looks like it's working great.
> I've got 2 other network cards, both 3Com 905B. I have the 3c59x module
> loading with modprobe, and I've checked ifconfig, and both cards look to be
> setup correctly.
> eth0 is 192.168.0.1, and eth1 is 192.168.1.1
> (Incedentally, eth2 is an NE2k-pci card, for the PPPoE client).
>
> I can see the world just fine from the router (I'm telnetting to an ISP
> where my maail is hosted to send out this message, and I'm on the router now),
> but I can't ping anything on my 192.168.0.0 network (192.168.1.0 isn't used
> yet).
> The route command returns:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> ADSL-NAME * 255.255.255.255 UH 0 0 0 ppp0
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
> 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
> default ADSL-NAME 0.0.0.0 UG 0 0 0 ppp0
>
> (I had to tyype this in by hand, so any formatting problems are mine.)
>
> This all looks OK to me, but pinging just gives 100% packet loss, and traceroute
> to 192.168.0.2 from the router gives:
> traceroute: sendto: Operation not permitted
> 1 traceroute: wrote 192.168.0.2 38 chars, ret=-1
>
> So, the question is, how have I managed to bugger this up, since it was working
> fine this morning. I recompiled a new 2.2.17 kernel, but AFAIK I picked all
> the options that I needed. My old (working) kernel was 2.2.14. Did I forget
> some vital piece of information?
>
> Thanks very much for any help.
> Adam
>
> OH, I also meant to ask. I used to use linuxconf on my RH systems. Is there an
> equiv. for Debian? Something better, perhaps?
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Reply to: