Página 1 de 1

Help please: can't get IP from cable modem

MensagemEnviado: Seg Out 22, 2012 6:20 pm
por mrgreen
I'm hoping someone with more Linux and BrazilFW 3.x experience can help me since I've been tearing my hair out for two days over this.

I've been running a BrazilFW 2.x box for probably near 7 or 8 years now, and I've never encountered a problem like this before. I recently wanted to set up VPN, and the add-on for BFW 2.x is outdated and not compatible with modern OpenVPN setups, so I decided it was time to migrate to BFW 3.x. I first installed it into a VMware virtual machine, and once I figured out how it all worked and how I wanted to modify it, I built a new router box and installed the latest 3.x release onto real hardware. Everything went fine until I tried to switch eth1 (Internet) from STATIC to DHCP.

The problem is that BFW is unable to obtain an IP from the cable modem (or doesn't try.) The really weird thing is that if I connect the eth1 NIC to my existing LAN instead of the modem then the new BFW box obtains an IP lease from the DHCP running on the old BFW router 2.x with no problem, but is unable to do the same when connected directly to the modem. I know the modem is fine, not only does my BFW 2.x box obtain a lease without trouble, so does any other device I connect directly to it. Only the new box is unable get a lease from it. If I change eth1 back to STATIC and plug in all the IP, MASK, and GATEWAY values obtained by the old router box from my ISP, then the new one happily accesses the internet and shares it with the LAN NIC. Since my ISP rarely changes IP allocations, I could perhaps leave it that way, but I'm sure after some period the lease will time out and the box will lose the connection.

My ISP allows two concurrent IP leases,and doesn't restrict access to a particular MAC, but just in case I set the eth1 MAC address to match the one on the old BFW 2.x box, but it still won't get a lease.

I tried swapping the internet/local eth0/eth1 allocations by modifying the files in /etc/brazilfw/physical/, but I still can't get an IP from the modem, even using the other NIC to connect to the modem. I've tried running dhclient manually but every time I run it it just outputs "Terminated" and there is no chance to the IP for eth1.

I'm hoping that someone here has an idea what it going on, and more importantly, how to fix it. I don't want to be stuck on BrazilFW 2.x indefinitely, even though it has served me faithfully up till now.

Here is my configuration:

Intel(R) Pentium(R) 4 CPU 2.00GHz @ (1x) 1.993 GHz
750Mb Hard Drive
BrazilFW version 3.0.258 (kernel 3.4.5)
etho: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) (Integrated) Kernel module: e100
eth1: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) (PCI) Kernel module: 8139too
ISP: TekSavvy

Modem:
    Thomson DCM476
    Firmware: STAC.02.50
    Software: a81a
    Bootloader: 2.3.1
ifconfig output when BFW 3.x box connected to cable modem:

Código: Selecionar todos
eth0      Link encap:Ethernet  HWaddr 00:09:6B:F2:81:64 
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST 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
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth1      Link encap:Ethernet  HWaddr 1C:65:9D:DC:32:A2 
          UP BROADCAST 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
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:21 Base address:0x8000

ifb0      Link encap:Ethernet  HWaddr 46:22:49:1E:95:83 
          UP BROADCAST RUNNING NOARP  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
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:1500  Metric:1
          RX packets:218 errors:0 dropped:0 overruns:0 frame:0
          TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:30134 (29.4 KiB)  TX bytes:30134 (29.4 KiB)

When I connect my new BFW 3.x box eth1 to my LAN and reboot it, this is what ifconfig eth1 looks like:

Código: Selecionar todos
eth1      Link encap:Ethernet  HWaddr 1C:65:9D:DC:32:A2 
          inet addr:192.168.1.4  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1492  Metric:1
          RX packets:8674 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4678 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:897855 (876.8 KiB)  TX bytes:2038033 (1.9 MiB)
          Interrupt:21 Base address:0x8000