Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 2 subscribers
  • Views 3815 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Refusal of a local network after updating

kirsanoff
After updating from version 8.003 to 8.100 or 8.101 there is a network switching-off on internal interface of ASG. Switch D-LINK (4-port) is connected to the internal interface. All the local network after the switch has ceased to receive addresses on DHCP. If to connect the computer directly to the internal interface it receives the IP address on DHCP and connects in the Internet.
With version 8.003 all worked normally.


This thread was automatically locked due to age.
Parents
  • 0
    SSH by default is not allowed to from the ASG. Do you have a packet filter rule with a Interface Address Object as Source to allow SSH?

    About ICMP: Anything in packetfilter.log? Do you have "Allow ICMP from Firewall" enabled?

    Cheers
     Ulrich
  • 0 in reply to da_merlin
    In my tests, I'm not trying to SSH to the ASG, rather from the ASG.  Before the updates, I'm able to SSH from the ASG.  After a complete reinstall and restore from backup, I can SSH from the ASG again. 

    I'm not sure how to check the packet logs since I cannot get to the Admin pages.
Reply
  • 0 in reply to da_merlin
    In my tests, I'm not trying to SSH to the ASG, rather from the ASG.  Before the updates, I'm able to SSH from the ASG.  After a complete reinstall and restore from backup, I can SSH from the ASG again. 

    I'm not sure how to check the packet logs since I cannot get to the Admin pages.
Children
No Data
Cookie Information Banner