Prev: wifi issue
Next: Okular plugin for epub
From: Danno on 21 Jan 2010 18:01
Full Slackware 13.0 install. Using two NICs, eth0 is an r6040 and eth1 is
an 8139too. My intent is to eventually use this system as a firewall, but
am running into an issue with acquiring an IP address from my ISP.
Have eth0 configured to acquire its IP via DHCP. When I run it from within
my LAN, it acquires an address from my LAN's DHCP server without
difficulty - I can ping and surf. When I hook the system up to my cable
modem, though, it times out waiting for a DHCP response. I've editted
/etc/rc.d/rc.inet1
for a 30 seconds timeout, and fixed up
/etc/udev/rules.d/70-persistent-net.rules
so that the two NICs stay as eth0 and eth1.
eth1 is assigned its static IP without problem. For troubleshooting, when
I set up eth1 for DHCP and hook up to the cable modem, it also times out.
Generally I just restart rc.inet1 to troubleshoot, but have tried with
dhcpcd as well (also times out). Made sure to start/restart in the absence
of /etc/dhcpc/dhcpcd-eth0.pid
I'm pretty much at the limit of my understanding of the circumstance.
Anyone got some wisdom / direction for me?


--
Slackware 12.2, 2.6.27.7, Core i7 920, GeForce 8400 GS
RLU #272755
From: buck on 21 Jan 2010 18:54
Danno <WhoaBaby(a)MySecretPlace.org> wrote in
news:K156n.6430$_96.2857(a)newsfe02.iad:

> Full Slackware 13.0 install. Using two NICs, eth0 is an r6040 and
> eth1 is
> an 8139too. My intent is to eventually use this system as a
firewall,
> but am running into an issue with acquiring an IP address from my
ISP.
> Have eth0 configured to acquire its IP via DHCP. When I run it
from
> within
> my LAN, it acquires an address from my LAN's DHCP server without
> difficulty - I can ping and surf. When I hook the system up to my
> cable modem, though, it times out waiting for a DHCP response.

I have to provide the modem's MAC
/sbin/dhcpcd -I "00:20:40:4B:4B:C0" -N -R -t 10 -d eth${1}

otherwise the DHCP attempt passes the NIC's MAC, which is not going to
work.
--
buck
From: Danno on 21 Jan 2010 20:27
buck wrote:

> Danno <WhoaBaby(a)MySecretPlace.org> wrote in
> news:K156n.6430$_96.2857(a)newsfe02.iad:
>
>> Full Slackware 13.0 install. Using two NICs, eth0 is an r6040 and
>> eth1 is
>> an 8139too. My intent is to eventually use this system as a
> firewall,
>> but am running into an issue with acquiring an IP address from my
> ISP.
>> Have eth0 configured to acquire its IP via DHCP. When I run it
> from
>> within
>> my LAN, it acquires an address from my LAN's DHCP server without
>> difficulty - I can ping and surf. When I hook the system up to my
>> cable modem, though, it times out waiting for a DHCP response.
>
> I have to provide the modem's MAC
> /sbin/dhcpcd -I "00:20:40:4B:4B:C0" -N -R -t 10 -d eth${1}
>
> otherwise the DHCP attempt passes the NIC's MAC, which is not going to
> work.
> --
> buck


Thanks for the reply. Got no joy trying your suggestion, but it did lead
me inquire with my ISP's support page as to whether or not such a thing was
necessary. Their solution was to unplug the modem and plug it back in. LOL
it worked! Seems I have to do that whenever I switch routers. -shaking
head- I sometimes forget the non-linux world prefers a one-button
solution...



--
Slackware 12.2, 2.6.27.7, Core i7 920, GeForce 8400 GS
RLU #272755
From: Mike Jones on 22 Jan 2010 06:06
Responding to Danno:

> buck wrote:
>
>> Danno <WhoaBaby(a)MySecretPlace.org> wrote in
>> news:K156n.6430$_96.2857(a)newsfe02.iad:
>>
>>> Full Slackware 13.0 install. Using two NICs, eth0 is an r6040 and
>>> eth1 is
>>> an 8139too. My intent is to eventually use this system as a
>> firewall,
>>> but am running into an issue with acquiring an IP address from my
>> ISP.
>>> Have eth0 configured to acquire its IP via DHCP. When I run it
>> from
>>> within
>>> my LAN, it acquires an address from my LAN's DHCP server without
>>> difficulty - I can ping and surf. When I hook the system up to my
>>> cable modem, though, it times out waiting for a DHCP response.
>>
>> I have to provide the modem's MAC
>> /sbin/dhcpcd -I "00:20:40:4B:4B:C0" -N -R -t 10 -d eth${1}
>>
>> otherwise the DHCP attempt passes the NIC's MAC, which is not going to
>> work.
>> --
>> buck
>
>
> Thanks for the reply. Got no joy trying your suggestion, but it did
> lead
> me inquire with my ISP's support page as to whether or not such a thing
> was necessary. Their solution was to unplug the modem and plug it back
> in. LOL it worked! Seems I have to do that whenever I switch routers.
> -shaking head- I sometimes forget the non-linux world prefers a
> one-button solution...


FWIW, I have a similar NIC arrangement, but use eth0 as the static LAN
connection, and DHCP on eth1 for the internet modem connection.

If DHCP (or anything else) fails, the default eth0 (LAN) is already
setup, so only internet fails, and not the whole network setup.

YMMV.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
 | 
Pages: 1
Prev: wifi issue
Next: Okular plugin for epub