Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #196811 > unrolled thread

ferm systemd rasbian

Back to article view | Back to linux.debian.user

Contents

  ferm systemd rasbian basti <mailinglist@unix-solution.de> - 2018-06-20 22:10 +0200
    Re: ferm systemd rasbian Don Armstrong <don@debian.org> - 2018-06-21 19:10 +0200
      Re: ferm systemd rasbian basti <mailinglist@unix-solution.de> - 2018-06-21 19:50 +0200
      Re: ferm systemd rasbian basti <basti@unix-solution.de> - 2018-06-21 19:50 +0200

#196811 — ferm systemd rasbian

Hello,
I know thats a bit offtopic.
I have raspian as router os, all works fine expect ferm on start /reboot.

If I use the default systemd.service on startup it hangs with "job
waiting ... " without timeout and won't boot to login prompt.

If I invoke the service with

/etc/systemd/system/ferm.service.d/local.conf
[Unit]
Wants=network.target
After=network.target

[Install]
WantedBy=multi-user.target

ferm is starting but some other network services fail, eg.

- dhcp
- interfaces have no addresses

The Lan interface is down for example.
When I login and force it with ifup -a it get an address but dhcp still
wont start.

start ferm in rc.local did also fail.

when i disable the ferm service dhcp is working, interfaces get
addresses and i can start ferm manually (after login) without any problems.

Any ideas for solve this?

Best regards,
basti

[toc] | [next] | [standalone]

#196839

On Wed, 20 Jun 2018, basti wrote:
> ferm is starting but some other network services fail, eg.
> 
> - dhcp
> - interfaces have no addresses
> 
> The Lan interface is down for example.
> When I login and force it with ifup -a it get an address but dhcp still
> wont start.

Without knowing more details, this sure sounds like you have some sort
of issues with your firewall rules not properly allowing DHCP.

You might have better luck including your ferm.conf and possibly the
output of iptables -L -n; when things work and iptables -L -n; when they
don't.


-- 
Don Armstrong                      https://www.donarmstrong.com

All my dreams came true.
I just didn't think them through.
 -- a softer world #388
    http://www.asofterworld.com/index.php?id=388

[toc] | [prev] | [next] | [standalone]

#196840

On 21.06.2018 18:42, Don Armstrong wrote:
> On Wed, 20 Jun 2018, basti wrote:
>> ferm is starting but some other network services fail, eg.
>>
>> - dhcp
>> - interfaces have no addresses
>>
>> The Lan interface is down for example.
>> When I login and force it with ifup -a it get an address but dhcp still
>> wont start.
> 
> Without knowing more details, this sure sounds like you have some sort
> of issues with your firewall rules not properly allowing DHCP.
> 
> You might have better luck including your ferm.conf and possibly the
> output of iptables -L -n; when things work and iptables -L -n; when they
> don't.

I have fixed it. dhcpcd was the problem.

[toc] | [prev] | [next] | [standalone]

#196841

On 21.06.2018 18:42, Don Armstrong wrote:
> On Wed, 20 Jun 2018, basti wrote:
>> ferm is starting but some other network services fail, eg.
>>
>> - dhcp
>> - interfaces have no addresses
>>
>> The Lan interface is down for example.
>> When I login and force it with ifup -a it get an address but dhcp still
>> wont start.
> 
> Without knowing more details, this sure sounds like you have some sort
> of issues with your firewall rules not properly allowing DHCP.
> 
> You might have better luck including your ferm.conf and possibly the
> output of iptables -L -n; when things work and iptables -L -n; when they
> don't.
> 
> 

I have fixed it. dhcpcd was the problem.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web