Hi Jason,
No it doesn't work. Now it is in a state that client can't even get an ip. If I set ip address statically it can't reach its gateway 10.100.60.2 either.
I monitored all the traffic, on dhcp server, on swich and on client.
1. Wireshark on the client shows that client send dhcp discover packages but does not receive any other dhcp reply packages.
2. Dhcp logs and tcpdump capture on dhcp server shows that ewc relays dhcp packages to him via 10.100.60.2 relay interface. So dhcp server gets dhcp discover package and reply with dhcp offer to ewc(10.100.60.2)
3. I mirrored ge.2.43 port of S4 which ewc esa1 connected to another port and watched with wireshark. It shows that ewc sends dhcp offer package to dstmac:client mac address and dstip:255.255.255.255. So it seems EWC config of DHCP Relay is working. But the problem is on client, wireshark shows no dhcp offer packages received. So client send dhcp discover continuously.
4. If I set ip address statically on the client and try to open
http://10.100.60.2, wireshark shows that client sends ARP packages and asks "show is 10.100.60.2 tell 10.100.60.100" continuously but never gets a reply. So static ip not working either.
If it makes sense network topology is like this: EWC esa0(default route) connected to S4-ge.2.46(vlan 1 untag). EWC esa1(3.rd party vlan 60 untag) connected to S4-ge.2.43(vlan 60 utag). Client connectted to S4-ge.2.42(vlan 60 untag). dhcp server connected to S4-ge.2.45(vlan 1 untag)
Any suggestion to troubleshoot further is mostly welcome.
I tried different browsers. No portal redirection. Directly connect to internet. If I browse
https://10.100.60.2 I get a page "Portal Central". There is logoff session button and get current status button. But no login page. I also tried to use logoff button but it does not get login page either.
Thanks,
Rahman