Hi!

Attached are some more debug logs...

shrew.pcap is captured while connecting with the ShrewSoft Client;
forticlient.pcap while connecting with a (currectly working) Forticlient
from another PC.
(xid:86e482ad) L3 socket: received request message from 192.168.101.13:68 to 
255.255.255.255 at wan1
 (xid:86e482ad) got a DHCPDISCOVER
(xid:86e482ad) Warning! can't get server id from client message
(xid:86e482ad) forwarding dhcp request from 192.168.156.9:67 to 
192.168.156.10:67
 (xid:86e482ad) got a DHCPOFFER
(xid:86e482ad) from server 192.168.156.10
(xid:86e482ad) sending dhcp reply from 0.0.0.0:67 to 192.168.101.13:68
 (xid:86e482ad) L3 socket: received request message from 192.168.101.13:68 to 
255.255.255.255 at wan1
(xid:86e482ad) got a DHCPREQUEST
(xid:86e482ad) forwarding dhcp request from 192.168.156.9:67 to 
192.168.156.10:67
 (xid:86e482ad) got a DHCPACK
(xid:86e482ad) from server 192.168.156.10
(xid:86e482ad) sending dhcp reply from 0.0.0.0:67 to 192.168.101.13:68
 netlink message!
dhcprelay: checking if we need to reconfigure
remove session src:192.168.156.9:67 dst:192.168.156.10:67 vf:0
dhcprelay: no changes detected
 (xid:66408215) L3 socket: received request message from 192.168.156.117:68 to 
255.255.255.255 at wan1
(xid:66408215) got a DHCPINFORM
(xid:66408215) Warning! can't get server id from client message
 (xid:66408215) forwarding dhcp request from 192.168.156.9:67 to 
192.168.156.10:67
(xid:66408215) got a DHCPACK
(xid:66408215) from server 192.168.156.10
 (xid:66408215) sending dhcp reply from 0.0.0.0:67 to 192.168.156.117:68
netlink message!
dhcprelay: checking if we need to reconfigure


disconnecting:

remove session src:192.168.156.9:67 dst:192.168.156.10:67 vf:0
dhcprelay: no changes detected

Attachment: forticlient.pcap
Description: Binary data

Attachment: shrew.log
Description: Binary data

Attachment: shrew.pcap
Description: Binary data

_______________________________________________
vpn-help mailing list
[email protected]
https://lists.shrew.net/mailman/listinfo/vpn-help

Reply via email to