ddclient gets confused with multiple ethernet ports (solved)

[Bobnoxous]

Hello. I have a server with 2 NICs. I may try to put them on different subnets in the future, with one for external requests and the other for intranet requests, but for right now, they're both on the same subnet and have static IPs.

My internet service provides a dynamic IP, and I use ddclient to get the IP from my router (linksys), and update my DNS service if it changes. My router forwards all incoming http requests to eth1 on my server. If ddclient tries to query my router on eth0, it hangs, presumably because the response is going to eth1. So ddclient.conf specifies that eth1 should be used.

The problem is, after I reboot the machine, ddclient still seems to query eth0. The following hangs:

> ddclient --query

Strangely enough, if I restart eth0 (/etc/init.d/net.eth0 restart), then ddclient only seems to try eth1 and is happy. So it seems to have something to with the order interfaces are brought up.

Anyone know why ddclient would query my router via eth0, when my config file says to use eth1?
_________________
"The problem with the world is that fools and fanatics are always so sure of themselves while wiser people are so full of doubt."
- Bertrand Russell

[SnakeByte]

Hi Bobnoxous.

can you please post the config files

[Bobnoxous]

Certainly. It's kind of silly not to have posted them.

ddclient.conf
######################################################
daemon=300 # check every 300 seconds
syslog=yes # log update msgs to syslog
# mail=root # mail all msgs to root
# mail-failure=root # mail failed update msgs to root
pid=/var/run/ddclient/ddclient.pid # record PID in file.

# FW login and password
use=if, if=eth1 # via interfaces
use=linksys-ver2, fw=192.168.15.1:80 # via Linksys's internet FW
fw-login=xxxxx
fw-password=yyyyyyyyyyy

## ZoneEdit (zoneedit.com)
server=www.zoneedit.com, \
protocol=zoneedit1, \
login=zzzzzzzz, \
password=aaaaaaaaaaaaaaaa, \
test.com


net
###########################################################
# Specify ifconfig interface as the default, rather than iproute2
modules=( "ifconfig" )

# Static configuration of ethernet ports
config_eth0=( "192.168.15.211/24 brd 192.168.15.255" )
# config_eth0=( "dhcp" )
config_eth1=( "192.168.15.210/24 brd 192.168.15.255" )
# config_eth1=( "dhcp" )

# Set default gateway to use eth0
gateway="eth1/192.168.15.1"

# If a specified module fails (like dhcp - see below), you can specify a
# fallback like so
#fallback_eth0=( "192.168.0.2 netmask 255.255.255.0" )
#fallback_route_eth0=( "default via 192.168.0.1" )
_________________
"The problem with the world is that fools and fanatics are always so sure of themselves while wiser people are so full of doubt."
- Bertrand Russell

[Bobnoxous]

Hmm, this problem seems to have gone away now. When I reboot the machine, ddclient only checks on eth1, as expected.

I moved some things around in ddclient.conf, and removed a bunch of comments, getting it cleaned up for this posting, so maybe the order things are specified can make a difference.

Just one of those things. Thanks for the help SnakeByte.
_________________
"The problem with the world is that fools and fanatics are always so sure of themselves while wiser people are so full of doubt."
- Bertrand Russell

[Bobnoxous]

An update. The problem occurred not when I rebooted the computer, as I thought, but when my dynamic IP changed at the router. Then, ddclient would hang when trying to retreive the new IP from the router.

I belive the problem is with the RT32P2 router that came with my vonage service. It seems to me that this router really sucks. Since I made it my "main" router, I've had to reboot it to get back internet access two times in as many weeks. So, I've gone back to using a WRT54G router, and the RT31P2 plugs into that, only being used for the vonage service. I was afraid this might affect voice quality since the RT31P2 could presumably enforce some bandwidth allocation for the VOIP, whereas now it's just on the same network as all the computers, but it hasn't been a problem.

Maybe the RT31P2 didn't respond to ddclient, although I don't think ddclient should just hang in that case. I also haven't setup my 2nd ethernet port, so it's possible I may still have a problem when I set that up (it wasn't working for some reason, and i wasn't motivated to track down the problem in the wiring yet) and the dynamic IP changes again. But being that the RT31P2 proved to be so unreliable, and there are no updates I can find for it, I think that was the culprit.
_________________
"The problem with the world is that fools and fanatics are always so sure of themselves while wiser people are so full of doubt."
- Bertrand Russell