Mark Copper wrote: > > Bob Proulx wrote: > > I thought I would say that while researching my response I fired up a > > VM running Wheezy 7 and tried the above. It worked perfectly fine for > > me. So definitely the version in Stable Wheezy 7 handles this above > > case fine. > > I'd go easy on the "definitely". That configuration appeared to work > fine on my wheezy box for both /etc/init.d/networking reload and > restart. It even worked partially when it was rebooted; viz. port 53 > and even port 80 (though extremely sluggishly). But sshd over port 22 > did not. It was as if sshd had not come up, but that couldn't be > since when I got in by KVM over IP, simply restarting networking > (using old style interfaces) solved the problem. Unfortunately, I'm > not in the position to try to replicate the problem. But a word of > caution to anyone else who might come across this may be in order. There may be gremlins there still. Note that I still like the older interface. And when using the dependent ethX:Y style I think there are definitely gremlins. I was able to hang the state and eventually simply rebooted the VM in order to clear it. I couldn't narrow something down into a repeatable test case. But I wasn't able to confuse the above style. But surely sshd listens on 0.0.0.0:22 which is a wildcard and matches any local address. Meaning that additional IP addresses can come and go and it doesn't matter. Or at least shouldn't matter. tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN However if an application binds to a specific address then it will need to be cycled if that address goes away or appears. tcp 0 0 192.168.1.99:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN Bob
Attachment:
signature.asc
Description: Digital signature